Wowza Community

I have problems by "client connectionClosed [1307077980] pingtimeout"...

Hello…

I have live service for 24 hours and also recording it through WowzaStreamingEngine’s live channel.

But it has occurrence of recording stopped abnormally.

At that time, i found “pingtimeout” from logs.

I was recording using the FFMPEG through rtmp://123.111.139.101:1935/live/hmall.stream.

I don’t know why it does…

thanks regard

: VHOST.xml
<Application>
			<ApplicationTimeout>60000</ApplicationTimeout>
			<PingTimeout>12000</PingTimeout>
			<UnidentifiedSessionTimeout>30000</UnidentifiedSessionTimeout>
			<ValidationFrequency>20000</ValidationFrequency>
			<MaximumPendingWriteBytes>0</MaximumPendingWriteBytes>
			<MaximumSetBufferTime>60000</MaximumSetBufferTime>
		</Application>

: logs
2015-05-19	13:42:08	KST	comment	session	INFO	401	1307077980	client connectionClosed [1307077980] pingtimeout	_defaultVHost_	live	_definst_	127.151	[any]	1935	rtmp://123.111.139.101:1935/live	123.111.139.101	rtmp	-	LNX 9,0,124,2	1307077980	3588	29817897	-	-	-	-	-	-	-	-	-	-	-	-	-	rtmp://123.111.139.101:1935/live	-
2015-05-19	13:42:08	KST	stop	stream	INFO	200	hmall.stream	-	_defaultVHost_	live	_definst_	127.067	[any]	1935	rtmp://123.111.139.101:1935/live	123.111.139.101	rtmp	-	LNX 9,0,124,2	1307077980	3588	29817897	1	112683	0	29739374	hmall.stream	-	-	-	-	-	rtmp://123.111.139.101:1935/live/hmall.stream	rtmp://123.111.139.101:1935/live/hmall.stream	-	rtmp://123.111.139.101:1935/live	-
2015-05-19	13:42:08	KST	destroy	stream	INFO	200	hmall.stream	-	_defaultVHost_	live	_definst_	127.068	[any]	1935	rtmp://123.111.139.101:1935/live	123.111.139.101	rtmp	-	LNX 9,0,124,2	1307077980	3588	29817897	1	-	0	29739374	hmall.stream	-	-	-	-	-	rtmp://123.111.139.101:1935/live/hmall.stream	rtmp://123.111.139.101:1935/live/hmall.stream	-	rtmp://123.111.139.101:1935/live	-
2015-05-19	13:42:08	KST	disconnect	session	INFO	200	1307077980	-	_defaultVHost_	live	_definst_	127.152	[any]	1935	rtmp://123.111.139.101:1935/live	123.111.139.101	rtmp	-	LNX 9,0,124,2	1307077980	3588	29817897	-	-	-	-	-	-	-	-	-	-	-	-	-	rtmp://123.111.139.101:1935/live	-
2015-05-19	13:42:08	KST	comment	server	INFO	200	-	onDisconnect: 1307077980	_defaultVHost_	live	_definst_	1741059.488	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
2015-05-19	13:42:08	KST	seek	stream	INFO	200	7df25851-29bb-48ce-b3ed-12d715903294/2015/05/19/cb9c4bd8-a090-4221-bc8f-8e325e36fc6f/3a5313c7-04b5-4d57-883f-cf7fea42e265.mp4	-	_defaultVHost_	streams	_definst_	13.263	123.111.139.103	1935	http://123.111.139.103:1935/streams/_definst_/mp4:7df25851-29bb-48ce-b3ed-12d715903294/2015/05/19/cb9c4bd8-a090-4221-bc8f-8e325e36fc6f/3a5313c7-04b5-4d57-883f-cf7fea42e265.mp4/playlist.m3u8?wowzaplaystart=5904000&wowzaplayduration=1371000	125.185.190.208	http (cupertino)	http://www.hyundaihmall.com/wenUploader/jwplayer/plugin/HLSProvider5.swf	Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; InfoPath.2; OfficeLiveConnector.1.5; OfficeLivePatch.1.3; .NET4.0C; moasigns=1.0.31; moasigns=1.0.31)	120344093	0	24866504	28491	6984211	0	24856044	7df25851-29bb-48ce-b3ed-12d715903294/2015/05/19/cb9c4bd8-a090-4221-bc8f-8e325e36fc6f/3a5313c7-04b5-4d57-883f-cf7fea42e265.mp4	wowzaplaystart=5904000&wowzaplayduration=1371000	7df25851-29bb-48ce-b3ed-12d715903294/2015/05/19/cb9c4bd8-a090-4221-bc8f-8e325e36fc6f/3a5313c7-04b5-4d57-883f-cf7fea42e265.mp4	mp4	4078550841	15291.944	http://123.111.139.103:1935/streams/_definst_/mp4:7df25851-29bb-48ce-b3ed-12d715903294/2015/05/19/cb9c4bd8-a090-4221-bc8f-8e325e36fc6f/3a5313c7-04b5-4d57-883f-cf7fea42e265.mp4/playlist.m3u8?wowzaplaystart=5904000&wowzaplayduration=1371000	http://123.111.139.103:1935/streams/_definst_/mp4:7df25851-29bb-48ce-b3ed-12d715903294/2015/05/19/cb9c4bd8-a090-4221-bc8f-8e325e36fc6f/3a5313c7-04b5-4d57-883f-cf7fea42e265.mp4/playlist.m3u8	wowzaplaystart=5904000&wowzaplayduration=1371000	http://123.111.139.103:1935/streams/_definst_/mp4:7df25851-29bb-48ce-b3ed-12d715903294/2015/05/19/cb9c4bd8-a090-4221-bc8f-8e325e36fc6f/3a5313c7-04b5-4d57-883f-cf7fea42e265.mp4/playlist.m3u8	wowzaplaystart=5904000&wowzaplayduration=1371000
2015-05-19	13:42:09	KST	comment	session	INFO	401	2031812717	client connectionClosed [2031812717] pingtimeout	_defaultVHost_	live	_definst_	127.284	[any]	1935	rtmp://123.111.139.101:1935/live	123.111.139.101	rtmp	-	LNX 9,0,124,2	2031812717	3588	29758761	-	-	-	-	-	-	-	-	-	-	-	-	-	rtmp://123.111.139.101:1935/live	-

Hello.

This is a normal occurrence. Wowza is disconnecting its side of a NetConnection when Wowza no longer senses the client that established that connection. House cleaning. So, by itself, this is not a problem.

This is most likely related to poor internet connections. And Wowza has to deal with lost connections, Wowza disconnects when it senses a lost connection. You do have control of this through the Application.xml /PingTimeOut and /ValidationFrequency settings. These are documented in the configuration guide

PingTimeout

The time (in milliseconds) that the server will wait for a ping response from the client. The ping mechanism is an RTMP internal ping (not an ICMP ping) that’s used to validate a client connection. If set to 0, the server will wait indefinitely. If this value isn’t provided (section commented-out), the value set in the VHost.xml file is used.

ValidationFrequency

The time (in milliseconds) that the server will wait during server-to-client validation. Validation only occurs if the client stops sending data to the server. Validation is done by sending a ping request from the server to the client. If set to 0, the server won’t validate client connections.

regards,

Salvadore