in reply to Re^2: mod_perl on apache works when symlinked to one directory but not to another
in thread mod_perl on apache works when symlinked to one directory but not to another

By "contexts" I was referring to the SELinux security contexts. If these are wrong then the mod_perl process may not be able to search the paths in order to find the modules. In that case the failed attempt would be logged in the audit log which is usually /var/log/audit/audit.log.


🦛

  • Comment on Re^3: mod_perl on apache works when symlinked to one directory but not to another
  • Download Code

Replies are listed 'Best First'.
Re^4: mod_perl on apache works when symlinked to one directory but not to another
by Cody Fendant (Friar) on Feb 02, 2021 at 04:21 UTC

    I was absolutely sure I'd thanked you for this answer, but somehow it's not there.

    Your answer solved my problem, thank you and sorry for taking so long.

    The answer was indeed the SELinux security contexts and once I'd got those set up correctly everything was fine.

    I do still think it's weird that the errors were saying "can't find the module" rather than "don't have permission", but it was a key thing to learn.