Inspiring

Question

Core is no longer active

Forum|Forum|14 years ago
March 25, 2012
1 reply
1151 views

Im running FMS 3.5.7 on Windows 2008 server, for video chat application that has up to 700 people making 2000-3000 FMS connections.

My application got restarted after less then 2 days running with these errors in master.log:

2012-03-25

00:45:56

2140

(i)2581223

Core (4824) is no longer active.

-

2012-03-25

00:45:56

2140

(w)2581256

Core (4824) _defaultRoot_:_defaultVHost_:::_2 experienced 1 failure!

-

2012-03-25

00:45:56

2140

(i)2581221

Core (7944) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app -inst -tag "_2" -conf "C:\Program Files (x86)\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_2".

-

2012-03-25

00:45:59

2140

(i)2581223

Core (4824) is no longer active.

-

2012-03-25

00:52:31

2140

(i)2581223

Core (7944) is no longer active.

-

2012-03-25

00:52:31

2140

(w)2581256

Core (7944) _defaultRoot_:_defaultVHost_:::_2 experienced 1 failure!

-

2012-03-25

00:52:31

2140

(i)2581221

Core (5604) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app -inst -tag "_2" -conf "C:\Program Files (x86)\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_2".

-

2012-03-25

00:52:35

2140

(i)2581223

Core (7944) is no longer active.

Can you please tell me could it have something to do with these error in core.log that happend at almost same time:

2012-03-25 00:43:07 4824 (e)2611029 Bad network data; terminating connection : chunkstream error:message length 14515351 is longerthan max rtmp packet length -

2012-03-25 00:43:07 4824 (e)2631029 Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: _defaultVHost_, IP: 201.191.198.190, App: videochat/_definst_, Protocol: rtmp, Client: 7021207954417413490, Handle: 3062959962) : E 00 00 4 16 C1 @ 00 80 06 A0 P 0A BE BC N @ BC ; EA DF EA 00 P C1 t $ CA 00 00 00 00 80 02 00 D EA 00 00 02 04 05 B4 01 03 -

And how can I prevent that kind of error?

This topic has been closed for replies.

Participant

We have Adobe Flash Media Server 4.5.0 r297 x64 running on Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-34-generic x86_64), but also on Windows 2003 Server.

Our application (for a collaborative service) has live audio/video streaming and widely uses shared object too.

We also have similar failures on FMS core, which corresponds to a disconnection on the client-side.

Sometimes disconnections happen with high frequency as in the following log:

master.log

2013-03-14	15:06:18	21087	(i)2581223	Core (31761) is no longer active.	-
2013-03-14	15:06:18	21087	(w)2581256	Core (31761) _defaultRoot_:_defaultVHost_:::_0 experienced 1 failure!	-
2013-03-14	15:06:22	21087	(i)2581221	Core (31921) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app -inst -tag "_0" -console -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:::_0".	-
2013-03-14	15:11:53	21087	(i)2581223	Core (31921) is no longer active.	-
2013-03-14	15:11:53	21087	(w)2581256	Core (31921) _defaultRoot_:_defaultVHost_:::_0 experienced 1 failure!	-
2013-03-14	15:12:04	21087	(i)2581221	Core (32088) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app -inst -tag "_0" -console -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:::_0".	-
2013-03-14	15:19:58	21087	(i)2581223	Core (32088) is no longer active.	-
2013-03-14	15:19:58	21087	(w)2581256	Core (32088) _defaultRoot_:_defaultVHost_:::_0 experienced 1 failure!	-
2013-03-14	15:20:03	21087	(i)2581221	Core (32251) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app -inst -tag "_0" -console -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:::_0".	-
2013-03-14	15:22:13	21087	(i)2581223	Core (32251) is no longer active.	-
2013-03-14	15:22:13	21087	(w)2581256	Core (32251) _defaultRoot_:_defaultVHost_:::_0 experienced 1 failure!	-
2013-03-14	15:23:34	21087	(i)2581221	Core (32410) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app -inst -tag "_0" -console -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:::_0".	-

core.log

Normal trace, no errors or warnings:

#Date: 2013-03-14

#Fields: date time x-pid x-status x-ctx x-comment

2013-03-14 15:06:22 31921 (i)2581237 Starting admin app on core (31921). -

2013-03-14 15:06:22 31921 (i)2581238 Core (31921) connecting to admin. -

2013-03-14 15:06:22 31921 (i)2581231 Core (31921) connected to admin. -

2013-03-14 15:06:22 31921 (i)2581234 Core (31921) connection to admin accepted. -

2013-03-14 15:06:22 31921 (i)2631174 Listener started ( _defaultRoot_ ) : 127.0.0.1:19351 (rtmfp-core)/v4 -

2013-03-14 15:06:22 31921 (i)2631174 Listener started ( _defaultRoot_ ) : 172.24.48.159:19351 (rtmfp-core)/v4 -

2013-03-14 15:06:22 31921 (i)2631174 Listener started ( _defaultRoot_ ) : 172.20.10.12:19351 (rtmfp-core)/v4 -

2013-03-14 15:06:22 31921 (i)2631509 Public rtmfp-core addresses for listener _defaultRoot_ are: 127.0.0.1:19351;172.24.48.159:19351;172.20.10.12:19351 -

2013-03-14 15:06:22 31921 (i)2581246 Core (31921) sending register cmd to edge. -

#Date: 2013-03-14

#Fields: date time x-pid x-status x-ctx x-comment

2013-03-14 15:12:04 32088 (i)2581237 Starting admin app on core (32088). -

2013-03-14 15:12:04 32088 (i)2581238 Core (32088) connecting to admin. -

2013-03-14 15:12:04 32088 (i)2581231 Core (32088) connected to admin. -

application.log

Normal trace, no errors or warnings.

At this time our application is still in a debugging phase and so has much tracing.

Someone has any idea on these severe troubles?

Thanks in advance.