On Wed, 31 Jul 2019 at 18:07, Thorsten Schöning <tschoen...@am-soft.de> wrote: > > Hi all, > > I recently started to have a look at supporting mod_perl for our > WebApp on Windows again and implemented a very simple PoC pre-loading > our app during start of HTTPd using "PerlPostConfigRequire". During > implementation I ran into the following problem with my setup. > > My HTTPd is NOT running using an account with lots of permissions like > SYSTEM, but as a standard user instead. That user has read permissions > on all necessary files to serve and execute, can write logs properly > etc. Everything is working fine using plain CGI instead of mod_perl as > well. > > When enabling mod_perl, the service refuses to start and the following > error is logged after some waiting: > > > [Wed Jul 31 18:35:50.609122 2019] [perl:error] [pid 15276:tid 848] > > APR::Finfo::stat: (70008) Partial results are valid but processing is > > incomplete at C:\\Program Files\\Apache Software > > Foundation\\mod_perl\\Current\\Perl64\\site\\lib/ModPerl/RegistryLoader.pm > > line 119Compilation failed in require at (eval 2) line 1.\n > [...] > All this leads to the following questions: > > 1. Does that make sense to anyone at all? :-) > 2. Does mod_perl really needs FINFO_NORM or can switch to FINFO_MIN? > 3. Is this maybe something the APR-project itself should lookt at? > FINFO_NORM seems to be some default which should fail in other > contexts with standard users as well. >
I ran into this myself recently. I posted questions about it to the APR-Dev list, and subsequently found an old bug report of exactly the same problem: https://bz.apache.org/bugzilla/show_bug.cgi?id=51560 Sadly, there is no response from APR-Dev about this yet.
