PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001239PacketFencecorepublic2011-07-25 09:392011-10-24 20:24
Reporterfgaudreault 
Assigned Toobilodeau 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versiondevel 
Target Version3.0.0Fixed in Version3.0.0 
fixed in git revision
fixed in mtn revision39961099cbc39f96cc7ea0974ae635fcdc589814
Summary0001239: PacketFence won't start if no inline interface
DescriptionWhen no inline interface is configured, PacketFence will not start and throw an undef error :

Can't call method "tag" on an undefined value at
    /usr/local/pf/lib/pf/services/apache.pm line 99 (0000002)
    (F) You used the syntax of a method call, but the slot filled by the
    object reference or package name contains an undefined value. Something
    like this will reproduce the error:
    
        $BADREF = undef;
        process $BADREF 1,2,3;
        $BADREF->process(1,2,3);
    
Uncaught exception from user code:
    Can't call method "tag" on an undefined value at /usr/local/pf/lib/pf/services/apache.pm line 99.
 at /usr/local/pf/lib/pf/services/apache.pm line 99
    pf::services::apache::generate_httpd_conf() called at /usr/local/pf/lib/pf/services.pm line 119
    pf::services::service_ctl('httpd', 'start') called at /usr/local/pf/bin/pfcmd line 1295
    main::service() called at /usr/local/pf/bin/pfcmd line 1236
    main::service() called at /usr/local/pf/bin/pfcmd line 198
    main::__ANON__() called at /usr/local/pf/bin/pfcmd line 215
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0001227closed obilodeau Reintroduce inline mode as a first class citizen 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-07-25 09:39fgaudreaultNew Issue
2011-08-01 16:31obilodeauPrioritynormal => high
2011-08-01 16:31obilodeauTarget Version => +1
2011-08-12 14:41maikelNote Added: 0002130
2011-08-12 16:46obilodeauStatusnew => assigned
2011-08-12 16:46obilodeauAssigned To => obilodeau
2011-08-16 15:59obilodeauRelationship addedrelated to 0001227
2011-08-16 15:59obilodeauNote Added: 0002138
2011-08-16 16:29obilodeaumtn revision => 39961099cbc39f96cc7ea0974ae635fcdc589814
2011-08-16 16:29obilodeauNote Added: 0002139
2011-08-16 16:29obilodeauStatusassigned => resolved
2011-08-16 16:29obilodeauFixed in Version => trunk
2011-08-16 16:29obilodeauResolutionopen => fixed
2011-09-21 22:07obilodeauFixed in Versiontrunk => 3.0.0
2011-09-21 22:15obilodeauNote Added: 0002250
2011-09-21 22:16obilodeauStatusresolved => closed
2011-10-24 20:24obilodeauTarget Version+1 => 3.0.0

Notes
(0002130)
maikel   
2011-08-12 14:41   
iptables also has a bug to startup:
Use of uninitialized value in chomp at /usr/local/pf/lib/pf/iptables.pm line 87 (0000001)
    (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 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 in substitution iterator at
        /usr/local/pf/lib/pf/util.pm line 637, <$template_fh> line 68 (0000001)
Use of uninitialized value in substitution iterator at
(0002138)
obilodeau   
2011-08-16 15:59   
first portion of the report was fixed
(0002139)
obilodeau   
2011-08-16 16:29   
both issue in this ticket were fixed as of revno: 39961099cbc39f96cc7ea0974ae635fcdc589814
(0002250)
obilodeau   
2011-09-21 22:15   
fix released in 3.0