I'm in the middle of upgrading a 2.2.0 installation to 3.3.1

I've been working my way through the upgrade guide 
http://mtn.inverse.ca/revision/file/31606a1f3090d583a80c7c6b0fff6796b69e9a37/pf/UPGRADE

and have completed all the steps I think I need (upgrading schema, adjusting 
custom.pm etc etc)

When I do a sanity check of the config (./pfcmd checkup or on starting 
PacketFence) I get

FATAL - invalid network type registration for interface eth0.0050
FATAL - unknown configuration parameter scan.ssl if you added the parameter 
yourself make sure it is present in conf/documentation.conf
FATAL - Uncaught exception while trying to identify authentication::ldap module 
version: Can't locate object method "new" via package "authentication::ldap" at 
/usr/local/pf/lib/pf/pfcmd/checkup.pm line 676, <DATA> line 225.
WARNING - Violation 1100005 is ignored: Invalid trigger id: VENDORMAC::9078  at 
/usr/local/pf/lib/pf/trigger.pm line 211.
WARNING - Violation 1100001 is ignored: Invalid trigger type (scan) at 
/usr/local/pf/lib/pf/trigger.pm line 202.

I have looked through the upgrade guide and can't figure out what I need to 
change here - what should type=registration be changed to in pf.conf?

I can't find scan.ssl - according to the upgrade guide that's OK but I'm seeing 
the error listed above " unknown configuration parameter scan.ssl" etc

I can't find any reference in the upgrade guide as to why I might be getting 
the other errors either.

Anyone know where I've gone wrong?

Cheers,

Mark




Nuffield College is a Registered Charity No. 1137506. Registered Office: 
Nuffield College, New Road, Oxford, OX1 1NF

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to