when I run PTPD2 v170 I get periodic syslog messages. This is with a symmetricom S350 master and 2 slaves.both slaves exhibit the error. I have not yot determined how glitch affects accuracy .
For the most part PTPD seems to be syncing correctly.
See syslog below:
Jan 13 08:15:04 (none) syslogd 1.5.0: restart.
Jan 13 08:15:04 (none) syslogd 1.5.0: restart.
Jan 13 08:34:13 (none) - MARK -
Jan 13 08:54:13 (none) - MARK -
Jan 13 08:55:01 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 09:14:13 (none) - MARK -
Jan 13 09:34:13 (none) - MARK -
Jan 13 09:54:13 (none) - MARK -
Jan 13 10:14:13 (none) - MARK -
Jan 13 10:34:13 (none) - MARK -
Jan 13 10:54:13 (none) - MARK -
Jan 13 11:14:13 (none) - MARK -
Jan 13 11:34:13 (none) - MARK -
Jan 13 11:54:13 (none) - MARK -
Jan 13 12:14:13 (none) - MARK -
Jan 13 12:34:13 (none) - MARK -
Jan 13 12:54:13 (none) - MARK -
Jan 13 13:02:29 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 13:14:13 (none) - MARK -
Jan 13 13:34:13 (none) - MARK -
Jan 13 13:54:13 (none) - MARK -
Jan 13 14:14:13 (none) - MARK -
Jan 13 14:34:13 (none) - MARK -
Jan 13 14:54:13 (none) - MARK -
Jan 13 15:14:13 (none) - MARK -
Jan 13 15:34:13 (none) - MARK -
Jan 13 15:54:13 (none) - MARK -
Jan 13 16:14:13 (none) - MARK -
Jan 13 16:34:13 (none) - MARK -
Jan 13 16:54:13 (none) - MARK -
Jan 13 17:09:40 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 17:34:13 (none) - MARK -
Jan 13 17:54:13 (none) - MARK -
Jan 13 18:14:13 (none) - MARK -
Jan 13 18:34:13 (none) - MARK -
Jan 13 18:54:13 (none) - MARK -
Jan 13 19:14:13 (none) - MARK -
Jan 13 19:34:13 (none) - MARK -
Jan 13 19:54:13 (none) - MARK -
Jan 13 20:14:13 (none) - MARK -
Jan 13 20:34:13 (none) - MARK -
Jan 13 20:54:13 (none) - MARK -
Jan 13 21:14:13 (none) - MARK -
Jan 13 21:16:49 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 21:34:13 (none) - MARK -
Jan 13 21:54:13 (none) - MARK -
Jan 13 22:14:13 (none) - MARK -
Jan 13 22:34:13 (none) - MARK -
Jan 13 22:54:13 (none) - MARK -
Jan 13 23:14:13 (none) - MARK -
Jan 13 23:34:13 (none) - MARK -
Jan 13 23:54:13 (none) - MARK -
Jan 14 00:14:13 (none) - MARK -
Jan 14 00:34:13 (none) - MARK -
Jan 14 00:54:13 (none) - MARK -
Jan 14 01:14:13 (none) - MARK -
Jan 14 01:25:31 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 14 01:54:13 (none) - MARK -
Jan 14 02:14:13 (none) - MARK -
Jan 14 02:34:13 (none) - MARK -
Jan 14 02:54:13 (none) - MARK -
Jan 14 03:14:13 (none) - MARK -
Jan 14 03:34:13 (none) - MARK -
Jan 14 03:54:13 (none) - MARK -
Jan 14 04:14:13 (none) - MARK -
Jan 14 04:34:13 (none) - MARK -
Jan 14 04:54:13 (none) - MARK -
Jan 14 05:14:13 (none) - MARK -
Jan 14 05:33:19 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 14 05:54:13 (none) - MARK -
Jan 14 06:14:13 (none) - MARK -
Jan 14 06:34:13 (none) - MARK -
Jan 14 06:54:13 (none) - MARK -
Jan 14 07:14:13 (none) - MARK -
Jan 14 07:34:13 (none) - MARK -
Jan 14 07:54:13 (none) - MARK -
Jan 14 08:14:13 (none) - MARK -
Jan 14 08:15:01 (none) /USR/SBIN/CRON: (root) CMD ( exec /etc/cron.daily/logrotate >> /dev/null 2>&1 &)
Jan 14 08:15:01 (none) syslogd 1.5.0: restart.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
when I run PTPD2 v170 I get periodic syslog messages. This is with a symmetricom S350 master and 2 slaves.both slaves exhibit the error. I have not yot determined how glitch affects accuracy .
For the most part PTPD seems to be syncing correctly.
See syslog below:
Jan 13 08:15:04 (none) syslogd 1.5.0: restart.
Jan 13 08:15:04 (none) syslogd 1.5.0: restart.
Jan 13 08:34:13 (none) - MARK -
Jan 13 08:54:13 (none) - MARK -
Jan 13 08:55:01 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 09:14:13 (none) - MARK -
Jan 13 09:34:13 (none) - MARK -
Jan 13 09:54:13 (none) - MARK -
Jan 13 10:14:13 (none) - MARK -
Jan 13 10:34:13 (none) - MARK -
Jan 13 10:54:13 (none) - MARK -
Jan 13 11:14:13 (none) - MARK -
Jan 13 11:34:13 (none) - MARK -
Jan 13 11:54:13 (none) - MARK -
Jan 13 12:14:13 (none) - MARK -
Jan 13 12:34:13 (none) - MARK -
Jan 13 12:54:13 (none) - MARK -
Jan 13 13:02:29 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 13:14:13 (none) - MARK -
Jan 13 13:34:13 (none) - MARK -
Jan 13 13:54:13 (none) - MARK -
Jan 13 14:14:13 (none) - MARK -
Jan 13 14:34:13 (none) - MARK -
Jan 13 14:54:13 (none) - MARK -
Jan 13 15:14:13 (none) - MARK -
Jan 13 15:34:13 (none) - MARK -
Jan 13 15:54:13 (none) - MARK -
Jan 13 16:14:13 (none) - MARK -
Jan 13 16:34:13 (none) - MARK -
Jan 13 16:54:13 (none) - MARK -
Jan 13 17:09:40 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 17:34:13 (none) - MARK -
Jan 13 17:54:13 (none) - MARK -
Jan 13 18:14:13 (none) - MARK -
Jan 13 18:34:13 (none) - MARK -
Jan 13 18:54:13 (none) - MARK -
Jan 13 19:14:13 (none) - MARK -
Jan 13 19:34:13 (none) - MARK -
Jan 13 19:54:13 (none) - MARK -
Jan 13 20:14:13 (none) - MARK -
Jan 13 20:34:13 (none) - MARK -
Jan 13 20:54:13 (none) - MARK -
Jan 13 21:14:13 (none) - MARK -
Jan 13 21:16:49 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 13 21:34:13 (none) - MARK -
Jan 13 21:54:13 (none) - MARK -
Jan 13 22:14:13 (none) - MARK -
Jan 13 22:34:13 (none) - MARK -
Jan 13 22:54:13 (none) - MARK -
Jan 13 23:14:13 (none) - MARK -
Jan 13 23:34:13 (none) - MARK -
Jan 13 23:54:13 (none) - MARK -
Jan 14 00:14:13 (none) - MARK -
Jan 14 00:34:13 (none) - MARK -
Jan 14 00:54:13 (none) - MARK -
Jan 14 01:14:13 (none) - MARK -
Jan 14 01:25:31 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 14 01:54:13 (none) - MARK -
Jan 14 02:14:13 (none) - MARK -
Jan 14 02:34:13 (none) - MARK -
Jan 14 02:54:13 (none) - MARK -
Jan 14 03:14:13 (none) - MARK -
Jan 14 03:34:13 (none) - MARK -
Jan 14 03:54:13 (none) - MARK -
Jan 14 04:14:13 (none) - MARK -
Jan 14 04:34:13 (none) - MARK -
Jan 14 04:54:13 (none) - MARK -
Jan 14 05:14:13 (none) - MARK -
Jan 14 05:33:19 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo
Jan 14 05:54:13 (none) - MARK -
Jan 14 06:14:13 (none) - MARK -
Jan 14 06:34:13 (none) - MARK -
Jan 14 06:54:13 (none) - MARK -
Jan 14 07:14:13 (none) - MARK -
Jan 14 07:34:13 (none) - MARK -
Jan 14 07:54:13 (none) - MARK -
Jan 14 08:14:13 (none) - MARK -
Jan 14 08:15:01 (none) /USR/SBIN/CRON: (root) CMD ( exec /etc/cron.daily/logrotate >> /dev/null 2>&1 &)
Jan 14 08:15:01 (none) syslogd 1.5.0: restart.
I added some additional debug info to the handleDelayReq() function in protocol.c:
if ((ptpClock->sentDelayReqSequenceId - 1) != header->sequenceId) {
INFO("HandledelayReq : disreguard delayreq because of wrong SeqNo: Sent:%d Recvd:%d\n",
ptpClock->sentDelayReqSequenceId - 1,header->sequenceId );
The resulting syslog entry:
Jan 19 11:20:45 (none) ptpd2: HandledelayReq : disreguard delayreq because of wrong SeqNo: Sent:-1 Recvd:65535
Shows that this is the result of an unhandled rollover of the 16 bit sequence number.
Perhaps I should open a bug for this, its really quite annoying.
Please open a bug and if you can capture a tcpdump of the traffic that would be great.
You can just filter the events with:
port 319 or port 320
or a full dump is also fine.