Skip to main content
AtiT
AtiT
New Member
August 18, 2017
Question

FSSO Collector Agent errors in log

  • August 18, 2017
  • 1 reply
  • 3999 views

Hi,

I can see errors in the log:

08/17/2017 14:26:36 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:26:47 [ 6332] 07/17/117 14:26:47: Bytes received: 16 08/17/2017 14:26:47 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:26:57 [ 6332] 07/17/117 14:26:57: Bytes received: 16 08/17/2017 14:26:57 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:27:07 [ 6332] 07/17/117 14:27:07: Bytes received: 16 08/17/2017 14:27:07 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:27:17 [ 6332] 07/17/117 14:27:17: Bytes received: 16 08/17/2017 14:27:17 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:27:27 [ 6332] 07/17/117 14:27:27: Bytes received: 16 08/17/2017 14:27:27 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:27:37 [ 6332] 07/17/117 14:27:37: Bytes received: 16 08/17/2017 14:27:37 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:27:48 [ 6332] 07/17/117 14:27:48: Bytes received: 16 08/17/2017 14:27:48 [ 6332] unknown message received:86 len:268435456 08/17/2017 14:27:58 [ 6332] 07/17/117 14:27:58: Bytes received: 16 08/17/2017 14:27:58 [ 6332] unknown message received:86 len:268435456

 

Does anyone know what does it mean?

    1 reply

    xsilver_FTNT
    Staff
    xsilver_FTNT
    Staff
    August 21, 2017

    it looks like something is trying to talk to Collector agent but it's not the FSSO language Collector understands.

    I'd sniff the traffic to see if there is any clue what is the app talking to Collector.

    Looks like some other, non-FSSO, app is trying to use port 8000/8002

    Terms & ConditionsAccessibility statement