in reply to Re: 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

Hi, I'm not sure what either of those means. I'm checking the Apache error log, but I don't know if that's what you mean about by 'audit log', or 'contexts'.

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

Replies are listed 'Best First'.
Re^3: mod_perl on apache works when symlinked to one directory but not to another
by hippo (Chancellor) on Nov 29, 2020 at 09:27 UTC

    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.


    🦛

      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.