379743:20251005:002427.205 executing housekeeper 379743:20251005:002452.600 slow query: 25.390971 sec, "select itemid,min(clock) from history group by itemid" 379743:20251005:002512.721 slow query: 19.903357 sec, "select itemid,min(clock) from history_uint group by itemid" 379743:20251005:002516.625 slow query: 3.903498 sec, "select itemid,min(clock) from history_text group by itemid" 379743:20251005:002643.500 housekeeper [deleted 158648 hist/trends, 2209 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 326 audit, 0 autoreg_host, 0 records in 136.290801 sec, idle for 1 hour(s)] 379796:20251005:003001.124 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"f5dc9e14-0eb2-4c80-bc7a-de69c3fdc930"}. 379804:20251005:003001.128 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"02810d7b-49a4-49ca-a466-ebaf42adb767"}. 379809:20251005:010000.895 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"54387e76-571f-4bb3-9fa2-d8262e5187ca"}. 379831:20251005:010000.902 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"e9c3dc16-6238-4b67-b608-2ab26f211e93"}. 379812:20251005:011015.692 [ AWS RDS ] ERROR: Error: cannot get URL: Timeout was reached. 379734:20251005:011015.693 discovery rule "nb-consumer-prod-consumer-prod-ecommerce-rds-1:aws.rds.events.discovery" became not supported: Preprocessing failed for: {"error":"Error: cannot get URL: Timeout was reached."} 1. Failed: TypeError: undefined not callable (property 'forEach' of [object Object]) at [anon] (duktape.c:69012) internal at [anon] (function:4) preventsyield 379734:20251005:012000.616 discovery rule "nb-consumer-prod-consumer-prod-ecommerce-rds-1:aws.rds.events.discovery" became supported 379743:20251005:012643.565 executing housekeeper 379743:20251005:012812.662 housekeeper [deleted 297512 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 6 audit, 0 autoreg_host, 0 records in 89.092419 sec, idle for 1 hour(s)] 379784:20251005:013000.600 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"6b5b1e42-eff7-493a-9dce-8f17813b70bc"}. 379813:20251005:013000.621 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"0b442d2c-0f09-4fa2-b524-7159c8b1d9a9"}. 379838:20251005:020000.966 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"7bbfee14-e490-4877-afd0-7ee8111b7ae7"}. 379797:20251005:020000.988 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"3b126a72-79e0-47a2-9b90-c51ba7bb2fb2"}. 379753:20251005:022000.986 item "ip-10-166-44-99:web.page.regexp[https://{$NL_DNS}/newspapers?sort=dsc&formType=basic&alltext=Smith&nagios_app={HOST.IP},,,Showing Results,,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379760:20251005:022429.209 item "ip-10-166-44-99:web.page.regexp[https://{$NL_DNS}/newspapers?sort=dsc&formType=basic&alltext=Smith&nagios_app={HOST.IP},,,Showing Results,,]" became supported 379743:20251005:022812.688 executing housekeeper 379743:20251005:022941.490 housekeeper [deleted 293927 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 7 audit, 0 autoreg_host, 0 records in 88.797299 sec, idle for 1 hour(s)] 379858:20251005:023001.014 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"75da2bce-f703-4d71-a665-321d217f26be"}. 379835:20251005:023001.024 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"7852e255-01e0-4338-94eb-1cb619faea2c"}. 379784:20251005:030000.786 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b3ba043a-8aab-4524-884d-72a8ccd5bf87"}. 379829:20251005:030000.857 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"484249a2-0a59-43e0-816c-d2df71714a8c"}. 379743:20251005:032941.591 executing housekeeper 379853:20251005:033000.792 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"28f7df04-322c-477f-b7cc-ffddd87d83fc"}. 379814:20251005:033000.890 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"288617fc-009f-4026-bf0c-8d6338776dc0"}. 379743:20251005:033109.343 housekeeper [deleted 293420 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 4 audit, 0 autoreg_host, 0 records in 87.747150 sec, idle for 1 hour(s)] 379781:20251005:040000.986 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"88d70b80-390e-4cd9-a627-178dd0104cfc"}. 379784:20251005:040001.007 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"65938fb4-bbb5-4ab9-a686-79d0219a5590"}. 379864:20251005:043000.573 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"d732039d-b098-483a-ade9-e529bc64a939"}. 379793:20251005:043000.680 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"01d2531a-a717-422d-8450-76f2d66f7ebf"}. 379743:20251005:043109.444 executing housekeeper 379743:20251005:043236.582 housekeeper [deleted 293707 hist/trends, 0 items/triggers, 0 events, 3 problems, 0 sessions, 0 alarms, 8 audit, 0 autoreg_host, 0 records in 87.131644 sec, idle for 1 hour(s)] 379871:20251005:050000.677 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"7d3f4da1-8788-4bbb-867c-be3f6a26f053"}. 379867:20251005:050000.704 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"de4ab407-e606-4d1a-8335-1da36dd3cfb3"}. 379823:20251005:053000.616 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"84630b2f-d9e4-4f22-a252-6ed61a9fe7f6"}. 379829:20251005:053000.646 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"ce51be46-1a8b-4980-9304-623ed96d286e"}. 379743:20251005:053236.663 executing housekeeper 379743:20251005:053405.470 housekeeper [deleted 293692 hist/trends, 0 items/triggers, 0 events, 2 problems, 0 sessions, 0 alarms, 169 audit, 0 autoreg_host, 0 records in 88.801402 sec, idle for 1 hour(s)] 379776:20251005:060000.651 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"72b6089f-d59d-4174-9c9e-7b48f1ca9789"}. 379785:20251005:060000.705 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"347a50c4-9d76-41d8-8348-871f545478be"}. 379925:20251005:060343.952 cannot send list of active checks to "10.166.40.183": host [ip-10-166-40-183] not found 379923:20251005:060352.189 cannot send list of active checks to "10.166.40.126": host [ip-10-166-40-126] not found 379999:20251005:060528.228 Zabbix agent item "proc.num[supervisord]" on host "ip-10-166-46-179" failed: first network error, wait for 15 seconds 379931:20251005:060649.616 failed to accept an incoming connection: from 10.166.46.180: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379802:20251005:063000.887 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"72034904-8d66-4787-b2c2-2d893614ae90"}. 379861:20251005:063001.135 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"cf0f9c77-c2ac-4ef4-a59c-6d22863c972a"}. 379743:20251005:063405.571 executing housekeeper 379929:20251005:063421.495 cannot send list of active checks to "10.166.46.79": host [ip-10-166-46-79] not found 379924:20251005:063422.019 cannot send list of active checks to "10.166.46.72": host [ip-10-166-46-72] not found 379928:20251005:063422.538 cannot send list of active checks to "10.166.46.172": host [ip-10-166-46-172] not found 379930:20251005:063423.065 cannot send list of active checks to "10.166.46.136": host [ip-10-166-46-136] not found 379931:20251005:063423.596 cannot send list of active checks to "10.166.46.78": host [ip-10-166-46-78] not found 379927:20251005:063424.107 cannot send list of active checks to "10.166.46.70": host [ip-10-166-46-70] not found 379932:20251005:063424.573 cannot send list of active checks to "10.166.46.75": host [ip-10-166-46-75] not found 379924:20251005:063425.086 cannot send list of active checks to "10.166.46.154": host [ip-10-166-46-154] not found 379929:20251005:063425.561 cannot send list of active checks to "10.166.46.182": host [ip-10-166-46-182] not found 379925:20251005:063426.083 cannot send list of active checks to "10.166.46.187": host [ip-10-166-46-187] not found 379753:20251005:063426.702 item "ip-10-166-46-70:tomcat_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_max_memory)-last(//tomcat_available_memory)". 379999:20251005:063426.834 enabling Zabbix agent checks on host "ip-10-166-46-136": interface became available 379999:20251005:063427.400 enabling Zabbix agent checks on host "ip-10-166-46-70": interface became available 379760:20251005:063430.773 item "ip-10-166-46-172:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251005:063431.731 item "ip-10-166-46-79:tomcat_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_max_memory)-last(//tomcat_available_memory)". 379753:20251005:063431.731 item "ip-10-166-46-172:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251005:063432.411 enabling Zabbix agent checks on host "ip-10-166-46-79": interface became available 379753:20251005:063436.714 item "ip-10-166-46-154:tomcat_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_max_memory)-last(//tomcat_available_memory)". 379753:20251005:063436.714 item "ip-10-166-46-187:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251005:063437.365 enabling Zabbix agent checks on host "ip-10-166-46-154": interface became available 379753:20251005:063440.735 item "ip-10-166-46-78:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379758:20251005:063441.835 item "ip-10-166-46-172:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-172/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379758:20251005:063441.835 item "ip-10-166-46-78:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251005:063442.374 enabling Zabbix agent checks on host "ip-10-166-46-172": interface became available 379753:20251005:063446.855 item "ip-10-166-46-187:tomcat_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_available_memory)". 379999:20251005:063447.372 enabling Zabbix agent checks on host "ip-10-166-46-187": interface became available 379753:20251005:063450.733 item "ip-10-166-46-75:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251005:063451.765 item "ip-10-166-46-78:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-78/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251005:063451.765 item "ip-10-166-46-75:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251005:063452.377 enabling Zabbix agent checks on host "ip-10-166-46-78": interface became available 379753:20251005:063455.840 item "ip-10-166-46-72:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251005:063456.775 item "ip-10-166-46-72:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:063500.846 item "ip-10-166-46-182:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251005:063501.781 item "ip-10-166-46-75:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-75/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251005:063501.781 item "ip-10-166-46-182:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251005:063502.387 enabling Zabbix agent checks on host "ip-10-166-46-75": interface became available 379753:20251005:063505.765 item "ip-10-166-46-136:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251005:063506.789 item "ip-10-166-46-72:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-72/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251005:063506.789 item "ip-10-166-46-136:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251005:063507.404 enabling Zabbix agent checks on host "ip-10-166-46-72": interface became available 379753:20251005:063511.795 item "ip-10-166-46-182:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-182/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379999:20251005:063512.377 enabling Zabbix agent checks on host "ip-10-166-46-182": interface became available 379753:20251005:063515.808 item "ip-10-166-46-70:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251005:063516.889 item "ip-10-166-46-136:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-136/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251005:063516.889 item "ip-10-166-46-70:tomcat_percent_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-70/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:063520.886 item "ip-10-166-46-79:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379755:20251005:063521.771 item "ip-10-166-46-79:tomcat_percent_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-79/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379755:20251005:063525.832 item "ip-10-166-46-154:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379755:20251005:063526.854 item "ip-10-166-46-154:tomcat_percent_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-154/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:063539.818 item "ip-10-166-46-72:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379753:20251005:063540.823 item "ip-10-166-46-78:tomcat_available_memory" became supported 379753:20251005:063540.824 item "ip-10-166-46-72:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379753:20251005:063541.924 error reason for "ip-10-166-46-78:tomcat_percent_used_memory" changed: Cannot evaluate function: item "/ip-10-166-46-78/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:063542.324 item "ip-10-166-46-172:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063542.827 item "ip-10-166-46-72:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379754:20251005:063543.811 item "ip-10-166-46-70:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379753:20251005:063543.898 item "ip-10-166-46-136:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063544.073 item "ip-10-166-46-70:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063544.652 item "ip-10-166-46-75:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379754:20251005:063544.834 item "ip-10-166-46-70:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379753:20251005:063545.101 item "ip-10-166-46-154:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063545.255 item "ip-10-166-46-78:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063545.687 item "ip-10-166-46-182:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063546.056 item "ip-10-166-46-187:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063546.403 item "ip-10-166-46-79:vfs.file.contents["/sys/class/net/eth0/speed"]" became not supported: Cannot read from file. 379753:20251005:063547.812 item "ip-10-166-46-154:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379754:20251005:063548.879 item "ip-10-166-46-154:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379753:20251005:063551.875 item "ip-10-166-46-78:tomcat_used_memory" became supported 379753:20251005:063551.875 item "ip-10-166-46-182:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379753:20251005:063552.822 item "ip-10-166-46-182:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379753:20251005:063605.860 item "ip-10-166-46-78:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379753:20251005:063606.898 item "ip-10-166-46-78:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379759:20251005:063607.902 item "ip-10-166-46-172:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379753:20251005:063608.845 item "ip-10-166-46-172:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379743:20251005:063610.628 housekeeper [deleted 293468 hist/trends, 1980770 items/triggers, 2 events, 1 problems, 0 sessions, 0 alarms, 2026 audit, 11 autoreg_host, 0 records in 125.051746 sec, idle for 1 hour(s)] 379753:20251005:063611.907 item "ip-10-166-46-136:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379757:20251005:063612.925 item "ip-10-166-46-136:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379753:20251005:063615.887 item "ip-10-166-46-75:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379759:20251005:063616.941 item "ip-10-166-46-75:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379753:20251005:063620.888 item "ip-10-166-46-79:tomcat_available_memory" became supported 379756:20251005:063623.971 item "ip-10-166-46-187:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379753:20251005:063624.881 item "ip-10-166-46-187:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379757:20251005:063625.979 item "ip-10-166-46-154:tomcat_available_memory" became supported 379753:20251005:063631.924 item "ip-10-166-46-79:tomcat_used_memory" became supported 379759:20251005:063636.036 item "ip-10-166-46-79:vfs.dev.read.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.read.time.rate[nvme0n1])/(last(//vfs.dev.read.rate[nvme0n1])+(last(//vfs.dev.read.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.read.rate[nvme0n1]) > 0)". 379753:20251005:063636.904 item "ip-10-166-46-154:tomcat_used_memory" became supported 379753:20251005:063636.905 item "ip-10-166-46-79:vfs.dev.write.await[nvme0n1]" became not supported: Cannot evaluate function: not enough data at "last(//vfs.dev.write.time.rate[nvme0n1])/(last(//vfs.dev.write.rate[nvme0n1])+(last(//vfs.dev.write.rate[nvme0n1])=0)))*1000*(last(//vfs.dev.write.rate[nvme0n1]) > 0)". 379757:20251005:063640.052 item "ip-10-166-46-72:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063640.929 item "ip-10-166-46-72:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063644.085 item "ip-10-166-46-70:vfs.dev.read.await[nvme0n1]" became supported 379757:20251005:063645.096 item "ip-10-166-46-70:vfs.dev.write.await[nvme0n1]" became supported 379759:20251005:063648.108 item "ip-10-166-46-154:vfs.dev.read.await[nvme0n1]" became supported 379756:20251005:063649.115 item "ip-10-166-46-154:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063651.933 item "ip-10-166-46-182:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063653.126 item "ip-10-166-46-182:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063705.972 item "ip-10-166-46-136:tomcat_available_memory" became supported 379753:20251005:063705.972 item "ip-10-166-46-78:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063706.956 error reason for "ip-10-166-46-136:tomcat_percent_used_memory" changed: Cannot evaluate function: item "/ip-10-166-46-136/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:063706.956 item "ip-10-166-46-78:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063708.235 item "ip-10-166-46-172:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063708.945 item "ip-10-166-46-172:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063712.115 item "ip-10-166-46-136:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063713.111 item "ip-10-166-46-136:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063716.047 item "ip-10-166-46-75:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063716.952 item "ip-10-166-46-136:tomcat_used_memory" became supported 379753:20251005:063716.952 item "ip-10-166-46-75:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063723.951 item "ip-10-166-46-187:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063725.123 item "ip-10-166-46-187:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063736.069 item "ip-10-166-46-79:vfs.dev.read.await[nvme0n1]" became supported 379753:20251005:063737.002 item "ip-10-166-46-79:vfs.dev.write.await[nvme0n1]" became supported 379753:20251005:063751.037 item "ip-10-166-46-75:tomcat_available_memory" became supported 379753:20251005:063752.193 error reason for "ip-10-166-46-75:tomcat_percent_used_memory" changed: Cannot evaluate function: item "/ip-10-166-46-75/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:063802.054 item "ip-10-166-46-75:tomcat_used_memory" became supported 379753:20251005:063830.202 item "ip-10-166-46-172:tomcat_available_memory" became supported 379753:20251005:063831.100 error reason for "ip-10-166-46-172:tomcat_percent_used_memory" changed: Cannot evaluate function: item "/ip-10-166-46-172/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:063836.107 error reason for "ip-10-166-46-187:tomcat_percent_used_memory" changed: Cannot evaluate function: item "/ip-10-166-46-187/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379755:20251005:063841.035 item "ip-10-166-46-172:tomcat_used_memory" became supported 379758:20251005:063846.068 item "ip-10-166-46-187:tomcat_used_memory" became supported 379753:20251005:063915.145 item "ip-10-166-46-70:tomcat_available_memory" became supported 379759:20251005:063926.108 item "ip-10-166-46-70:tomcat_used_memory" became supported 379753:20251005:063955.112 item "ip-10-166-46-72:tomcat_available_memory" became supported 379757:20251005:063956.143 error reason for "ip-10-166-46-72:tomcat_percent_used_memory" changed: Cannot evaluate function: item "/ip-10-166-46-72/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251005:064000.123 item "ip-10-166-46-182:tomcat_available_memory" became supported 379753:20251005:064001.123 error reason for "ip-10-166-46-182:tomcat_percent_used_memory" changed: Cannot evaluate function: item "/ip-10-166-46-182/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379757:20251005:064006.204 item "ip-10-166-46-72:tomcat_used_memory" became supported 379753:20251005:064011.143 item "ip-10-166-46-182:tomcat_used_memory" became supported 379753:20251005:064041.171 item "ip-10-166-46-78:tomcat_percent_used_memory" became supported 379753:20251005:064121.230 item "ip-10-166-46-79:tomcat_percent_used_memory" became supported 379753:20251005:064126.229 item "ip-10-166-46-154:tomcat_percent_used_memory" became supported 379753:20251005:064206.256 item "ip-10-166-46-136:tomcat_percent_used_memory" became supported 379753:20251005:064251.392 item "ip-10-166-46-75:tomcat_percent_used_memory" became supported 379753:20251005:064331.427 item "ip-10-166-46-172:tomcat_percent_used_memory" became supported 379753:20251005:064336.528 item "ip-10-166-46-187:tomcat_percent_used_memory" became supported 379753:20251005:064416.409 item "ip-10-166-46-70:tomcat_percent_used_memory" became supported 379753:20251005:064456.453 item "ip-10-166-46-72:tomcat_percent_used_memory" became supported 379758:20251005:064501.498 item "ip-10-166-46-182:tomcat_percent_used_memory" became supported 379857:20251005:070001.178 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"a3bbc05d-14c6-496f-87fe-e0e2b81c6100"}. 379785:20251005:070001.201 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"97b01e5b-c103-4853-828b-b7fb916a58ed"}. 379868:20251005:073000.977 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"c5d81bcd-7ab2-458f-bd7d-3d5691ee6ded"}. 379825:20251005:073001.072 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b256d0b2-9b1a-4111-9bf3-dd0da81b9a0d"}. 379743:20251005:073610.715 executing housekeeper 379743:20251005:073804.958 housekeeper [deleted 309049 hist/trends, 7007 items/triggers, 10 events, 13 problems, 0 sessions, 0 alarms, 2873 audit, 0 autoreg_host, 0 records in 114.237366 sec, idle for 1 hour(s)] 379925:20251005:075828.902 failed to accept an incoming connection: from 10.166.53.106: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379793:20251005:080001.115 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"2e5876d4-4a33-43af-86f6-6a82be6d5021"}. 379870:20251005:080001.189 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"13085bf7-f23a-4806-9ae4-f6fc36dff198"}. 379807:20251005:083000.425 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"3ca6d8ba-cbe7-4fb8-bccf-f18babed1101"}. 379851:20251005:083000.707 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b46429ca-744d-4f1f-85f8-a44b66570b42"}. 379743:20251005:083805.026 executing housekeeper 379743:20251005:084006.120 housekeeper [deleted 383918 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 132 audit, 0 autoreg_host, 0 records in 121.089843 sec, idle for 1 hour(s)] 379932:20251005:085432.411 failed to accept an incoming connection: from 10.166.47.185: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379777:20251005:090001.288 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"9a3c1a29-3b43-4fde-8e82-051a9554abbd"}. 379863:20251005:090001.348 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"7263dd29-df51-40f1-b667-0618f16c04f4"}. 379822:20251005:093001.185 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"253a2f94-fc1b-4801-bb8d-6010d166b8d9"}. 379824:20251005:093001.222 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"e29f9708-2f42-4c65-acd1-1fbb29225b7a"}. 379743:20251005:094006.181 executing housekeeper 379743:20251005:094220.891 housekeeper [deleted 419132 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 25 audit, 0 autoreg_host, 0 records in 134.706036 sec, idle for 1 hour(s)] 379809:20251005:100000.813 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"ee5ca8a0-a9bd-4cfc-bffb-690728fe3cb9"}. 379773:20251005:100000.855 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"ccb0d169-794e-4ba3-9be9-1f2c928a7602"}. 379753:20251005:101208.656 item "ip-10-166-44-182:web.page.regexp[https://{$NL_DNS}/newspapers?sort=dsc&formType=basic&alltext=Smith&nagios_app={HOST.IP},,,Showing Results,,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379755:20251005:101636.028 item "ip-10-166-44-182:web.page.regexp[https://{$NL_DNS}/newspapers?sort=dsc&formType=basic&alltext=Smith&nagios_app={HOST.IP},,,Showing Results,,]" became supported 379925:20251005:102429.000 failed to accept an incoming connection: from 10.166.47.150: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379846:20251005:103001.305 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"3f8737d5-53c4-43eb-b1d4-0f40d2537dba"}. 379782:20251005:103001.332 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"a8f952bf-d5a8-492a-9f79-be057850d797"}. 379743:20251005:104220.992 executing housekeeper 379743:20251005:104434.487 housekeeper [deleted 439428 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 999 audit, 0 autoreg_host, 0 records in 133.489390 sec, idle for 1 hour(s)] 379758:20251005:105701.237 item "ip-10-166-44-182:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379843:20251005:110001.150 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"5b9aa644-1e98-4770-83a7-f2a4caabd6d8"}. 379835:20251005:110001.181 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"d185ac53-5510-4d21-8909-427c0561c06c"}. 379753:20251005:110132.175 item "ip-10-166-44-182:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became supported 379819:20251005:113000.734 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"2a9c863e-4622-4dd8-8a73-e23f3ed8ab70"}. 379840:20251005:113000.741 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"280a99f3-0534-443b-a4d7-2a8d44496cb6"}. 379743:20251005:114434.588 executing housekeeper 379743:20251005:114649.168 housekeeper [deleted 440138 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 33 audit, 0 autoreg_host, 0 records in 134.573440 sec, idle for 1 hour(s)] 379858:20251005:120000.789 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"aba19331-b567-4f1f-adb2-1a70839e87d4"}. 379857:20251005:120001.092 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"858d256d-028b-410f-a1f2-da3fdbdd8ad2"}. 379860:20251005:123000.484 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"1a5261a3-0481-4099-914e-9118167f3e3b"}. 379784:20251005:123000.617 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"ac09caa8-cebb-4247-ba96-7129c2fef830"}. 379743:20251005:124649.205 executing housekeeper 379743:20251005:124902.153 housekeeper [deleted 440569 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 9 audit, 0 autoreg_host, 0 records in 132.941873 sec, idle for 1 hour(s)] 379929:20251005:125516.611 failed to accept an incoming connection: from 10.166.47.150: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379818:20251005:130001.070 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"9eb7f18e-cd35-41e8-901e-36f57f6cae63"}. 379794:20251005:130001.093 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"e9e99a03-c837-4b5d-ac45-db1b2c5226d7"}. 379717:20251005:132551.276 cannot get secrets for path "data/emos_secrets": Cannot perform request: Empty reply from server 379824:20251005:133000.680 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"bff414a2-ef95-49f6-a011-07f24aa8c845"}. 379865:20251005:133000.706 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"0068a58e-5a2a-4533-a8e1-e474abf5e5a8"}. 379743:20251005:134902.165 executing housekeeper 379743:20251005:135116.087 housekeeper [deleted 439830 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 2 audit, 0 autoreg_host, 0 records in 133.917340 sec, idle for 1 hour(s)] 379852:20251005:140000.771 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"c9c21200-92e0-480a-a789-f88ea4ec0004"}. 379826:20251005:140000.786 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"945b96f1-5e87-449a-8303-a8c4e8d60952"}. 379820:20251005:143000.710 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b88c3bb2-e9d6-4220-9e06-1536d99f227c"}. 379778:20251005:143000.726 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"e96a5a28-964a-407d-9151-c95f79177c38"}. 379753:20251005:144121.237 item "ip-10-166-44-164:web.page.regexp[https://{$OA_DNS}/obituaries?fname=john&nagios_app={HOST.IP},,,{$POSITIVE},,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379753:20251005:144552.355 item "ip-10-166-44-164:web.page.regexp[https://{$OA_DNS}/obituaries?fname=john&nagios_app={HOST.IP},,,{$POSITIVE},,]" became supported 379743:20251005:145116.108 executing housekeeper 379753:20251005:145154.262 error reason for "ip-10-166-44-149:nbSSLcert" changed: Value of type "string" is not suitable for value type "Numeric (unsigned)". Value "-330" 379743:20251005:145330.057 housekeeper [deleted 440441 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 34 audit, 0 autoreg_host, 0 records in 133.944750 sec, idle for 1 hour(s)] 379795:20251005:150001.101 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"58bf9015-4ff1-4011-8118-6352916a2266"}. 379841:20251005:150001.110 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"4625ce4f-87db-4931-bb84-819c07574e4a"}. 379801:20251005:153000.845 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b00de494-4cd2-4b05-a43f-0e7d6a443c28"}. 379833:20251005:153000.902 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"9ac64c51-a0e7-4ddf-8039-854568c2fe2c"}. 379743:20251005:155330.152 executing housekeeper 379743:20251005:155544.444 housekeeper [deleted 439559 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 autoreg_host, 0 records in 134.286361 sec, idle for 1 hour(s)] 379804:20251005:160000.709 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"1b423c50-7437-4674-9a43-0faaa101a116"}. 379822:20251005:160000.820 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"7489e32d-cadb-4361-bdf7-27a8834141ee"}. 379823:20251005:163001.054 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"9a641783-9ce8-443a-84df-1990de0f7179"}. 379807:20251005:163001.081 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"18f0da69-1905-428b-bdca-3e211206dba4"}. 379743:20251005:165544.501 executing housekeeper 379743:20251005:165756.844 housekeeper [deleted 441151 hist/trends, 0 items/triggers, 0 events, 2 problems, 0 sessions, 0 alarms, 34 audit, 0 autoreg_host, 0 records in 132.339012 sec, idle for 1 hour(s)] 379800:20251005:170000.773 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"3ef8e8e9-02cd-40f4-99af-abb70d9fd290"}. 379865:20251005:170000.896 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"1b7f7124-7fb6-4f73-9847-23cd59b25016"}. 379863:20251005:173000.743 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"56fb7b1d-849b-409a-83e4-a0d657d6c4f1"}. 379832:20251005:173001.195 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"a3da0732-598b-4e23-9b3e-fa003f041ec3"}. 379743:20251005:175756.942 executing housekeeper 379835:20251005:180000.764 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"29806b38-784b-454a-b9cf-94c8c0243a36"}. 379857:20251005:180000.828 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b92bf229-9fdf-4a22-a621-04fbc7957678"}. 379743:20251005:180013.811 housekeeper [deleted 439547 hist/trends, 0 items/triggers, 0 events, 2 problems, 0 sessions, 0 alarms, 0 audit, 0 autoreg_host, 0 records in 136.864803 sec, idle for 1 hour(s)] 379753:20251005:181453.205 item "ip-10-166-44-99:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379753:20251005:181924.228 item "ip-10-166-44-99:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became supported 379858:20251005:183000.910 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"6cbb07c5-addb-4a2b-b399-7dd844a9ae64"}. 379832:20251005:183001.108 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"610bb6b1-d9ea-4979-9ea8-b53aff20a33f"}. 379819:20251005:190000.706 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"adb2049a-94e4-45a5-a998-a3acc2426b84"}. 379851:20251005:190000.720 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"0ba4f3b1-fe63-49d0-81af-98d0cdfabbf4"}. 379743:20251005:190013.851 executing housekeeper 379743:20251005:190218.456 housekeeper [deleted 369413 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 23 audit, 0 autoreg_host, 0 records in 124.600625 sec, idle for 1 hour(s)] 379932:20251005:192337.478 failed to accept an incoming connection: from 10.166.47.185: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379753:20251005:192744.240 item "ip-10-166-44-76:web.page.regexp[https://{$GB_DNS}/doc/ssdi/news/123A144EC446A678?nagios_app={HOST.IP},,,Smith,,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379867:20251005:193000.788 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"605e48e6-aff5-4c89-871f-8593dfa4769e"}. 379829:20251005:193000.796 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"390e2953-ea26-4b73-8b14-b9a0616fea4e"}. 379753:20251005:193215.287 item "ip-10-166-44-76:web.page.regexp[https://{$GB_DNS}/doc/ssdi/news/123A144EC446A678?nagios_app={HOST.IP},,,Smith,,]" became supported 379851:20251005:200000.804 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"1fb9c554-1dcc-4151-ba7f-b4f4c28b43a3"}. 379822:20251005:200000.832 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"c6e64eed-d70c-4de0-9ced-907f9547136d"}. 379743:20251005:200218.557 executing housekeeper 379924:20251005:200320.932 failed to accept an incoming connection: from 10.166.47.148: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379743:20251005:200406.683 housekeeper [deleted 348097 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 162 audit, 0 autoreg_host, 0 records in 108.120255 sec, idle for 1 hour(s)] 379818:20251005:203000.726 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"838ce944-d6c5-495c-89d7-0c97af76e881"}. 379856:20251005:203000.750 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"fcd067cf-d324-409f-9714-ecf8ca2a15bb"}. 379781:20251005:210001.387 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b3285b1e-d870-446d-bd7c-a76872127293"}. 379814:20251005:210001.395 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"79d3649c-edc9-442e-9613-81d65f881f23"}. 379743:20251005:210406.717 executing housekeeper 379743:20251005:210548.697 housekeeper [deleted 338483 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 6 audit, 0 autoreg_host, 0 records in 101.976141 sec, idle for 1 hour(s)] 379827:20251005:213000.547 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b0308606-e8f4-4613-a243-6622b2091e8b"}. 379837:20251005:213000.698 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"d9ba25aa-6385-4876-82b3-b5c1b1010032"}. 379756:20251005:213116.346 item "ip-10-166-44-164:web.page.regexp[https://{$GB_DNS}/doc/ssdi/news/123A144EC446A678?nagios_app={HOST.IP},,,Smith,,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379753:20251005:213547.326 item "ip-10-166-44-164:web.page.regexp[https://{$GB_DNS}/doc/ssdi/news/123A144EC446A678?nagios_app={HOST.IP},,,Smith,,]" became supported 379822:20251005:220000.688 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"9425296d-6ff1-4cec-9855-a207fb02fb57"}. 379835:20251005:220000.696 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b505c3e7-ffef-4b76-983e-f8a22f713557"}. 379743:20251005:220548.715 executing housekeeper 379743:20251005:220722.567 housekeeper [deleted 292108 hist/trends, 0 items/triggers, 0 events, 3 problems, 0 sessions, 0 alarms, 3 audit, 0 autoreg_host, 0 records in 93.848569 sec, idle for 1 hour(s)] 379927:20251005:222410.058 failed to accept an incoming connection: from 10.166.47.138: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379813:20251005:223000.724 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"7f64646a-ea5d-4668-bff5-2f79f6670f43"}. 379777:20251005:223000.761 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"40c43a70-74b4-47ec-bced-e21784dcde98"}. 379847:20251005:230000.794 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"c82f606a-0eed-41ae-9839-74fe4619a03c"}. 379801:20251005:230000.814 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"eaf004ed-1426-40bf-bb66-973769a743d2"}. 379743:20251005:230722.653 executing housekeeper 379743:20251005:230856.685 housekeeper [deleted 294065 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 53 audit, 0 autoreg_host, 0 records in 94.026573 sec, idle for 1 hour(s)] 379717:20251005:231739.140 cannot get secrets for path "data/marklogic_secrets": Cannot perform request: Empty reply from server 379753:20251005:231956.434 item "ip-10-166-46-83:vfs.fs.dependent[/tmp/log4j-hotpatch.Hc9fT1ClL6,data]" became not supported: Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0.000000,"pused":... 1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/tmp/log4j-hotpatch.Hc9fT1ClL6')].first()": no data matches the specified path 379753:20251005:231956.434 item "ip-10-166-46-83:vfs.fs.dependent.inode[/tmp/log4j-hotpatch.Hc9fT1ClL6,pfree]" became not supported: Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0.000000,"pused":... 1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/tmp/log4j-hotpatch.Hc9fT1ClL6')].first()": no data matches the specified path 379753:20251005:231956.434 item "ip-10-166-46-83:vfs.fs.dependent.size[/tmp/log4j-hotpatch.Hc9fT1ClL6,free]" became not supported: Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0.000000,"pused":... 1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/tmp/log4j-hotpatch.Hc9fT1ClL6')].first()": no data matches the specified path 379753:20251005:231956.434 item "ip-10-166-46-83:vfs.fs.dependent.size[/tmp/log4j-hotpatch.Hc9fT1ClL6,pused]" became not supported: Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0.000000,"pused":... 1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/tmp/log4j-hotpatch.Hc9fT1ClL6')].first()": no data matches the specified path 379753:20251005:231956.434 item "ip-10-166-46-83:vfs.fs.dependent.size[/tmp/log4j-hotpatch.Hc9fT1ClL6,total]" became not supported: Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0.000000,"pused":... 1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/tmp/log4j-hotpatch.Hc9fT1ClL6')].first()": no data matches the specified path 379753:20251005:231956.434 item "ip-10-166-46-83:vfs.fs.dependent.size[/tmp/log4j-hotpatch.Hc9fT1ClL6,used]" became not supported: Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0.000000,"pused":... 1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/tmp/log4j-hotpatch.Hc9fT1ClL6')].first()": no data matches the specified path 379753:20251005:231956.434 item "ip-10-166-46-83:vfs.fs.dependent[/tmp/log4j-hotpatch.Hc9fT1ClL6,readonly]" became not supported: Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0.000000,"pused":... 1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/tmp/log4j-hotpatch.Hc9fT1ClL6')].first()": no data matches the specified path 379795:20251005:233000.787 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"a99fe11b-2790-4d18-a4a9-95d470f0af95"}. 379849:20251005:233000.790 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"243cb85a-3046-41f7-8e9a-0b2207a86620"}. 379807:20251006:000000.725 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"b2d45ce0-6a09-4ebd-8c5b-2ee799da595f"}. 379868:20251006:000000.727 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"c16af64e-1427-48a4-bd9f-3751cf69abbe"}. 379743:20251006:000856.786 executing housekeeper 379753:20251006:000953.423 item "ip-10-166-44-99:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379743:20251006:001032.756 housekeeper [deleted 293899 hist/trends, 2200 items/triggers, 0 events, 18 problems, 0 sessions, 0 alarms, 325 audit, 0 autoreg_host, 0 records in 95.963251 sec, idle for 1 hour(s)] 379753:20251006:001424.159 item "ip-10-166-44-99:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became supported 379833:20251006:003000.636 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"e45be934-5f62-47b3-8f9b-c598104c2c62"}. 379809:20251006:003000.676 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"1232b1f3-05f3-4bdd-84aa-ac30057702ee"}. 379847:20251006:010001.356 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"5ae63c0c-19a0-4e3e-8143-975b9c48c690"}. 379830:20251006:010001.381 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"4ae64393-7ac2-4ffc-b5d6-da85c0ffdc45"}. 379743:20251006:011032.856 executing housekeeper 379743:20251006:011207.511 housekeeper [deleted 294797 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 6 audit, 0 autoreg_host, 0 records in 94.650292 sec, idle for 1 hour(s)] 379865:20251006:013000.670 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"369336ea-04b4-420d-9cda-ea875adeede9"}. 379801:20251006:013000.695 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"89072d13-865b-4948-9ee4-f79d2efcbd32"}. 379930:20251006:014631.004 failed to accept an incoming connection: from 10.166.47.87: unspecified certificate verification error: TLS handshake set result code to 5 (SSL_ERROR_SYSCALL):[104] Connection reset by peer: 379797:20251006:020001.197 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"727c8bdc-d986-4df9-9bd1-b9d8bdb7c2eb"}. 379852:20251006:020001.286 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"82d23b11-9e1d-4d78-8bc2-2e177b280e78"}. 379743:20251006:021207.611 executing housekeeper 379743:20251006:021343.415 housekeeper [deleted 294014 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 7 audit, 0 autoreg_host, 0 records in 95.799158 sec, idle for 1 hour(s)] 379790:20251006:023000.491 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"6de37b66-47b9-4bbe-8596-06b13c5edcac"}. 379858:20251006:023000.514 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"f561bddb-0c31-415c-a485-f16be8b95e10"}. 379826:20251006:030001.106 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"6f063a01-5c4d-4d9e-b958-c9a989b9ac06"}. 379857:20251006:030001.162 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"a3782905-e8a6-4294-9b36-693246a46b8f"}. 379743:20251006:031343.488 executing housekeeper 379743:20251006:031519.838 housekeeper [deleted 294263 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 8 audit, 0 autoreg_host, 0 records in 96.345356 sec, idle for 1 hour(s)] 379849:20251006:033000.864 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"5c90ff78-182d-4252-8941-98d001088c5a"}. 379857:20251006:033000.952 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"4046c9a3-f454-4c75-b53c-169fd8222fd5"}. 379822:20251006:040000.364 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"8c6137f4-0db0-46a7-b8a7-f29e922d59db"}. 379813:20251006:040000.686 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"1c9e865e-eea8-4df6-a579-b2f46592b30b"}. 379753:20251006:041409.313 item "ip-10-166-44-181:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became not supported: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379743:20251006:041519.924 executing housekeeper 379743:20251006:041654.074 housekeeper [deleted 294595 hist/trends, 0 items/triggers, 0 events, 1 problems, 0 sessions, 0 alarms, 4 audit, 0 autoreg_host, 0 records in 94.145543 sec, idle for 1 hour(s)] 379753:20251006:041840.257 item "ip-10-166-44-181:web.page.regexp[https://{$GB_DNS}/explore/all?lname=smith&nagios_app={HOST.IP},,,Smith,,]" became supported 379861:20251006:043000.670 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"85a5f0a7-ad4c-48ca-aa36-65c15994d07d"}. 379841:20251006:043000.674 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"04a74bb2-f183-4350-ba66-8454cc8a7887"}. 379773:20251006:050000.656 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"708864c2-9ebd-40b6-a7ef-1050099f0038"}. 379800:20251006:050000.709 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"2e211a90-96c0-43e9-800b-96e1d23a69f9"}. 379928:20251006:050342.258 cannot send list of active checks to "10.166.26.152": host [ip-10-166-26-152] not found 379743:20251006:051654.105 executing housekeeper 379743:20251006:051827.714 housekeeper [deleted 293595 hist/trends, 0 items/triggers, 0 events, 4 problems, 0 sessions, 0 alarms, 176 audit, 0 autoreg_host, 0 records in 93.605975 sec, idle for 1 hour(s)] 379851:20251006:053000.691 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"d5b8fb1d-33d2-45e6-b86c-92d7d9ada210"}. 379801:20251006:053000.702 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"19202fb7-cb0e-4f78-b488-365048d0546c"}. 379810:20251006:060000.514 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"9e2b8f77-9ab8-46d3-bea6-fa601113ad79"}. 379869:20251006:060000.617 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"6f4a5a89-fb10-4a80-b09a-b92196d797f0"}. 379931:20251006:060346.337 cannot send list of active checks to "10.166.40.136": host [ip-10-166-40-136] not found 379924:20251006:060355.147 cannot send list of active checks to "10.166.40.78": host [ip-10-166-40-78] not found 379753:20251006:060413.659 item "ip-10-166-40-78:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:060414.411 item "ip-10-166-40-78:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251006:060424.389 item "ip-10-166-40-78:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-40-78/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379999:20251006:060425.471 enabling Zabbix agent checks on host "ip-10-166-40-78": interface became available 379755:20251006:060458.230 item "ip-10-166-40-78:camstest" became not supported: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379759:20251006:060506.256 item "ip-10-166-40-78:web.page.regexp[{HOST.IP},/gateway2/platform/SimpleSearch?product=AWNB&navoutput=none&maxhits=10&haystack=&p_text_alltext-0=jones&p_field_alltext-0=alltext&p_field_dti-0=dti&p_text_dti-0=2012-10-11T09%3A31%3A05+-+2012-10-12T09%3A30%3A38&p_params_dti-0=date%3AB%2CE&api_key=pltfrm&cust_auth_type=userpw&cust_auth=apitest1%7Capitest1&readCache=false,9090,hitlist,,]" became not supported: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379753:20251006:060507.242 item "ip-10-166-40-78:web.page.regexp[{HOST.IP},/gateway2/platform/favorites/Get?api_key=pltfrm&cust_auth_type=userpw&cust_auth=apitest1%7Capitest1,9090,"favorite:states",,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379753:20251006:060508.265 item "ip-10-166-40-78:web.page.regexp[{HOST.IP},/gateway2/platform/retrievedoc?api_key=pltfrm&cust_auth_type=userpw&cust_auth=apitest1%7Capitest1&product=WORLDNEWS&docid=news/1170C244A5D1F9F0,9090,"PLYMOUTH, N.H.",,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379753:20251006:060509.239 item "ip-10-166-40-78:web.page.regexp[{HOST.IP},/gateway2/platform/retrievedoc?{$DOCIMG.PARAMS},9090,"Maple Sugar And Syrup Recipes",,]" became not supported: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379999:20251006:060518.228 Zabbix agent item "web.page.regexp[ {HOST.IP},/seeker/search?engine=fast&type=triplet&product=OBIT&p_text_search-0=smith&offset=1&maxhits=10&sortfield=ymd:d,9090,internalid,,]" on host "ip-10-166-46-98" failed: first network error, wait for 15 seconds 379759:20251006:061041.252 item "ip-10-166-44-83:web.page.regexp[https://{$OA_DNS}/obituaries?fname=john&nagios_app={HOST.IP},,,{$POSITIVE},,]" became not supported: Cannot perform request: Operation timed out after 30001 milliseconds with 0 bytes received 379753:20251006:061512.290 item "ip-10-166-44-83:web.page.regexp[https://{$OA_DNS}/obituaries?fname=john&nagios_app={HOST.IP},,,{$POSITIVE},,]" became supported 379743:20251006:061827.797 executing housekeeper 379743:20251006:062039.172 housekeeper [deleted 294183 hist/trends, 1980359 items/triggers, 2 events, 2 problems, 0 sessions, 0 alarms, 2028 audit, 12 autoreg_host, 0 records in 131.369830 sec, idle for 1 hour(s)] 379776:20251006:063000.608 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"0388b8d1-2e7d-4e96-9534-dca16ffda8e4"}. 379819:20251006:063000.684 [ AWS ELB Target groups ] ERROR: Request failed with status code 403: {"Error":{"Code":"SignatureDoesNotMatch","Message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.","Type":"Sender"},"RequestId":"8cbdc3a6-5405-429a-b0d6-33768813fe34"}. 379753:20251006:063058.229 item "ip-10-166-46-83:tomcat_serverinfo" became not supported: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379753:20251006:063101.229 item "ip-10-166-46-83:tomcat_status" became not supported: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379753:20251006:063101.229 error reason for "ip-10-166-46-83:tomcat_total_memory" changed: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379753:20251006:063101.229 error reason for "ip-10-166-46-83:tomcat_max_memory" changed: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379753:20251006:063101.229 error reason for "ip-10-166-46-83:tomcat_free_memory" changed: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379753:20251006:063101.229 error reason for "ip-10-166-46-83:tomcat_busythreads" changed: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379753:20251006:063106.283 item "ip-10-166-46-83:tomcat_status_code" became not supported: Cannot perform request: Operation timed out after 30000 milliseconds with 0 bytes received 379926:20251006:063419.709 cannot send list of active checks to "10.166.46.74": host [ip-10-166-46-74] not found 379923:20251006:063420.499 cannot send list of active checks to "10.166.46.106": host [ip-10-166-46-106] not found 379924:20251006:063421.002 cannot send list of active checks to "10.166.46.168": host [ip-10-166-46-168] not found 379926:20251006:063421.532 cannot send list of active checks to "10.166.46.117": host [ip-10-166-46-117] not found 379930:20251006:063422.091 cannot send list of active checks to "10.166.46.165": host [ip-10-166-46-165] not found 379753:20251006:063422.323 item "ip-10-166-46-74:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379925:20251006:063422.573 cannot send list of active checks to "10.166.46.163": host [ip-10-166-46-163] not found 379932:20251006:063423.062 cannot send list of active checks to "10.166.46.88": host [ip-10-166-46-88] not found 379753:20251006:063423.326 item "ip-10-166-46-74:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379926:20251006:063423.529 cannot send list of active checks to "10.166.46.190": host [ip-10-166-46-190] not found 379927:20251006:063424.045 cannot send list of active checks to "10.166.46.110": host [ip-10-166-46-110] not found 379928:20251006:063424.523 cannot send list of active checks to "10.166.46.179": host [ip-10-166-46-179] not found 379753:20251006:063431.492 item "ip-10-166-46-110:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379999:20251006:063431.529 enabling Zabbix agent checks on host "ip-10-166-46-165": interface became available 379999:20251006:063431.599 enabling Zabbix agent checks on host "ip-10-166-46-168": interface became available 379999:20251006:063432.033 enabling Zabbix agent checks on host "ip-10-166-46-179": interface became available 379753:20251006:063432.339 item "ip-10-166-46-88:tomcat_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_max_memory)-last(//tomcat_available_memory)". 379753:20251006:063432.339 item "ip-10-166-46-110:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379760:20251006:063433.529 item "ip-10-166-46-74:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-74/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379999:20251006:063434.441 enabling Zabbix agent checks on host "ip-10-166-46-88": interface became available 379999:20251006:063434.562 enabling Zabbix agent checks on host "ip-10-166-46-74": interface became available 379753:20251006:063436.346 item "ip-10-166-46-117:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:063437.398 item "ip-10-166-46-106:tomcat_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_available_memory)". 379753:20251006:063437.398 item "ip-10-166-46-117:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251006:063438.381 enabling Zabbix agent checks on host "ip-10-166-46-106": interface became available 379753:20251006:063442.411 item "ip-10-166-46-110:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-110/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379999:20251006:063443.400 enabling Zabbix agent checks on host "ip-10-166-46-110": interface became available 379753:20251006:063446.465 item "ip-10-166-46-163:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:063447.422 item "ip-10-166-46-117:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-117/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251006:063447.422 item "ip-10-166-46-163:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251006:063448.389 enabling Zabbix agent checks on host "ip-10-166-46-117": interface became available 379753:20251006:063456.566 item "ip-10-166-46-190:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:063457.440 item "ip-10-166-46-163:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-163/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251006:063457.440 item "ip-10-166-46-190:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251006:063458.383 enabling Zabbix agent checks on host "ip-10-166-46-163": interface became available 379753:20251006:063501.510 item "ip-10-166-46-168:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:063502.396 item "ip-10-166-46-168:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251006:063506.690 item "ip-10-166-46-179:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:063507.458 item "ip-10-166-46-190:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-190/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251006:063507.458 item "ip-10-166-46-179:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379999:20251006:063508.294 enabling Zabbix agent checks on host "ip-10-166-46-190": interface became available 379753:20251006:063511.697 item "ip-10-166-46-165:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:063512.466 item "ip-10-166-46-168:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-168/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251006:063512.466 item "ip-10-166-46-165:tomcat_percent_used_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251006:063517.549 item "ip-10-166-46-179:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-179/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251006:063521.875 item "ip-10-166-46-88:tomcat_available_memory" became not supported: Cannot evaluate function: not enough data at "last(//tomcat_free_memory)+last(//tomcat_max_memory)-last(//tomcat_total_memory)". 379753:20251006:063522.487 item "ip-10-166-46-165:tomcat_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-165/tomcat_available_memory" is not supported at "last(//tomcat_available_memory)". 379753:20251006:063522.487 item "ip-10-166-46-88:tomcat_percent_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-88/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251006:063527.460 item "ip-10-166-46-106:tomcat_percent_used_memory" became not supported: Cannot evaluate function: item "/ip-10-166-46-106/tomcat_used_memory" is not supported at "last(//tomcat_used_memory)/last(//tomcat_max_memory)". 379753:20251006:063528.232 item "ip-10-166-46-83:tomcat_serverinfo" became supported 379753:20251006:063531.232 item "ip-10-166-46-83:tomcat_status" became supported 379753:20251006:063531.232 error reason for "ip-10-166-46-83:tomcat_total_memory" changed: Preprocessing failed for: ..