In the kong hybrid deployment mode, the active health check is not performed after it has been running for a period of time about kong HOT 10 CLOSED

When I checked kong's dp node log, I found the following log and wanted to know how it was run. Why did the health tests stop。
2024/02/04 11:49:09 [debug] 47930#0: *6039159 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aitxzl) event: target added '172.23.0.85(172.23.0.85:10011)'
2024/02/04 11:49:09 [debug] 47930#0: *6039159 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aitxzl) event: target status '172.23.0.85(172.23.0.85:10011)' from 'false' to 'true'
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] events.lua:211: do_event_json(): worker-events: handling event; source=mlcache_2, event=mlcache:purge:kong_core_db_cache_2, pid=47930, data=
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] events.lua:211: do_event_json(): worker-events: handling event; source=mlcache_2, event=mlcache:purge:kong_db_cache_2, pid=47930, data=
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] events.lua:211: do_event_json(): worker-events: handling event; source=declarative, event=flip_config, pid=47930, data=1ce43538-a005-4f97-b55a-4e9f3bf5269a
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:modelAnalysis) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aiyyhc) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:eqtest) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:message) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:serviceArea) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aitpmbjc) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aiocr) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:ertest) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:test) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:ailxyysb) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:blockchain) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:event) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aispmbjc) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aiyysb) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aispzl) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aitxzl) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] healthcheck.lua:1126: log(): [healthcheck] (1ce43538-a005-4f97-b55a-4e9f3bf5269a:aiyylj) healthchecker stopped
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] init.lua:275: flip(): [DB cache] flipping current cache
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] init.lua:275: flip(): [DB cache] flipping current cache
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:456: init(): [dns-client] (re)configuring dns client
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:461: init(): [dns-client] staleTtl = 4
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:465: init(): [dns-client] noSynchronisation = false
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:484: init(): [dns-client] query order = LAST, SRV, A, CNAME
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:524: init(): [dns-client] adding A-record from 'hosts' file: localhost = 127.0.0.1
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:539: init(): [dns-client] adding AAAA-record from 'hosts' file: localhost = [::1]
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:539: init(): [dns-client] adding AAAA-record from 'hosts' file: localhost6 = [::1]
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:539: init(): [dns-client] adding AAAA-record from 'hosts' file: localhost6.localdomain6 = [::1]
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:524: init(): [dns-client] adding A-record from 'hosts' file: localhost.localdomain = 127.0.0.1
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:539: init(): [dns-client] adding AAAA-record from 'hosts' file: localhost.localdomain = [::1]
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:524: init(): [dns-client] adding A-record from 'hosts' file: localhost4 = 127.0.0.1
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:524: init(): [dns-client] adding A-record from 'hosts' file: localhost4.localdomain4 = 127.0.0.1
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:524: init(): [dns-client] adding A-record from 'hosts' file: abilitycenter-gateway-7 = 172.23.8.158
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:548: init(): [dns-client] validTtl = nil
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:589: init(): [dns-client] nameserver 172.23.8.2
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:589: init(): [dns-client] nameserver 172.23.8.3
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:594: init(): [dns-client] attempts = 5
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:601: init(): [dns-client] no_random = true
2024/02/04 11:49:10 [debug] 47932#0: *6039165 [lua] client.lua:610: init(): [dns-client] timeout = 2000 ms

from kong.

Hi. I tried searching the code and the log does not seem to be from 2.7 (the file "healthcheck.lua" does not exist in the 2.7 code base). Could you confirm if that's the exact version? And we always recommend using the latest version of Kong.

from kong.

Hi. I tried searching the code and the log does not seem to be from 2.7 (the file "healthcheck.lua" does not exist in the 2.7 code base). Could you confirm if that's the exact version? And we always recommend using the latest version of Kong.

Hi.I downloaded the installation package from the following website, and I run kong versiong on the server where I installed it, showing version 2.7.0.I wonder if these versions are different from the version you said.
https://docs.konghq.com/gateway/2.7.x/install-and-run/centos/

from kong.

@FuleChu Anyway, still we recommend using the latest version of Kong: https://docs.konghq.com/gateway/3.6.x/install/
Does the issue reproduce with 3.6?

from kong.

@FuleChu Anyway, still we recommend using the latest version of Kong: https://docs.konghq.com/gateway/3.6.x/install/ Does the issue reproduce with 3.6?

I have not used version 3.6 yet. This is a problem I found in the online environment. Upgrading the version is not easy. By the way, I am solving this problem by executing the command kong reload regularly. Thank you for your reply, I will try to upgrade the version and test if there is any problem.

from kong.

@FuleChu , do you get this issue solved?

from kong.

This issue is marked as stale because it has been open for 14 days with no activity.

from kong.

This seems related to another ticket, which says the active health checker does not update its status for a long time. Bumping this for visibility.

from kong.

This issue is marked as stale because it has been open for 14 days with no activity.

from kong.

Dear contributor,

We are automatically closing this issue because it has not seen any activity for three weeks.
We're sorry that your issue could not be resolved. If any new information comes up that could
help resolving it, please feel free to reopen it.

Your contribution is greatly appreciated!

Please have a look
our pledge to the community
for more information.

Sincerely,
Your Kong Gateway team

from kong.