Re^5: apache 2.4 mod_perl permission denied on standard modules

This really sounds as if there is at least one entry in @INC which is not readable for the user Apache is running as. As soon as Perl encounters such a directory, it will stop searching. So you should make sure that the relevant directories you have in @INC appear before the bad ones where the user does not have read permissions.

Comment on Re^5: apache 2.4 mod_perl permission denied on standard modules Select or Download Code

Replies are listed 'Best First'.
Re^6: apache 2.4 mod_perl permission denied on standard modules by Crackers2 (Parson) on Aug 28, 2015 at 21:23 UTC
Gah I wish I'd known this: As soon as Perl encounters such a directory, it will stop searching/ Found a directory in INC that was readable but not executable; changed to 755 and we're past the issue. Still have to figure out why that directory is in INC in the first place; it's not in there when I check INC from the shell, and I don't see it anywhere in the apache config. But things are working now. Thanks to both of you!	[reply]
Re^7: apache 2.4 mod_perl permission denied on standard modules by sundialsvc4 (Abbot) on Aug 31, 2015 at 01:37 UTC
Hmm... you are right about that, and it certainly is not intuitive that Perl would “stop searching.” Thanks for pointing that out.
Re^8: apache 2.4 mod_perl permission denied on standard modules by Crackers2 (Parson) on Sep 02, 2015 at 20:22 UTC
As a final follow-up. This is apparently new behaviour and mentioned in the perl 5.18 release notes: When require encounters an unreadable file, it now dies. It used to ignore the file and continue searching the directories in @INC [perl #113422].	[reply]


P is for Practical
	PerlMonks