Ad Widget

**dimir** · 17-05-2021, 11:56

the message in the log from server:
cannot send list of active checks to "200.16.161.26": host [USS-NotebookBerro] not found

Does anyone know what can cause this problem and how to resolve it?
***happens with some hosts and others don't

Active agent's Hostname configuration parameter (USS-NotebookBerro) must match the name of this host in Frontend configuration. Otherwise server will not accept its requests.

**solution** · 17-05-2021, 15:10

Thanks for the reply.
But this has already been checked and the hostname in .conf is the same as the hostname in zabbix server, I have already changed it for testing and even so the problem is the same:

1208:20210514:104241.083 sending [{"request":"active checks","host":"USS-NotebookBerro"}]
1208:20210514:104241.087 active check configuration update from [server.no-ip.org:10051] started to fail (SSL_write() timed out)
1208:20210514:104241.091 End of refresh_active_checks():FAIL

**dimir** · 17-05-2021, 15:31

This looks like encryption configuration problem. Could you post the appropriate part from zabbix server log file? Where this agent connects.

**solution** · 17-05-2021, 17:13

I changed the hostname just for testing:

SERVER:
Log Server:
cat /var/log/zabbix/zabbix_server.log | grep -i 200.16.161.26
5004:20210517:120133.970 cannot send list of active checks to "200.16.161.26": host [USSContabil-NotebookBeatriz] not found
5004:20210517:120133.970 SSL_shutdown() with 200.16.161.26 set result code to 5:

Print host config in attachment

Log (verb default) in host:
12068:20210517:120135.965 Starting Zabbix Agent [USSContabil-NotebookBeatriz]. Zabbix 5.2.6 (revision 798506596c).
12068:20210517:120135.973 **** Enabled features ****
12068:20210517:120135.978 IPv6 support: YES
12068:20210517:120135.984 TLS support: YES
12068:20210517:120135.989 **************************
12068:20210517:120135.994 using configuration file: C:\zabbix\conf\zabbix_agentd.conf
12068:20210517:120136.531 agent #0 started [main process]
3452:20210517:120136.537 agent #2 started[listener #1]
11772:20210517:120136.542 agent #3 started[listener #2]
9516:20210517:120136.547 agent #5 started [active checks #1]
8732:20210517:120136.553 agent #4 started[listener #3]
6756:20210517:120136.558 agent #1 started [collector]
9516:20210517:120136.912 active check configuration update from [server.no-ip.org:10051] started to fail (SSL_write() timed out)

Host Config:
# This is a configuration file for Zabbix agent service (Windows)
# To get more information about Zabbix, visit http://www.zabbix.com

############ GENERAL PARAMETERS #################

### Option: LogFile
# Log file name for LogType 'file' parameter.
#
# Mandatory: no
# Default:
# LogFile=

LogFile=C:\zabbix\zabbix_log.log

### Option: DebugLevel
# Specifies debug level:
# 0 - basic information about starting and stopping of Zabbix processes
# 1 - critical information
# 2 - error information
# 3 - warnings
# 4 - for debugging (produces lots of information)
# 5 - extended debugging (produces even more information)
#
# Mandatory: no
# Range: 0-5
# Default:
# DebugLevel=4

### Option: EnableRemoteCommands
# Whether remote commands from Zabbix server are allowed.
# 0 - not allowed
# 1 - allowed
#
# Mandatory: no
# Default:
EnableRemoteCommands=1

### Option: LogRemoteCommands
# Enable logging of executed shell commands as warnings.
# 0 - disabled
# 1 - enabled
#
# Mandatory: no
# Default:
LogRemoteCommands=1

##### Passive checks related

### Option: Server
# List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers.
# Incoming connections will be accepted only from the hosts listed here.
# If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.
# '0.0.0.0/0' can be used to allow any IPv4 address.
# Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain
#
# Mandatory: no
# Default:
# Server=

Server=server.no-ip.org

##### Active checks related

### Option: ServerActive
# List of comma delimited IP

ort (or hostname

ort) pairs of Zabbix servers for active checks.
# If port is not specified, default port is used.
# IPv6 addresses must be enclosed in square brackets if port for that host is specified.
# If port is not specified, square brackets for IPv6 addresses are optional.
# If this parameter is not specified, active checks are disabled.
# Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
#
# Mandatory: no
# Default:
# ServerActive=

ServerActive=server.no-ip.org

### Option: Hostname
# Unique, case sensitive hostname.
# Required for active checks and must match hostname as configured on the server.
# Value is acquired from HostnameItem if undefined.
#
# Mandatory: no
# Default:
# Hostname=

Hostname=USSContabil-NotebookBeatriz

############ ADVANCED PARAMETERS #################

### Option: Timeout
# Spend no more than Timeout seconds on processing.
#
# Mandatory: no
# Range: 1-30
# Default:
Timeout=30

### Option: Include
# You may include individual files in the configuration file.
#
# Mandatory: no
# Default:
# Include=

