Steve,

Please provide the following file: 
/usr/local/pf/html/pfappserver/lib/pfappserver/Controller/Configuration.pm

Cheers!
dw.

-- 
Derek Wuelfrath
[email protected] :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110)
Inverse inc. (www.inverse.ca) :: Leaders behind SOGo (www.sogo.nu) and 
PacketFence (www.packetfence.org)

On May 24, 2015 at 12:51:58, Steve Allen ([email protected]) wrote:

Hi Derek

I had a look and the "Fingerprints.pm" file does not exist.

Can you tell me what the following means:

---------------
Syntax error on line 69 of /usr/local/pf/conf/httpd.conf.d/httpd.admin:
Can't locate pf/os.pm in @INC (@INC contains: /usr/local/pf/conf 
/usr/local/fingerbank/lib /usr/local/pf/lib /usr/local/pf/html/pfappserver/lib 
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl 
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 . /etc/httpd) at 
/usr/local/pf/html/pfappserver/lib/pfappserver/Controller/Configuration.pm line 
24.\nBEGIN failed--compilation aborted at 
/usr/local/pf/html/pfappserver/lib/pfappserver/Controller/Configuration.pm line 
24.\nCompilation failed in require at 
/usr/share/perl5/vendor_perl/Catalyst/Utils.pm line 294.\nCompilation failed in 
require at (eval 2) line 3.\n
httpd.admin|not started
---------------

I had a look and on my 4.7.0 server I can find the pf/os.pm file but after 
upgrading to 5.0.2 the file is no longer there.
Is this what is causing the problems?


Kind regards,
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to