Hi cg, cg wrote: > Hello List, > > Setting pf up on a Debian server and have run into the following two > issues during the initial installation. Hoping that someone here can > offer advice. I followed the installation procedure in the archive as > well as one or two online writeups (useful, although both are somewhat > out of date).
Nice to see that you are willing to try to run pf on debian. We want to have debian packages in the future so if you have some advice or you did some things to get packetfence working better on debian let us know. The best way would be posting info on -devel list or filing a bug in category packaging. > > First, the following error message occurs when I attempt to start pf : > ===================================================================== > Checking configuration sanity... > Use of uninitialized value $_[7] in join or string at > /usr/local/pf/lib/pf/class.pm line 170 (#1) > (W uninitialized) An undefined value was used as if it were already > defined. It was interpreted as a "" or a 0, but maybe it was a mistake. > To suppress this warning assign a defined value to your variables. > > To help you figure out what was undefined, perl will try to tell you the > name of the variable (if any) that was undefined. In some cases it cannot > do this, so it also tells you what operation you used the undefined value > in. Note, however, that perl optimizes your program and the operation > displayed in the warning may not necessarily appear literally in your > program. For example, "that $foo" is usually optimized into "that " > . $foo, and the warning will refer to the concatenation (.) operator, > even though there is no . in your program. > > Use of uninitialized value $_[8] in join or string at > /usr/local/pf/lib/pf/class.pm line 170 (#1) > Use of uninitialized value $_[6] in join or string at > /usr/local/pf/lib/pf/class.pm line 170 (#1) > service|command > config files|start > iptables|start > pfdhcplistener|already running > pfmon|already running > pfdetect|already running > httpd|start > snort|start > ===================================================================== > > line 170, referred to, is of course the error trap where the exception > is thrown. These are just warnings, I know they are scary but PF should run fine anyways. The error will affect violations. After restarting your PF did you still get the errors? Can you try simplifying your conf/violations.conf file (commenting most of it) and try reproducing? > > Second, the included 'packetfence.spec' file lists a > 'php-jpgraph-packetfence' rpm (= 2.3.4) which I've searched for but > cannot find. (Presumably it can be converted into a .deb by alien.) > Does anyone have any idea where I can source it ? It's a shameful hard-coded path package we've done to include library code in the right spot. Grab it from our CentOS repo and try to alien it it should work since it's more or less a tarball (no magic rpm stuff hapening). http://inverse.ca/downloads/PacketFence/CentOS5/i386/RPMS/ > > Following what seems to have become a tradition, once it's working I'm > thinking of posting a HowTo ... That would be very welcomed! > > Greetings and thanks for the attention. All advice, critique, > commentary, flames, etc. are welcome. Well just want to say thanks again and feel free to ask for help and file issues! I'll be more responsive. Have a good one! -- Olivier Bilodeau obilod...@inverse.ca :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Packetfence-users mailing list Packetfence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users