<div class="gmail_quote">There was a post on the time syncronization of NSCA just 2 weeks ago, the following is a copy of the email</div>
<div class="gmail_quote">(I did not verify that this works)</div>
<div class="gmail_quote">TOny</div>
<div class="gmail_quote"> </div>
<div class="gmail_quote"> </div>
<div class="gmail_quote">dateFri, Jun 13, 2008 at 10:44 AM<br>subjectRe: [Nagios-users] Dropping packet with future timestamp, NSCA<br>mailing <a href="http://listnagios-users.lists.sourceforge.net">listnagios-users.lists.sourceforge.net</a> Filter messages from this mailing list<br>
<a href="http://mailed-bylists.sourceforge.net">mailed-bylists.sourceforge.net</a></div>
<div class="gmail_quote">hide details Jun 13 (12 days ago) Reply</div>
<div class="gmail_quote"><br>Just change the source:<br>---8<---<br> /* check the timestamp in the packet */<br> packet_time=(time_t)ntohl(receive_packet.timestamp);<br> time(¤t_time);<br> //if(packet_time>current_time){<br>
// syslog(LOG_ERR,"Dropping packet with future<br> // timestamp.");<br> // /*return;*/<br> // close(sock);<br> // if(mode==SINGLE_PROCESS_DAEMON)<br>
// return;<br> // else<br> // do_exit(STATE_OK);<br> // }<br> //else{<br> packet_age= abs ( (unsigned long)(current_time-packet_time) );<br>
syslog(LOG_ERR,"Time diff: %lu seconds", packet_age);<br> if(max_packet_age>0 && (packet_age>max_packet_age)){<br> syslog(LOG_ERR,"Dropping packet with stale timestamp - packet was %lu seconds old or new.",packet_age);<br>
/*return;*/<br> close(sock);<br> if(mode==SINGLE_PROCESS_DAEMON)<br> return;<br> else<br> do_exit(STATE_OK);<br>
}<br> // }<br>---8<---<br>If you want, you can see now the "Time diff" in the syslog.<br>Workes for me.</div>
<div class="gmail_quote">Perhaps that should be an option in the next release!<br>Chris</div>
<div class="gmail_quote">- Hide quoted text -</div>
<div class="gmail_quote"><br>On Do, Jun 12, 2008 at 06:08:10 +0200, Vinogratzky wrote:<br>> Hi list,<br>><br>> I have some passive checks with NSCA and my clients are a few seconds<br>> ahead.<br>> The server rejects the package with:<br>
> ---8<---<br>> nsca[10986]: Dropping packet with future timestamp.<br>> ---8<---<br>><br>> max_packet_age=0<br>> doesn't help here.<br>><br>> Any hints?<br>> (No, I'm not able to sync the Clients with ntp.)<br>
><br>> Thx,<br>> Chris<br>></div>
<div class="gmail_quote"> </div>
<div class="gmail_quote"> </div>
<div class="gmail_quote"> </div>
<div class="gmail_quote">On Tue, Jun 24, 2008 at 9:20 PM, Jason <<a href="mailto:angc0020@ntu.edu.sg">angc0020@ntu.edu.sg</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>eems to me that it is a time synchronization issue.<br><br>NSCA only works when the time between the client and server is sync veri<br>
accurately. (even 30 secs diff will cause packets to be dropped).<br><br>Check your logs at your Nagios server for any errors like "dropping packet due<br>to future timestamp". (/var/log/message, /var/log/messages, /var/log/syslog)<br>
<br>If the problem exists, sync client's time with the server and set the client's<br>sync interval (default for windows is to sync once per week)<br><br>or u can get a ntp server<br>
<div>
<div></div>
<div class="Wj3C7c"><br><br><br><br><br><br>-------------------------------------------------------------------------<br>Check out the new SourceForge.net Marketplace.<br>It's the best place to buy or sell services for<br>
just about anything Open Source.<br><a href="http://sourceforge.net/services/buy/index.php" target="_blank">http://sourceforge.net/services/buy/index.php</a><br>_______________________________________________<br>Nagios-users mailing list<br>
<a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>::: Messages without supporting info will risk being sent to /dev/null<br></div></div></blockquote><br>