From: (no name) (no email)
Date: Thu Feb 26 2004 - 15:32:48 EST
On Thu, 26 Feb 2004, Kenneth Berry wrote:
> Here is a small snippet of the log showing the file open and an odd file
> not found eroor, followed by a successful open of the same library.
> This pattern is repeated for many files
>
> (...)
>
> Feb 26 10:26:53 mbtweb logger: open("/lib/security/$ISA/pam_env.so",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> Feb 26 10:26:53 mbtweb logger:
> open("/lib/security/../../lib/security/pam_env.so", O_RDONLY) = 11
> Feb 26 10:26:53 mbtweb logger: read(11,
> "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\f\0"..., 512) = 512
> Feb 26 10:26:53 mbtweb logger: fstat64(11, {st_mode=S_IFREG|0755,
> st_size=11592, ...}) = 0
> Feb 26 10:26:53 mbtweb logger: old_mmap(NULL, 14572,
> PROT_READ|PROT_EXEC, MAP_PRIVATE, 11, 0) = 0x40324000
> Feb 26 10:26:53 mbtweb logger: old_mmap(0x40327000, 4096,
> PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 11, 0x2000) = 0x40327000
> Feb 26 10:26:53 mbtweb logger: close(11)
>
Is this a SASL recursion problem? SASL calling PAM which calls LDAP which
calls SASL? Search the archives for Liviu Daia explaining reentrancy
issues in SASL.
In any case this does not look like a Postfix issue, understand
in detail the call chain implied by your design and make sure it makes
sense. Make sure there are no library conflicts or reentrancy issues.
-- Viktor.
|
|
|