Alarm: Bad Packet Time

Scrutinizer is an enterprise/business class NetFlow and sFlow analysis tool. Scrutinizer provides historical trends of the company's critical network interfaces as well as the details on:

Who: The end system causing the traffic
What: The application/protocol that is being used
When: The time frame it has been occurring for
Where: The network connection that is affected

Moderators: scottr, Moderator Team

Post Reply
Posts: 7
Joined: Wed May 11, 2011 11:50 am

Alarm: Bad Packet Time

Post by elang » Fri Feb 20, 2015 10:55 am

On my Scrutinizer Dashboard, under recent alarms, I keep getting "ScrutCollector: Bad Packet Time". In the details, it says "{"bad_pkt_time":"exporter clock is 294 seconds ahead of collector"}"

Seems fairly self-explanatory, except that it is indicating that the problem exported is the scrutinizer server itself. Since that is the collector, how can the exporter and collector have different times?
Scrut.JPG (82.73 KiB) Viewed 2062 times

Posts: 83
Joined: Thu Jan 10, 2013 2:15 pm

Re: Alarm: Bad Packet Time

Post by JakeB » Mon Feb 23, 2015 2:34 pm

Hello Elang -

That seems strange, Do you know if there were any changes to the time and are you still receiving these alerts?


User avatar
Site Admin
Posts: 315
Joined: Wed Jul 27, 2005 10:53 am
Location: Sunny Sanford Maine

Re: Alarm: Bad Packet Time

Post by tomp » Tue Feb 24, 2015 9:57 am

Hi Elang and Jake,

I investigated this issue just the other day and found a bug, which has been escalated to development. It is currently being addressed.

- Tom

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 2 guests