After the installation of BIUL 23.1 we are seeing below errors in logs. This is a custom installation of BIUL 23.1 on master server.
pbksh.log
Dec 8 19:06:48 [368244] 1171 pbSSLAtomicWrite error 32: Broken pipe
pbmasterd.log
Dec 8 19:18:24 [369488] 3018 LIBMANGLE_mangleRecvStart failure on fd 4. No data returned
Best answer by Arvinder Kaur
Error ‘pbSSLAtomicWrite error 32: Broken pipe’ means the connection dropped, packet lost or blocked. Check tcp keepalive is on. Are you using 'noreconnect' in policy script forcing pbmasterd to stay connected to a remote pblocald connection?
The second error ‘LIBMANGLE_mangleRecvStart failure on fd 4. No data returned’ is usually due to ssl negotiation failure, network encryption mismatch. First find out which client connection is generating this error. Verify the encryption keys are the same on the client (runhost) and master using /usr/sbin/pbsum. Have a look at KB article Endpoint Privilege Management - 3018_LIBMANGLE_error
Error ‘pbSSLAtomicWrite error 32: Broken pipe’ means the connection dropped, packet lost or blocked. Check tcp keepalive is on. Are you using 'noreconnect' in policy script forcing pbmasterd to stay connected to a remote pblocald connection?
The second error ‘LIBMANGLE_mangleRecvStart failure on fd 4. No data returned’ is usually due to ssl negotiation failure, network encryption mismatch. First find out which client connection is generating this error. Verify the encryption keys are the same on the client (runhost) and master using /usr/sbin/pbsum. Have a look at KB article Endpoint Privilege Management - 3018_LIBMANGLE_error
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
