PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000944 | PacketFence | scanning | public | 2010-04-07 15:25 | 2015-02-13 15:24 |
| Reporter | obilodeau | ||||
| Assigned To | obilodeau | ||||
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | 1.8.5 | ||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0000944: scheduled nessus scan doing weird things | ||||
| Description | scheduled scans generate a long list of errors like: Apr 07 15:18:16 pfcmd(0) DEBUG: starting to parse 'config get database.user' (pf::pfcmd::parseCommandLine) Apr 07 15:18:16 pfcmd(0) DEBUG: main cmd argument is config (pf::pfcmd::parseCommandLine) launching: /usr/bin/perl /usr/local/pf/bin/pfcmd config get database.user in a loop it would seem. The scan is launched from crontab. Here's the crontab: [root@pf-dev pf]# crontab -u pf -l 0 15 * * * /usr/local/pf/bin/pfcmd schedule now 192.168.1.104 Need to investigate further. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-04-07 15:25 | obilodeau | New Issue | |||
| 2010-04-07 15:25 | obilodeau | Status | new => assigned | ||
| 2010-04-07 15:25 | obilodeau | Assigned To | => obilodeau | ||
| 2010-04-07 15:26 | obilodeau | Category | 1.8.5 => scanning | ||
| 2011-01-18 12:02 | obilodeau | Target Version | => 2.1.0 | ||
| 2011-03-03 15:15 | obilodeau | Target Version | 2.1.0 => +1 | ||
| 2011-03-03 15:18 | obilodeau | Target Version | +1 => +2 | ||
| 2015-02-13 15:24 | lmunro | Note Added: 0003663 | |||
| 2015-02-13 15:24 | lmunro | Status | assigned => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||