libpam_ntlm.1 failed, no such file or directory

[James Ellis_1]

I noticed these in my log files:

ftpd: open_module: stat (/usr/lib/security/libpam_ntlm.1) failed: no such file or directory

vmunix: vxfs:msg 018: vx_idelxwri_done fs inode 1974 had write error at offset XXXXXXXX

Does this indicate a corrupt file system?

Thanks.

[Steven E. Protter]

That is one possibility.

Does the file actually exist and is it the same size as one on a system without the message?

It could be just filedamage or an application running with the wrong SHLIB_PATH

This is in /var/adm/syslog/syslog.log right?

SEP

[James Ellis_1]

Steven,

Yes, it is the same size as the file on another system. The interesting thing is this person is running the same ftp job on another system and it is working ok. This is the test server, and we are having problems now.

One other thing, the system crashed back in Aug 25/26 and we have had problems starting around that time, make_recovery errors, ftp.

How can you tell if a file gets corrupted?

Thanks.

[Zeev Schultz]

libpam_ntlm is provided by CIFS/9000 client
software for authentication with NT (not win2000 which uses AD) systems. I know one more
product that is able to benefit from pam_ntlm library - its Apache Web server that can allow
remote users to access web pages based on how good they authenticated using this module and some NT domain controller.I doubt much that ftpd needs pam_ntlm at all.Check your /etc/pam.conf (and can post it if needed).
IF (and only if) pam.conf contains no sign of libpam_ntlm it means something is not good about ftpd (by the way is it a standard HP-UX ftpd --> check with "grep ftp /etc/inetd.conf")

To see what is the file vxfs complains about use ff command -
ff /dev/vgXX/lvolYY | grep 1974 (inode number).
basically I think there was a write fault of the file. Check in syslog.log for I/O or scsi error messages also.

Zeev