some clients fail to connect the opsiserver at startup

[EricT]

Hello,

some of the opsi-clients fail to connect the opsiserver at startup, but are manageable using configed and users can install software using the software-kiosk.

The logged error is:
[6] [Nov 11 08:06:33] [ opsiclientd ] ==>>> Failed to process method 'backend_getInterface': [Errno 11001] getaddrinfo failed (JSONRPC.pyo|125)
[3] [Nov 11 08:06:33] [ service connection ] Failed to connect to config server 'https://<fqdn opsi-server>:4447/rpc': [Errno 11001] getaddrinfo failed (OpsiService.pyo|366)

The error 'failed to connect to config server' is clear, but I can't think of the reason why only some of the clients aren't able to connect. Clients receive IP and DNS-servers from DHCP and are using the same subnet.
The problem is seen on some of the freshly installed Windows-clients, which never connected the opsi-server before, but not on all freshly installed clients. It also occurs on a couple of existing clients which didn't have this problem before.

I hope someone has a suggestion why the client can't connnect.

Thanks in advance for your reply.

Regards, Eric

[SisterOfMercy]

What versions are you running?

IE, I'd like to see this output:

Code: Alles auswählen

yum list installed | grep opsi		(or of course the command for your own package manager)

and

Code: Alles auswählen

opsi-package-manager -l | grep opsi

[EricT]

Hi, thanks for your reply.

The output is:
opsi-configed.noarch 4.0.7.6.34-2.9 @home_uibmz_opsi_4.1_stable
opsi-linux-bootimage.noarch 20210903-1.1 @home_uibmz_opsi_4.1_stable
opsi-server.noarch 4.1.1.8-1.5 @home_uibmz_opsi_4.1_stable
opsi-tftp-hpa-server.x86_64 5.2.8-76.1 @home_uibmz_opsi_4.1_stable
opsi-utils.noarch 4.1.1.37-1.1 @home_uibmz_opsi_4.1_stable
opsiconfd.noarch 4.1.1.20-5.1 @home_uibmz_opsi_4.1_stable
opsipxeconfd.noarch 4.1.1.20-3.3 @home_uibmz_opsi_4.1_stable
python-Twisted.x86_64 12.0.0-10.7 @home_uibmz_opsi_opsi40
python-ldaptor.x86_64 0.0.43-16.11 @home_uibmz_opsi_opsi40
python-opsi.noarch 4.1.1.101-1.1 @home_uibmz_opsi_4.1_stable
python-pam.x86_64 0.5.0-4.8 @home_uibmz_opsi_opsi40
zsync.x86_64 0.6.2-5.6 @home_uibmz_opsi_opsi40

and for the packages:
l-opsi-server 4.2.0.5-2 Installs opsi
opsi-client-agent 4.1.1.47-1 opsi.org client agent
opsi-client-kiosk 4.1.1.11-10 Opsi Client Kiosk
opsi-clonezilla 4.2.0.0-1 Clonezilla over opsi
opsi-configed 4.1.9.9.2-2 opsi configed
opsi-linux-client-agent 4.2.0.5-1 opsi.org client agent for Linux
opsi-local-image-backup 4.2.0.1-1 opsi local image backup
opsi-local-image-backup-starter 4.2.0.0-1 opsi template product
opsi-local-image-capture 4.0.7.1-2 opsi local image capture
opsi-local-image-delimage 4.1.0.1-5 opsi local image: delete image
opsi-local-image-opensuse13-2 4.0.7.1-4 OpenSuse 13.2
opsi-local-image-postrestore 4.0.5.1-2 opsi-local-image-postrestore
opsi-local-image-prepare 4.1.0.1-4 opsi local image disk prepare
opsi-local-image-restore 4.2.0.1-1 opsi local image restore
opsi-local-image-sysprep 4.0.6.1-1 opsi-local-image-sysprep
opsi-local-image-ubuntu 4.1.0.0-2 Linux Ubuntu
opsi-local-image-wim-capture 4.2.0.1-2 opsi-wim-capture for opsi-local-image
opsi-local-image-win10 4.2.0.1-4 Windows 10 - 32 Bit
opsi-local-image-win10-capture 4.2.0.1-4 Windows 10 - 32 Bit
opsi-local-image-win10-x64 4.2.0.1-4 Windows 10 - x64
opsi-local-image-win10-x64-capture 4.2.0.1-4 Windows 10 - x64
opsi-local-image-win7 4.2.0.1-4 Windows 7 - x86
opsi-local-image-win7-capture 4.2.0.1-4 Windows 7 - x86
opsi-local-image-win7-x64 4.2.0.1-4 Windows 7 - x64
opsi-local-image-win7-x64-capture 4.2.0.1-4 Windows 7 - x64
opsi-local-image-win81 4.2.0.1-4 Windows 81
opsi-local-image-win81-capture 4.2.0.1-4 Windows 81
opsi-local-image-win81-x64 4.2.0.1-4 Windows 81 - x64
opsi-local-image-win81-x64-capture 4.2.0.1-4 Windows 81 - x64
opsi-local-image-winxp 4.0.6.1-5 Windows XP - x86
opsi-logviewer 3.1-9 opsi logfile viewer
opsi-script 4.12.4.28-1 script
opsi-script-test 4.12.4.24-1 opsi-script test
opsi-set-win-uac 1.0-2 opsi set Windows UAC
opsi-setup-detector 4.2.0.7-1 opsi-setup-detector
opsi-template 4.0.6-1 opsi template product
opsi-template-with-admin 4.1.0.0-4 opsi template for installs with logged in admin
opsi-uefi-netboot 4.2.0.0-1 opsi-uefi-netboot
opsi-vhd-auto-upgrade 4.1.0.0-13 opsi-vhd-auto-upgrade
opsi-vhd-control 4.1.0.0-17 opsi-vhd-control
opsi-vhd-win10-x64 4.2.0.1-4 Windows 10 x64 in VHD
opsi-wan-config-off 4.1.0-1 opsi-wan-config-off
opsi-wan-config-on 4.1.0-1 opsi-wan-config-on
opsi-wim-capture 4.2.0.1-3 opsi-wim-capture
opsi-wim-delete 4.1.0.1-1 opsi-wim-delete
opsi-wim-info 4.0.7.2-1 opsi-wim-info
opsi-winpe 4.1.0-1 WinPE patching tool
opsi-winst 4.12.4.27-1 winst
opsi-winst-test 4.11.6.1-1 opsi-winst test

Regards, Eric

[SisterOfMercy]

You could make the timeout longer, to see if that helps. Maybe the fresh clients have a different network adapter that takes a while to properly wake up? Or if the clients have the same hardware, are you using a different driver?

[EricT]

hi SisterOfMercy ,

It starting to look like a network-related problem and not a problem with the OPSI-backend. Some of the clients initially show the error and then are connecting to the opsi-server.
Perhaps in some cases DHCP isn't providing the IP-address quickly enough.

Or it's an issue with the client-NIC, perhaps it isn't fully 'up' yet when the opsi-client starts.

Thanks for your replies.

Regards, Eric

[SisterOfMercy]

I have a few clients connected via VPN, and if I keep the default timeout at 30 seconds the connection will often timeout. 60 seconds is often more than enough here.