On Tue, Jul 20, 2010 at 5:27 AM, Tom Murphy <[email protected]> wrote: > On Sun, Jul 11, 2010 at 06:27:41PM -0700, Philip Guenther wrote: >> When in doubt, use a bigger hammer. You could try using 'ktrace' on >> the web server (probably with the -i option) to see exactly what is >> happening when perl tries to open the Carp/Heavy.pm file. > > ktrace produces a rather large (6M) kdump file. I checked all the paths > below and the only place the file exists is at > /usr/libdata/perl5/Carp/Heavy.pm. The permissions on the file are root:wheel > and 0444, so it should be readable by anyone. I am not sure why it can't > find this file at all.
I think I was a bit misleading in my suggestion. I think you should scan the *entire* kdump output to see if it's calling chroot(), for example, which will completely screw the lazy-loading used by Carp.pm for Carp/Heavy.pm. ... > 2037 httpd CALL stat(0x8325f480,0xcfbdac90) > 2037 httpd NAMI "/usr/libdata/perl5/Carp/Heavy.pmc" > 2037 httpd RET stat -1 errno 2 No such file or directory You confirm that that file exists when you check with the normal root directory, which suggests the process is running with some other root directory when it is doing the above, no? Philip Guenther
