perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jayson Hill <jaysonhil...@sbcglobal.net>
Subject Re: Perl module not reading/setting PerlSetEnv command on apache start
Date Tue, 14 May 2013 11:42:35 GMT
From: "jitendra.soni@accenture.com" <jitendra.soni@accenture.com>
To: modperl@perl.apache.org
Sent: Tue, May 14, 2013 2:57:42 AM
Subject: RE: Perl module not reading/setting PerlSetEnv command on apache start

I posted the issue on AMF group only then they said to post query to apache perl 
group.Is there any other forum where I can get solution for this issue?

Met vriendelijke groet / With kind regards,

Jitendra Soni
KPN - Application Development
Accenture | Bangalore INDIA
Mailto : jitendra.soni@accenture.com
Mobile : (+91) 99 860 298 97


-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com] 
Sent: Tuesday, May 14, 2013 1:21 PM
To: mod_perl list
Subject: Re: Perl module not reading/setting PerlSetEnv command on apache start

jitendra.soni@accenture.com wrote:
> I tried with /AMF path also with folder owner as "nobody" then also while 
>starting apache its saying CacheDirectoryStore not exits.I tried following 
>steps:
> 
> (1) sudo su (that is for root user login)
> (2) Created folder AMF with owner as nobody.
> (3) Set PerlSetEnv CacheDirectoryStore /AMf
> (4) Restarted apache and got error CacheDirectoryStore not exits.
> 
> Don't know what is missing from my side??

Neither do we, really.
You may have better luck a the the support address for the add-on module that 
you are using :
http://groups.google.com/group/amf-device-detection -



> 
> Met vriendelijke groet / With kind regards,
> 
> Jitendra Soni
> KPN - Application Development
> Accenture | Bangalore INDIA
> Mailto : jitendra.soni@accenture.com
> Mobile : (+91) 99 860 298 97
> 
> -----Original Message-----
> From: Vincent Veyron [mailto:vv.lists@wanadoo.fr]
> Sent: Monday, May 13, 2013 9:11 PM
> To: Soni, Jitendra
> Cc: modperl@perl.apache.org
> Subject: RE: Perl module not reading/setting PerlSetEnv command on apache 
start
> 
> Le lundi 13 mai 2013 à 13:45 +0000, jitendra.soni@accenture.com a écrit :
>> But I have given chmod 777 to these folder, will then also it won't work??
> 
> 
> It's not only these folders that must be accessible, the whole tree above them 
>has to be executable by the Apache user.
> 
> 
> 
> --
> Salutations, Vincent Veyron
> http://marica.fr/site/demonstration
> Logiciel de gestion des contentieux juridiques et des sinistres d'assurance
> 
> 
> 
> This message is for the designated recipient only and may contain privileged, 
>proprietary, or otherwise confidential information. If you have received it in 
>error, please notify the sender immediately and delete the original. Any other 
>use of the e-mail by you is prohibited.
> 
> Where allowed by local law, electronic communications with Accenture and its 
>affiliates, including e-mail and instant messaging (including content), may be 
>scanned by our systems for the purposes of information security and assessment 
>of internal compliance with Accenture policy.
> 
>______________________________________________________________________________________
>_
> 
> www.accenture.com
> 
> 



Hi Jitendra,

Have you tried dumping your %ENV settings with a .cgi script to be 
sure CacheDirectoryStore is picked up?
The reason I ask is because of this bit of code in Apache2::AMF51DegreesFilter:
  if ($ENV{CacheDirectoryStore}) { 
	$cachedirectorystore=$ENV{CacheDirectoryStore}; 
	$CommonLib->printLog("CacheDirectoryStore is: $cachedirectorystore");   } else 
{ 	  $CommonLib->printLog("CacheDirectoryStore not exist.	Please set the 
variable CacheDirectoryStore into httpd.conf, (the directory must be 
writeable)"); 	  ModPerl::Util::exit();         }    


I believe that's the code logging your error and exiting. Given that, 
double-check that CacheDirectoryStore is actually being set in your %ENV.
In the past, I've found dumping %ENV to be an easy way to check. A quick search 
will deliver a .cgi that can do that for you.

Also, due to the way the error is logged, I'm not convinced you actually have a 
write-ability issue on the directory. 
It looks like "must be writeable" is a thrown-in comment as there doesn't seem 
to be an actual check if the dir is writable or not. That's unfortunate if so, 
but perhaps I'm misreading the error above...

Double-check your location in httpd.conf that you set CacheDirectoryStore and 
dump out %ENV to be sure it's there.

Hope this helps.

Thanks,

Jayson
Mime
View raw message