Hello Fabrice,
Still can"t get my head around this.. Seems to me like an API communication
problem or any more ideas to what the problem might be.
Regards,
Kehinde
On Sat, Jul 29, 2017 at 8:53 AM, Akala Kehinde <[email protected]>
wrote:
> Hello Fabrice,
>
> I still get the same error, kindly see logs below:
>
> [root@pfence logs]# netstat -nlp | grep 8834
> tcp 0 0 0.0.0.0:8834 0.0.0.0:*
> LISTEN 1761/nessusd
> tcp6 0 0 :::8834 :::* LISTEN
> 1761/nessusd
> [root@pfence logs]#
>
> Jul 29 08:51:53 pfence pfqueue: pfqueue(13223) INFO:
> [mac:00:50:ff:25:ce:00] Instantiate profile SNS (pf::Connection::
> ProfileFactory::_from_profile)
> Jul 29 08:51:53 pfence pfqueue: pfqueue(13223) INFO:
> [mac:00:50:ff:25:ce:00] violation 1200005 already exists for
> 00:50:ff:25:ce:00, not adding again (pf::violation::violation_add)
> Jul 29 08:51:54 pfence pfqueue: pfqueue(13223) INFO:
> [mac:00:50:ff:25:ce:00] Instantiate profile SNS (pf::Connection::
> ProfileFactory::_from_profile)
> Jul 29 08:51:54 pfence pfqueue: pfqueue(13223) INFO:
> [mac:00:50:ff:25:ce:00] New ID generated: 150131111423ce00
> (pf::util::generate_id)
> Jul 29 08:51:54 pfence pfqueue: pfqueue(13223) ERROR:
> [mac:00:50:ff:25:ce:00] communication error: Can't connect to
> 127.0.0.1:8834 at /usr/local/pf/lib/pf/scan/nessus6.pm line 96.
> (pf::api::can_fork::notify)
>
>
>
> Regards,
> Kehinde
>
> On Fri, Jul 28, 2017 at 8:22 PM, Fabrice Durand via PacketFence-users <
> [email protected]> wrote:
>
>> Hello Akala,
>>
>> if nessus run on the same server then try 127.0.0.1 for the server ip.
>>
>> Also what return : netstat -nlp | grep 8834
>>
>> Regards
>>
>> Fabrice
>>
>>
>>
>> Le 2017-07-28 à 12:09, Akala Kehinde via PacketFence-users a écrit :
>>
>> Just FYI, the Nessus server runs on the PF server.
>>
>> Regards,
>> Kehinde
>>
>> On Fri, Jul 28, 2017 at 5:53 PM, Akala Kehinde <[email protected]>
>> wrote:
>>
>>> Hallo Guys,
>>>
>>> Quick one..
>>> I get this error when PF tries triggering a violation:
>>>
>>> Checked line 96 and seems it's an error with the creds, but creds is
>>> right. Or is the creds not supposed to be that on the Nessus server?
>>>
>>> Jul 8 13:57:58 pfence pfqueue: pfqueue(10450) INFO:
>>> [mac:00:50:ff:25:ce:00] New ID generated: 149951507810ce00
>>> (pf::util::generate_id)
>>> Jul 8 13:57:58 pfence pfqueue: pfqueue(10450) ERROR:
>>> [mac:00:50:ff:25:ce:00] communication error: Can't connect to
>>> 172.16.100.10:8834 at /usr/local/pf/lib/pf/scan/nessus6.pm line 96.
>>> (pf::api::can_fork::notify)
>>>
>>>
>>> Regards,
>>> Kehinde
>>>
>>> Regards,
>>> Kehinde
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> PacketFence-users mailing
>> [email protected]https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>> --
>> Fabrice [email protected] :: +1.514.447.4918 <(514)%20447-4918>
>> (x135) :: www.inverse.ca
>> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence
>> (http://packetfence.org)
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> PacketFence-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
