API: Incorrect session or participant duration - Revision history

Dosproul: 1 revision

2012-08-14T18:57:20Z

1 revision

← Older revision

Revision as of 18:57, 14 August 2012

Rshroyer: Added Categories 8.5 and 9.0.

2012-08-14T01:23:28Z

Added Categories 8.5 and 9.0.

← Older revision		Revision as of 01:23, 14 August 2012
Line 42:		Line 42:
	None.		None.

		+	[[Category:Cisco_MediaSense,_Release_8.5]]
		+	[[Category:Cisco_MediaSense,_Release_9.0]]
	\|}		\|}

Dosproul: 1 revision

2012-08-03T13:04:12Z

1 revision

← Older revision

Revision as of 13:04, 3 August 2012

Rshroyer: Added release 9.0(1)

2012-08-02T03:04:42Z

Added release 9.0(1)

← Older revision		Revision as of 03:04, 2 August 2012
Line 35:		Line 35:
	! '''Release'''		! '''Release'''
	\|		\|
-	Release 8.5(1), Release 8.5(2), Release 8.5(3), ~~and~~ Release 8.5(4).	+	Release 8.5(1), Release 8.5(2), Release 8.5(3), Release 8.5(4), and Release 9.0(1).

	\|-		\|-
Line 43:		Line 43:

	\|}		\|}
-
-	~~[[Category:Cisco_MediaSense,_Release_8.5]]~~

Dosproul: 1 revision

2012-01-27T17:08:40Z

1 revision

← Older revision

Revision as of 17:08, 27 January 2012

Kemacdon at 19:38, 25 January 2012

2012-01-25T19:38:09Z

← Older revision		Revision as of 19:38, 25 January 2012
Line 23:		Line 23:
	! '''Possible Cause'''		! '''Possible Cause'''
	\|		\|
-	Incorrect duration could have several causes, unsynchronized NTP servers is a known possibility.	+	Incorrect duration could have several causes, unsynchronized NTP servers is a known possibility.

	The Cisco MediaSense publisher server uses two NTP servers to synchronize time. However, the time on these NTP servers may not be synchronized. As a result, Cisco MediaSense servers switch their times based on the currently-synchronized NTP server.		The Cisco MediaSense publisher server uses two NTP servers to synchronize time. However, the time on these NTP servers may not be synchronized. As a result, Cisco MediaSense servers switch their times based on the currently-synchronized NTP server.
Line 35:		Line 35:
	! '''Release'''		! '''Release'''
	\|		\|
-	Release 8.5(1), Release 8.5(2), ~~and~~ Release 8.5(3).	+	Release 8.5(1), Release 8.5(2), Release 8.5(3), and Release 8.5(4).

	\|-		\|-

Cchetty: 1 revision

2011-10-08T20:19:33Z

1 revision

← Older revision

Revision as of 20:19, 8 October 2011

Cchetty at 07:39, 30 September 2011

2011-09-30T07:39:23Z

New page

== Incorrect session or participant duration ==

{| border="1"
|-
! '''Problem Summary'''
| Track, participant, or session duration is incorrect or negative (for example: "sessionDuration":-4776).
|-
! '''Error Message'''
| from /var/log/active/syslog/messages: <pre>Aug 23 02:51:05 pauems01 user 6 ilog_impl: Restarting NTP as time offset is -185.215622 msec.

Aug 23 02:51:07 pauems01 user 6 ilog_impl: NTP servers list: 10.192.254.11 10.192.254.1</pre><pre>Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.11, \
stratum 1, '''offset -185.225332''', delay 0.04140 23

Aug 02:51:07 ntpdate[17992]: step time server 10.192.254.11 ''offset -185.225332 sec'' (rc=0).</pre><pre>Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.1, \
stratum 2, '''offset 0.054938''', delay 0.02736 23

Aug 02:51:07 ntpdate[18001]: adjust time server 10.192.254.1 offset 0.054938 sec (rc=0). </pre>
|-
! '''Possible Cause'''
|
Incorrect duration could have several causes, unsynchronized NTP servers is a known possibility.

The Cisco MediaSense publisher server uses two NTP servers to synchronize time. However, the time on these NTP servers may not be synchronized. As a result, Cisco MediaSense servers switch their times based on the currently-synchronized NTP server.

|-
! '''Recommended Action'''
|
Verify that both NTP servers provide synchronized times.

|-
! '''Release'''
|
Release 8.5(1), Release 8.5(2), and Release 8.5(3).

|-
! '''Associated CDETS #'''
|
None.

|}

[[Category:Cisco_MediaSense,_Release_8.5]]