Good day,
I know that OES2018-SP3 is end of life, but my customer will be utilizing it a little longer than was expected, and we've been seeing some issues with the LUM services on those OES boxes. There have been a few different errors, but looking to see if we can approach them one at a time.
The first that is being seen is,
write_errToSock: Write error to socket, errno 32.
In the instance below, it seems that the LUM service actually starts, but then a day or two later we see the first errono 32. Should we be concerned with this error, in many cases I have been simply restarting the LUM services, and it returns to the Started condition, but would like to know what's happening to cause that error 32 if possible.
Jan 22 10:49:19 Gxx-Pxx-Mxxxxx1 systemd[1]: Started Novell Linux User Management(LUM).
Jan 24 18:12:58 Gxx-Pxx-Mxxxxx1 namcd[4860]: write_errToSock: Write error to socket, errno 32.
Jan 24 18:28:18 Gxx-Pxx-Mxxxxx1 namcd[4860]: write_errToSock: Write error to socket, errno 32.
The same for the one below, it appears that the service started on Jan 16, but then 3 days later the first error 32, then again a week later.
Jan 16 05:14:20 Mxx-Pxx-Mxxxx2 /usr/sbin/namcd[4860]: main: init_threads successful
Jan 16 05:14:21 Mxx-Pxx-Mxxxx2 systemd[1]: Started Novell Linux User Management(LUM).
Jan 19 18:27:46 Mxx-Pxx-Mxxxx2 namcd[4860]: write_errToSock: Write error to socket, errno 32.
Jan 26 18:43:23 Mxx-Pxx-Mxxx2 namcd[4860]: write_errToSock: Write error to socket, errno 32
Any assistance or hints as to what we can investigate would be most appreciated.
Thank you,
-DS