PacketFence - BTS - PacketFence
View Issue Details
0000852PacketFenceerror-handlingpublic2009-11-16 12:332015-02-13 15:26
obilodeau 
 
highminoralways
closedopen 
 
 
0000852: httpd should almost always run even if config sanity check fails
For most users, when there is no httpd running, packetfence is just hosed and they need to get in touch with their sysadmin. This could be avoided if we still launched httpd and have them diagnose the problem in the web ui.

one exemple misuse case:
enable trapping.detection (snort) but forget to put an interface monitor, restart:

[root@pf-dev pf]# service packetfence restart
Restarting PacketFence...service|command
pfdhcplistener|stop
pfmon|stop
pfdetect|stop
httpd|stop
snmptrapd|stop
pfsetvlan|stop
snort|stop
Checking configuration sanity...
Uncaught exception from user code:
        monitor interface not defined, please disable trapping.dectection or set an interface type=...,monitor 
in pf.conf at /usr/lib/perl5/vendor_perl/5.8.8/Log/Log4perl/Logger.pm line 884
 at /usr/local/pf/bin/pfcmd line 2225
        main::sanity_check('pfdhcplistener', 'pfmon', 'pfdetect', 'httpd', 'snmptrapd', 'pfsetvlan', 
'snort') called at /usr/local/pf/bin/pfcmd line 1022
        main::service() called at /usr/local/pf/bin/pfcmd line 997
        main::service() called at /usr/local/pf/bin/pfcmd line 172
        main::__ANON__() called at /usr/local/pf/bin/pfcmd line 186


httpd should be able to start since its not affected by that error but:
[root@pf-dev pf]# bin/pfcmd service httpd start
Checking configuration sanity...
Uncaught exception from user code:
        monitor interface not defined, please disable trapping.dectection or set an interface type=...,monitor 
in pf.conf at /usr/lib/perl5/vendor_perl/5.8.8/Log/Log4perl/Logger.pm line 884
 at bin/pfcmd line 2225
        main::sanity_check('httpd') called at bin/pfcmd line 1022
        main::service() called at bin/pfcmd line 172
        main::__ANON__() called at bin/pfcmd line 186


In you do that through web ui you never get the error message shown, it just never works and if you restart the whole thing by mistake then you can never get it back up.

The log of the last ERRORs / FATALs would help in that case. This was reported elsewhere.

Nov 16 12:30:34 pfcmd(0) FATAL: monitor interface not defined, please disable trapping.dectection or 
set an interface type=...,monitor in pf.conf (main::sanity_check)
No tags attached.
related to 0001500closed  Tracking stuff related to web configuration improvements 
Issue History
2009-11-16 12:33obilodeauNew Issue
2009-11-16 12:37obilodeauStatusnew => assigned
2009-11-16 12:37obilodeauAssigned To => obilodeau
2010-04-15 17:43obilodeauProjectPacketFence 1.9 => PacketFence
2010-07-01 11:51obilodeauRelationship addedrelated to 0001023
2011-01-18 12:02obilodeauTarget Version => 2.1.0
2011-03-03 15:15obilodeauTarget Version2.1.0 => +1
2011-03-03 15:18obilodeauTarget Version+1 => +2
2012-05-07 15:35obilodeauRelationship addedchild of 0001444
2012-08-03 10:18dwuelfrathRelationship addedrelated to 0001500
2012-08-03 10:18dwuelfrathRelationship deletedchild of 0001444
2012-08-03 10:18dwuelfrathRelationship deletedrelated to 0001023
2012-08-07 10:45obilodeauNote Added: 0002901
2012-10-19 13:53fgaudreaultAssigned Toobilodeau =>
2012-10-19 13:53fgaudreaultTarget Versionlong-term => general
2015-02-13 15:26lmunroNote Added: 0003695
2015-02-13 15:26lmunroStatusassigned => closed

Notes
(0002901)
obilodeau   
2012-08-07 10:45   
Reminder sent to: dwuelfrath

How are we doing regarding that and the new admin with pfappserver?
(0003695)
lmunro   
2015-02-13 15:26   
Old issues.
Most are not relevant to PF 4 and up.

Let's reopen the ones that matter when we move to github.