Skip to main content
A
awebsupport
Participating Frequently
October 10, 2011
Question

FMS_4_5_0_r297 and Debian 5.0 x64

  • October 10, 2011
  • 1 reply
  • 2594 views

Hello!

I'm testing the new FMS 4.5 with Debian 5 amd_64 with kernel 2.6.32 and 2.7-18lenny7. I know that Debian is not officialy supported but we use Debian as the main distribution on all our servers.

Seems to have a compatibily problem. The server crach randomly and after we got error 1000 when we try to stream a video.

I've found this in core.00.log:

#Date: 2011-10-10

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

2011-10-10      13:37:46        2220    (i)2581237      Starting admin app on core (2220).      -

2011-10-10      13:37:46        2220    (i)2581238      Core (2220) connecting to admin.        -

2011-10-10      13:37:46        2220    (i)2581231      Core (2220) connected to admin. -

2011-10-10      13:37:46        2220    (i)2581234      Core (2220) connection to admin accepted.       -

2011-10-10      13:37:46        2220    (i)2631174      Listener started ( _defaultRoot_ ) : 127.0.0.1:19351 (rtmfp-core)/v4    -

2011-10-10      13:37:46        2220    (i)2631174      Listener started ( _defaultRoot_ ) : 195.154.234.237:19351 (rtmfp-core)/v4      -

2011-10-10      13:37:46        2220    (i)2631509      Public rtmfp-core addresses for listener _defaultRoot_ are: 127.0.0.1:19351;195.154.234.237:19351      -

2011-10-10      13:37:46        2220    (e)2631007      Failed to create thread (TCPollThread Ctor).    -

2011-10-10      13:37:46        2220    (e)2581279      Assert failed in tincan/util/TCAsyncIO.cpp line 1036    -

2011-10-10      13:37:46        2220    (e)2631007      Failed to create thread (TCPollThread Ctor).    -

2011-10-10      13:37:46        2220    (e)2581279      Assert failed in tincan/util/TCAsyncIO.cpp line 1046    -

2011-10-10      13:37:46        2220    (e)2581279      Assert failed in tincan/util/TCAsyncIO.cpp line 1051    -

2011-10-10      13:37:46        2220    (e)2581279      Assert failed in tincan/util/TCAsyncIO.cpp line 1053    -

2011-10-10      13:37:46        2220    (e)2661007      Failed to create thread (TCServerConnector::startConnector).    -

2011-10-10      13:37:46        2220    (e)2581279      Assert failed in tincan/server/core/FCSRemoteConnector.cpp line 89      -

2011-10-10      13:37:46        2220    (e)2571122      Server aborted. -

In production, we curently use FMS_4_0_1_r2009 x386 version with Debian 5.0 without problem (in fact, we use FMS on Debian since version 3 without problem).

Does someone have an idea of the problem?

    This topic has been closed for replies.

    1 reply

    Nikhil_Kalyan
    Nikhil_Kalyan
    Participating Frequently
    October 10, 2011

    Hi ,

    Thanks for moving to 4.5

    Is this issue something to do with epoll ? I guess the async assert indicates that a poll thread took longer than expected to stop. Can you please confirm ? Or disable epoll and see if it works ok ?

    A
    awebsupportAuthor
    Participating Frequently
    October 10, 2011

    I realy don't know if this is a epoll issue or if this message have something to do with the streaming problem. Disabling epoll is not easy for us as we use openvz container with only one shared 2.6.32 kernel.

    In syslog, I have found this message too.

    Oct 10 14:50:17 fms2 Adaptor[3166]: Listener started ( _defaultRoot_ ) : 127.0.0.1:19351 (rtmfp-core)/v4

    Oct 10 14:50:17 fms2 Adaptor[3166]: Listener started ( _defaultRoot_ ) : 195.154.234.237:19351 (rtmfp-core)/v4

    Oct 10 14:50:17 fms2 Adaptor[3166]: Public rtmfp-core addresses for listener _defaultRoot_ are: 127.0.0.1:19351;195.154.234.237:19351

    Oct 10 14:50:17 fms2 Adaptor[3166]: Failed to create thread (TCPollThread Ctor).

    Oct 10 14:50:17 fms2 Adaptor[3166]: Failed to create thread (TCPollThread Ctor).

    Oct 10 14:50:17 fms2 Connector[3166]: Failed to create thread (TCServerConnector::startConnector).

    Oct 10 14:50:17 fms2 Service[3166]: Server aborted.

    Oct 10 14:50:18 fms2 Server[716]: System memory load (13) is now below the maximum threshold.

    Oct 10 14:50:19 fms2 Server[739]: System memory load (404750345) is high.

    Oct 10 14:50:22 fms2 Server[739]: System memory load (9) is now below the maximum threshold.

    Oct 10 14:50:31 fms2 Server[1227]: System memory load (404750345) is high.

    Oct 10 14:50:32 fms2 Server[739]: System memory load (404750345) is high.

    I have to wait for next FMS crash to try to look for more message in logs. I'll may be found more detail.

    Or I can do a test with the same system but running with a 2.6.18 kernel. I still have one cluster node with this kind of old kernel.

    Nikhil_Kalyan
    Nikhil_Kalyan
    Participating Frequently
    October 10, 2011

    Sure.

    Please let us know the findings. But i still stick to epoll till there is anything else that comes up.

    In server.xml of FMS,

    Root/Server/ResourceLimits/Connector/RTMP/Epoll

    <Epoll>false</Epoll>

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