# Include=c:\zabbix\zabbix_agentd.userparams.conf
# Include=c:\zabbix\zabbix_agentd.conf.d\
Include=c:\zabbix\zabbix_agentd.conf.d\*.conf

####### USER-DEFINED MONITORED PARAMETERS #######

####### TLS-RELATED PARAMETERS #######

### Option: TLSConnect
# How the agent should connect to server or proxy. Used for active checks.
# Only one value can be specified:
# unencrypted - connect without encryption
# psk - connect using TLS and a pre-shared key
# cert - connect using TLS and a certificate
#
# Mandatory: yes, if TLS certificate or PSK parameters are defined (even for 'unencrypted' connection)
# Default:
TLSConnect=psk

### Option: TLSAccept
# What incoming connections to accept.
# Multiple values can be specified, separated by comma:
# unencrypted - accept connections without encryption
# psk - accept connections secured with TLS and a pre-shared key
# cert - accept connections secured with TLS and a certificate
#
# Mandatory: yes, if TLS certificate or PSK parameters are defined (even for 'unencrypted' connection)
# Default:
TLSAccept=psk

### Option: TLSPSKIdentity
# Unique, case sensitive string used to identify the pre-shared key.
#
# Mandatory: no
# Default:
TLSPSKIdentity=zapsk

### Option: TLSPSKFile
# Full pathname of a file containing the pre-shared key.
#
# Mandatory: no
# Default:
# TLSPSKFile=
TLSPSKFile=C:\zabbix\conf\agentkey.psk

**dimir** · 18-05-2021, 14:55

This looks like a popular case of mixing different Zabbix servers/proxies. Do you have multiple Zabbix database, server or proxy instances?

**solution** · 18-05-2021, 15:20

My Zabbix Server is 5.2.6 and I have 20 Proxies 5.2.4.
But these Hosts (there are 5 on different networks) are NOT connected to a proxy.
The connection is: Host <==> Zabbix Server

Out of a total of 1000 Hosts, only these 5 added ones present this problem.

Yesterday we installed a new machine on a new client with Windows 10 20H2 and used the same installer / configuration and is reporting data without problems.

Is there a command you can run on Windows to help identify the cause?

**pah** · 05-11-2021, 20:21

solution : Were you able to solve the problem?

We have exactly the same problem. Only with some devices, too.

If I use the 100% same configuration (same PSKIdentity and Key same hostname, ..) in a test VM, everything works.

Zabbix Server: 5.0.16
OS: Ubuntu 18.04.6

Clients:
Windows 10 21H1
Zabbix Agent 5.0.17 with OpenSSL (MSI)

**pah** · 19-11-2021, 12:46

I created a bug report for this: https://support.zabbix.com/browse/ZBX-20228

**vso** · 26-11-2021, 21:14

What kind of hardware are you using ? Unfortunately issue could not be reproduced locally.

**solution** · 09-12-2021, 20:04

As it happens only on some machines.
It's hard to reproduce, I've tried it on my PC and VM and the error doesn't happen.

In the example above, the hardware/software is:
Dell Laptop
OS: Windows 10 **Fresh Install + Windows Update updated.

Zabbix agent that works:
ONLY Zabbix Agent 3.4.6 or Zabbix Agent 2

**Maxburn** · 22-02-2022, 22:55

OK, I just ran into this also. Started with agent 5.0.15, moved it up to 5.0.20. While doing the upgrade it actually wiped out my client config file and windows service but not the log file. Reinstalled it copying and pasting the config from zabbix server got the client up and running again, with the exact same error.

This was running fine, and it just doesn't now?

Log attached.

Attached Files

zabbixclientSSLtimeout.txt (9.5 KB, 7 views)

**Maxburn** · 22-02-2022, 23:34

Actually this is worse than I thought, I just found a total of six clients doing this, out of about 55 total. They all stopped working with similar log files in above on the same day; February 20th, two days ago.

I just updated and rebooted the zabbix server too, Zabbix 5.0.20 on ubuntu 20.04. Also rebooted the client windows server in above post.

The active check I'm doing is a log count to see how many OpenVPN clients are connected and alert me on disconnections. It's kinda important to us. log.count[C:\Program Files\OpenVPN\log\openvpn-status.log,^client,ANSI,100,all,0]

**Maxburn** · 22-02-2022, 23:49

Solved. Updating to the beta posted below fixed me.

Loading...

https://support.zabbix.com/browse/ZBX-20228?page=com.atlassian.jira.plugin.system.issuetabpanels%3Achangehistory-tabpanel

File; https://support.zabbix.com/secure/at...-openssl-2.zip

**solution** · 23-02-2022, 00:27

i stopped trying and started using zabbix agent 2 as default for new installs.
And I started migrating the old ones too.

Ad Widget

how to solve problem active check update from started to fail (SSL_write() timed out)

how to solve problem active check update from started to fail (SSL_write() timed out)

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment