Skip to main content
A
Albuendi
Participant
February 4, 2011
Question

FMS 3.5, fixing timeouts reported by fmscheck

  • February 4, 2011
  • 1 reply
  • 836 views

Hello,

I have a script that runs fmscheck every 5 minutes against my FMS 3.5 for checking server status. In the past, some of the applications stopped working randomly and this scripts reboots server if it finds that application doesn't work.

This has worked flawlessly for almost a year, but recently I started to get alerts showing that script is getting timeouts.

This is the log when script timeouts. Timeout is always in the same point, not when publishing / unpublishing, but right after connection:

#Version 1.0.0 r15

#2011-02-04 17:56:01

#Software: Adobe Flash Media Server Check 1.0.0 r15

#2011-02-04

#Fields: date    time        x-event                             x-sname

2011-02-04     17:56:01     Connect                              rtmp://localhost:1935/audiotest

2011-02-04     17:56:01     NetConnection.Connect.Success        Connection succeeded.

2011-02-04     17:56:01     Success                              StreamCreated

2011-02-04     17:56:01     Success                              StreamCreated

2011-02-04     17:56:17     Timeout                              -

And this is the exact line used in fmscheck:

./fmscheck --host localhost --port 1935 --app appname --publish foo --pubfile sample.flv  --logfile fmscheck.log

I am worried that if fmscheck is getting timeouts, some of my users may be getting timeouts too..

May this error be related with the number of concurrent users ?

Any hints on how can I locate the cause and / or what values on config file may help to reduce timeouts ?

Thanks !

    This topic has been closed for replies.

    1 reply

    S
    SE_0208
    Participating Frequently
    February 9, 2011

    Do you see any errors in master.00.logs, edge.00.logs & core.00.logs when timeout happens?

    A
    AlbuendiAuthor
    Participant
    February 9, 2011

    Nothing at all. I am pasting here log lines:

    This is the result of fmscheck:

    2011-02-09     08:04:01     Connect                              rtmp://localhost:1935/appname

    2011-02-09     08:04:02     NetConnection.Connect.Success        Connection succeeded.

    2011-02-09     08:04:02     Success                              StreamCreated

    2011-02-09     08:04:02     Success                              StreamCreated

    2011-02-09     08:04:18     Timeout                              -

    [Timeout detected. Service restart starts here..]

    edge

    2011-02-09      08:04:22        9905    (i)2581250      Edge disconnected from core (10160).    -

    2011-02-09      08:04:23        9905    (i)2581250      Edge disconnected from core (9908).     -

    2011-02-09      08:04:23        9905    (i)2581250      Edge disconnected from core (10621).    -

    core

    2011-02-09      08:04:22        10160   (i)2581247      Core (10160) disconnected from edge.    -

    2011-02-09      08:04:23        10621   (i)2581247      Core (10621) disconnected from edge.    -

    2011-02-09      08:04:23        9908    (i)2581247      Core (9908) disconnected from edge.     -

    master

    #Date: 2011-02-09

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

    2011-02-09      08:05:30        13486   (i)2581173      FMS detected IPv6 protocol stack!       -

    2011-02-09      08:05:30        13486   (i)2581173      FMS config <NetworkingIPv6 enable=false>        -

    2011-02-09      08:05:30        13486   (i)2581173      FMS running in IPv4 protocol stack mode!        -

    2011-02-09      08:05:30        13486   (i)2581173      Host: XXXXX.com IPv4: x.x.x.x -

    2011-02-09      08:05:30        13486   (i)2571011      Server starting...      -

    And just for the records, on access.log I got this lines related to fmscheck

    access.log

    connect-pending session 2011-02-09      08:04:02        CET     127.0.0.1       x.x.x.x     10160   0       6       _defaultRoot_   _defaultVHost_  appname        _definst_       0       100     127.0.0.1       rtmp    -       rtmp://localhost:1935/appname rtmp://localhost:1935/appname -       rtmp://localhost:1935/appname FMSc/0.9 (compatible; FMSc/0.9) 8605031244008345960     3073    3073    normal  -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -

    connect session 2011-02-09      08:04:02        CET     127.0.0.1       x.x.x.x     10160   0       6       _defaultRoot_   _defaultVHost_  appname        _definst_       0       200     127.0.0.1       rtmp    -       rtmp://localhost:1935/appname rtmp://localhost:1935/appname -       rtmp://localhost:1935/appname FMSc/0.9 (compatible; FMSc/0.9) 8605031244008345960     3073    3073    normal  -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -       -

    But no lines regarding neither publish nor record. The rest of connections from remote clients seems working as usual.

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