Skip to main content
A
Anonymous
September 11, 2012
Question

AMS 5 - Assert failed

  • September 11, 2012
  • 1 reply
  • 3724 views

Hello,

I am running AMS 5 on Amazon and I`m facing some troubles.

I am running CentOS 5.5 on my server and when I run the command TOP I don`t the process amscore, but, my server is running.

When i run the command

./amscore, I get the following error:

Adobe Adobe Media Server (Core)Console mode.

FMS detected IPv6 protocol stack!

FMS config <NetworkingIPv6 enable=false>

FMS running in IPv4 protocol stack mode!

Host: ip-10-252-24-80 IPv4: 10.252.24.80

Assert failed in tincan/util/TCIpcQueue.cpp line 48

Server aborted.

Segmentation fault

When I run the command netstat -nap, I get this:

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address               Foreign Address             State            PID/Program name  

tcp        0      0 127.0.0.1:11110                       0.0.0.0:*                   LISTEN           2166/amsadmin      

tcp        0      0 0.0.0.0:1935                            0.0.0.0:*                   LISTEN           1446/amsedge    

tcp        0      0 127.0.0.1:19350                       0.0.0.0:*                   LISTEN           1446/amsedge       

tcp        0      0 0.0.0.0:1111                             0.0.0.0:*                   LISTEN           2166/amsadmin

tcp        0      0 127.0.0.1:11110             127.0.0.1:55331             ESTABLISHED      2166/amsadmin      

tcp        0      0 127.0.0.1:48667             127.0.0.1:19350             ESTABLISHED      2393/amscore       

tcp        0      0 127.0.0.1:11110             127.0.0.1:52737             ESTABLISHED      2166/amsadmin      

tcp        0      0 127.0.0.1:19350             127.0.0.1:48667             ESTABLISHED      1446/amsedge       

tcp        0      0 127.0.0.1:55183             127.0.0.1:1935              ESTABLISHED      2104/httpd         

tcp        0      0 127.0.0.1:55182             127.0.0.1:1935              ESTABLISHED      2104/httpd         

tcp        0      0 127.0.0.1:55181             127.0.0.1:1935              ESTABLISHED      2104/httpd         

tcp        0      0 127.0.0.1:55180             127.0.0.1:1935              ESTABLISHED      2104/httpd         

tcp        0      0 127.0.0.1:53028             127.0.0.1:19350             ESTABLISHED      1727/amscore       

tcp        0      0 127.0.0.1:19350             127.0.0.1:53028             ESTABLISHED      1446/amsedge       

tcp        0      0 127.0.0.1:1935              127.0.0.1:55183             ESTABLISHED      1446/amsedge       

tcp        0      0 127.0.0.1:1935              127.0.0.1:55182             ESTABLISHED      1446/amsedge       

tcp        0      0 127.0.0.1:1935              127.0.0.1:55181             ESTABLISHED      1446/amsedge       

tcp        0      0 127.0.0.1:1935              127.0.0.1:55180             ESTABLISHED      1446/amsedge       

tcp        0      0 127.0.0.1:52737             127.0.0.1:11110             ESTABLISHED      1727/amscore       

tcp        0      0 10.252.24.80:1935           201.45.72.62:65364          ESTABLISHED      1727/amscore       

tcp        0      0 127.0.0.1:55331             127.0.0.1:11110             ESTABLISHED      2393/amscore       

tcp        0      0 10.252.24.80:1111           189.29.131.28:62777         ESTABLISHED    2166/amsadmin      

tcp        0      0 10.252.24.80:1935           177.81.58.187:55591         ESTABLISHED      1727/amscore       

tcp        0      0 10.252.24.80:1935           201.28.179.130:16364        ESTABLISHED      1727/amscore       

tcp        0      1 10.252.24.80:1935           200.193.77.204:48404        LAST_ACK    -                  

tcp        0      0 :::8134                     :::*                        LISTEN      1441/httpd         

tcp        0      0 :::80                       :::*                        LISTEN      1441/httpd         

tcp        0      0 :::22                       :::*                        LISTEN      1345/sshd          

tcp        0   3632 ::ffff:10.252.24.80:22      ::ffff:201.28.179.130:26781 ESTABLISHED 2851/2             

tcp        0      0 ::ffff:10.252.24.80:22      ::ffff:177.139.162.15:54599 ESTABLISHED 2831/1             

tcp        0      0 ::ffff:10.252.24.80:22      ::ffff:177.139.162.15:64996 ESTABLISHED 2352/0             

udp        0      0 10.252.24.80:1935           0.0.0.0:*                               1446/amsedge       

udp        0      0 127.0.0.1:1935              0.0.0.0:*                               1446/amsedge       

udp        0      0 10.252.24.80:19350          0.0.0.0:*                               1446/amsedge       

udp        0      0 127.0.0.1:19350             0.0.0.0:*                               1446/amsedge       

udp        0      0 10.252.24.80:19351          0.0.0.0:*                               1727/amscore       

udp        0      0 127.0.0.1:19351             0.0.0.0:*                               1727/amscore       

udp        0      0 10.252.24.80:19352          0.0.0.0:*                               2393/amscore       

udp        0      0 127.0.0.1:19352             0.0.0.0:*                               2393/amscore       

udp        0      0 0.0.0.0:68                  0.0.0.0:*                               1223/dhclient

Thanks

This topic has been closed for replies.

1 reply

S
ShivenK
Inspiring
September 12, 2012

Hi,

I would recommend that you destroy the instance and create a fresh one.

When the instance boots, the AMS services are up and running by default.

Thanks,

Shiven

A
Anonymous
September 13, 2012

That exaclty what I did, it happened on both instances.

Shiven,

I have two main applications, audio and video recorder.

I have used Influxis and Amazon, and found the same issue on both Servers, already checked my application.

The applicatiosn works pretty well, but at some time it crashes, and make the console show a wrong number of connected clients and becomes unresponsive. to make the server restart again ts to restart the server completely.

Since it does not cause any client limit exceed or fatal error, there`s no log of that at all.

How can I check if my application is running properly, using cores, closing idle connections and etc?

I really need some guide here, My server crashes at least twice a day, no kidding.

Thanks.

S
ShivenK
Inspiring
September 14, 2012

Hi Jeff,

Are you sure there is no core, master log that mentions about the crash?

What is the instance type that you are using?

What is the estimate load on the server at the time of crash?

Thanks,

Shiven

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices