Upgrading to FMS

Do I need to uninstall FCS 1.5 before upgrading to FMS 2.0?
I'm backing up all the files from FCS 1.5.

In my experience, it's not an absolute must to uninstall FCS,
but you don't want both running at the same time. I have a
development server with 1.5 and 2.0 both installed, and I never
have a problem with either (I just don't run them at the same
time).

Similar Messages

  • Upgrade from FMS 3.5 to Flash Media Interactive Server no apps working

    I sucessfully upgraded from FMS to FMIS. In the Admin it shows that the license is now Flash Media Interactive Server r405 I believe.
    The live and vod services continue to work as expected.
    On a separate development server I have developed a number of applications that I want to move to the new production server. Nothing connects at all on the new server. In the Admin, all the applications show as being available.
    Is there something I need to do to make it work?
    I don't want to post details on line but willing to share if someone can help out?
    Boss really wants to make the $4000 upgrade work if you know what I mean...

    Thank you. If you don't mind, I would prefer to do it here although I am
      happy to post the final results for the thread. I used to work at MM
    and Adobe before that so I think there is great value in one to many
    support.
    1. How did you upgrade - using license file or license keys - i suppose license key?
    License key. Just copied and pasted into the server admin's license screen.
    2. Did you restart your server after putting in the serial key? If not , please restart, for licensing changes to take place, you need to restart the server.
    Yes. I did, but I did it from the admin, not the start and stop applets.
    3. If you have restarted and you are facing same issue - can you check your logs and see what error messages are you getting, you can check edge.00.log,core.00.log and master.00.log.
    This is from the Edge.log. I am not really sure what it says, but it
    coincides with when I entered the key.
    #Version: 1.0#Start-Date: 2010-08-03 07:11:16
    #Software: Adobe Flash Media Server 3.5.0 r405
    #Date: 2010-08-03
    #Fields:
    date     time     x-pid     x-status     x-ctx     x-comment2010-08-03     07:11:15     52 36     (i)2581250     
    Edge disconnected from core (9412).     -2010-08-03     08:51:40     5236     (i)2581252     
    Registering core (11384).     -2010-08-03     11:37:14     5236     (i)2581250     
    Edge disconnected from core (11384).     -2010-08-03     11:37:31     5236     (i)2581252     
    Registering core (12104).     -2010-08-03     17:06:16     5236     (i)2581250     
    Edge disconnected from core (12104).     -2010-08-03     17:06:16     5236     (i)2581250     
    Edge disconnected from core (5264).     -
    #Date: 2010-08-03
    #Fields:
    date     time     x-pid     x-status     x-ctx     x-comment2010-08-03     17:06:38     60 80     (i)2581173     
    Host: C29527-121731 IPv4: 10.0.0.2     -2010-08-03     17:06:38     6080     (i)2631174     
    Listener started ( defaultRoot_edge1 ) :
    localhost:19350/v4     -2010-08-03     17:06:39     6080     (i)2631174     
    Listener started ( defaultRoot_edge1 ) :
    80/v4     -2010-08-03     17:06:39     6080     (i)2631174     
    Listener started ( defaultRoot_edge1 ) :
    1935/v4     -2010-08-03     17:06:39     6080     (i)2581252     
    Registering core (6052).     -2010-08-03     17:06:40     6080     (i)2581252     
    Registering core (6120).     -
    #End-Date: 2010-08-05 05:43:58
    4. If I am not mistaken you have upgraded from Streaming Server to Interactive Server, am i right?
    Well the name on the screen was Flash Media Server 3.5 It streams just
    fine, but I get really confused with all the names of the servers frankly.
    5. Also which version of FMS are you using?
    3.5
    Thank you so much for your help. I am trying not to have to deinstall
    the server and reinstall it. If I can avoid that, please let me know.
    FWIW, this is the code I used to test to see if the server was accepting
    connections to an unsigned app.
    package
    import flash.net.NetConnection;
    import flash.display.Sprite;
    import flash.text.TextField;
    import flash.events.NetStatusEvent;
    public class FMS3Connect extends Sprite
    private var nc:NetConnection;
    private var rtmpNow:String;
    private var msg:String;
    private var connectText:TextField;
    private var posX:Number;
    function FMS3Connect ()
    nc=new NetConnection();
    nc.addEventListener (NetStatusEvent.NET_STATUS,checkConnect);
    rtmpNow="rtmp://www.letsgoexpo.com/connect";
    trace (rtmpNow);
    //rtmpNow="rtmpe:/connect";
    nc.connect (rtmpNow);
    private function checkConnect (event:NetStatusEvent):void
    connectText=new TextField();
    msg=event.info.code;
    connectText.width=250;
    connectText.text=msg;
    addChild (connectText);
    posX=connectText.stage.stageWidth;
    connectText.x=100;
    connectText.y=175;
    Of course it has a little SWF that goes with it, but there isn't
    anything there except this.
    On the development server this works and shows the connect.
    Thanks for your help. I will be checking mail frequently after noon
    pacific. I don't know where you are located so I guess you get mail out
    whenver you can.
    Matt Brown - Moss Beach Ceramics     
    email: [email protected]
    web: www.mossbeachceramics.com     
    store: mossbeachceramics.etsy.com
    cell: (650) 518-0250

  • Upgrading from FMS to FMIS

    Good afternoon,
    Were in the process of upgrading the FMS server licence to a FMIS licence.
    My question is that when we upgrade will we lose any of the functionality of FMS3.0 that is not present in FMIS.
    The FMS is currently used for direct streaming.
    Thanks in advance
    Thomas
    Qwise

    FMIS contains all the functionality of FMS plus additional features to power interactive applications. Take a look at Adobe's feature comparison chart to see the differences:
    http://www.adobe.com/products/flashmediaserver/compare/

  • Can we Upgrade FMS 3.5.1 to 3.5.5

    do we need to pay anything for Upgrading FMS 3.5.1 to 3.5.5 ?
    if it is free then updating to latest available version possible or only to 3.5 series?
    And also please provide me with the upgrading steps.. someone who already did this upgrading in realtime successfully help me with those real steps..
    Regards,

    Yes you can upgrade from FMS 3.5.1 to 3.5.5 for free. Updating to latest version for 4.0 , you would have to pay for the upgrade but anything in 3.5 series would be free.
    See this link might be of some help: http://help.adobe.com/en_US/FlashMediaServer/3.5_InstallingFMS/WS5b3ccc516d4fbf351e63e3d11 9ed5bf6c6-7ff2.html

  • FMS license key

    Hi
    Can we use same license key for more than one FMS server? If we use one key for other server then what will be the effect on the FMS.
    Also one more think can we use one license key of one version to other version? For example can we use license key of FMS 3.0 for FMS 3.5.
    How to upgrade from FMS 2.0.5 to FMS 3.0 and may we know the cost of upgradation?
    Thanks

    Can we use same license key for more than one FMS server? - NO - its against EULA
    Also one more think can we use one license key of one version to other version - NO - license keys are specific to versions
    How to upgrade from FMS 2.0.5 to FMS 3.0 and may we know the cost of upgradation? - You need to get upgrade key + install newer version whichever you want to upgrade to. As far as cost is concerned - i think you can check that on Adobe site. I am not sure whether site will show upgrade from 2.0.5 to 3.0 as its little older version upgrade.

  • FMS proxying HTTP does not close sockets correctly?

    Hi,
    So, after waiting for a while, we decided to upgrade our streamers to FMS 3.5.3 and set them up to proxy HTTP requests to a lighttpd server instead of the "built in" Apache. With the previous version 3.5 of FMS, we had problems of FMS hanging up after a while and stopping relaying requests, generally a few hours, even when it did not serve a lot of requests. With version 3.5.3, we had great hopes that this problem had disappeared as we had FMS running for more than a month on a test server. So we did the upgrade and we encounter another problem:
    After less that one day of activity, our servers crashed for an unknown reason, almost at the same time. Analysing the logs, I saw out of memory messages, but how could two linux servers stop working in the same 5 minutes interval. I supposed there was a power failure of some sort. And I kept analysing because the sysadmins in the server room swore that they saw out of memory kernel panic on the consoles. After a bit of investigation, I found the reasons: the TCP connexions between FMS and the lighttpd server are stacking up and fill the OS network memory! Now, I don't know who is the culprit:
    FMS code does not manage correctly HTTP proxy sessions?
    lighttpd does not handle correctly HTTP proxying from FMS and does not close correctly the sessions?
    Our Ubuntu linux network stack is not correctly configured to manage so many connexions?
    Here are the details, any assistance is welcome!
    The servers: linux Ubuntu 8.04 with 8 GB RAM.
    FMS 3.5.3 proxying to lighttpd 1.4.19 listening on port 81. FMS and lighttpd are set up on the same server.
    The streamer receives many (> 10/s) HTTP requests from iPhones which are proxied to lighttpd. iPhones request partial content and lighttpd is well suited for these type of requests.
    Locking at the state of the TCP stack:
    # netstat -st
    IcmpMsg:
        InType3: 6
        InType8: 5501
        OutType0: 5501
        OutType3: 6
    Tcp:
        101662 active connections openings
        1192680 passive connection openings
        33 failed connection attempts
        177391 connection resets received
        1653 connections established
        73559682 segments received
        70196072 segments send out
        165137 segments retransmited
        0 bad segments received.
        37219 resets sent
    UdpLite:
    TcpExt:
        22 resets received for embryonic SYN_RECV sockets
        141884 packets pruned from receive queue because of socket buffer overrun
        2052 packets pruned from receive queue
        40293 TCP sockets finished time wait in fast timer
        801 time wait sockets recycled by time stamp
        711318 delayed acks sent
        2401 delayed acks further delayed because of locked socket
        Quick ack mode was activated 535 times
        68554 packets directly queued to recvmsg prequeue.
        11705 bytes directly in process context from backlog
        341070 bytes directly received in process context from prequeue
        5114830 packet headers predicted
        22083 packets header predicted and directly queued to user
        32542120 acknowledgments not containing data payload received
        25289961 predicted acknowledgments
        9191 times recovered from packet loss due to fast retransmit
        6222 times recovered from packet loss by selective acknowledgements
        Detected reordering 7 times using FACK
        Detected reordering 1 times using SACK
        Detected reordering 7 times using reno fast retransmit
        Detected reordering 9 times using time stamp
        15 congestion windows fully recovered without slow start
        42 congestion windows partially recovered using Hoe heuristic
        17 congestion windows recovered without slow start by DSACK
        16517 congestion windows recovered without slow start after partial ack
        51 TCP data loss events
        3916 timeouts after reno fast retransmit
        3372 timeouts after SACK recovery
        10048 timeouts in loss state
        9157 fast retransmits
        6 forward retransmits
        28990 retransmits in slow start
        30176 other TCP timeouts
        7656 classic Reno fast retransmits failed
        95 SACK retransmits failed
        2738020 packets collapsed in receive queue due to low socket buffer
        52 DSACKs sent for old packets
        52 DSACKs received
        3 connections reset due to unexpected data
        74950 connections reset due to early user close
        2846 connections aborted due to timeout
        TCP ran low on memory 10 times
        TCPDSACKIgnoredOld: 41
    IpExt:
    The last red line can be visualised below; sometimes the server crashes in out of memory kernel panic...
    And if you compare with previous behavior, you can tell when we did the upgrade to FMS 3.5.3...
    A few words on our previous configuration with FMS 3.5. To be able to accept HTTP requests, we have a front load balancer which is able to route HTTP requests to lighttpd and RTMP requests to FMS. But with this configuration, we don't benefit from the ability of FMS to fallback to RTMPT for clients behind a proxy or proxy ol' HTTP requests... With the previous configuration, we never had so many connections active simultaneously: we change from 200 max to more than 7000 with FMS 3.5.3 in proxy!
    Some figures on what exactly happens:
    # netstat -tn | grep :81 | awk '{print $6}' | sort | uniq -c
         20 CLOSE_WAIT
       2245 ESTABLISHED
       1236 FIN_WAIT1
          5 TIME_WAIT
    # netstat -tn
    Active Internet connections (w/o servers)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State
    tcp        0 275841 127.0.0.1:81            127.0.0.1:45088         FIN_WAIT1
    tcp   562347      0 127.0.0.1:55150         127.0.0.1:81            ESTABLISHED
    tcp        0 225152 127.0.0.1:81            127.0.0.1:34856         ESTABLISHED
    tcp        0 238081 127.0.0.1:81            127.0.0.1:54310         FIN_WAIT1
    tcp        0 114433 127.0.0.1:81            127.0.0.1:51810         FIN_WAIT1
    tcp   670800      0 127.0.0.1:40746         127.0.0.1:81            ESTABLISHED
    tcp   597444      0 127.0.0.1:40654         127.0.0.1:81            ESTABLISHED
    tcp   592810      0 127.0.0.1:40669         127.0.0.1:81            ESTABLISHED
    tcp        0 103168 127.0.0.1:81            127.0.0.1:54544         ESTABLISHED
    tcp        0 201344 127.0.0.1:81            127.0.0.1:40567         ESTABLISHED
    tcp        0      0 10.1.74.30:1935         10.1.74.2:60372         ESTABLISHED
    tcp   665360      0 127.0.0.1:45282         127.0.0.1:81            ESTABLISHED
    tcp        0 210432 127.0.0.1:81            127.0.0.1:40662         ESTABLISHED
    tcp        0 207361 127.0.0.1:81            127.0.0.1:44895         FIN_WAIT1
    tcp        0 109825 127.0.0.1:81            127.0.0.1:52144         FIN_WAIT1
    tcp        0 221825 127.0.0.1:81            127.0.0.1:54844         FIN_WAIT1
    tcp        0 103168 127.0.0.1:81            127.0.0.1:40791         ESTABLISHED
    tcp   782301      0 127.0.0.1:55074         127.0.0.1:81            ESTABLISHED
    tcp        0 219137 127.0.0.1:81            127.0.0.1:45040         FIN_WAIT1
    tcp        0 209921 127.0.0.1:81            127.0.0.1:44837         FIN_WAIT1
    tcp   574170      0 127.0.0.1:45275         127.0.0.1:81            ESTABLISHED
    tcp        0 252033 127.0.0.1:81            127.0.0.1:54907         FIN_WAIT1
    tcp        0 254977 127.0.0.1:81            127.0.0.1:54515         FIN_WAIT1
    tcp        0 142977 127.0.0.1:81            127.0.0.1:52129         FIN_WAIT1
    In case this is needed, FMS configuration is almost out of the box:
    _defaultRoot_/Adaptor.xml:
    <HTTPTunnel>
                    <Enable>true</Enable>
                    <NodeID></NodeID>
                    <IdlePostInterval>512</IdlePostInterval>
                    <IdleAckInterval>512</IdleAckInterval>
                    <IdleTimeout>60</IdleTimeout>
                    <MimeType>application/x-fcs</MimeType>
                    <WriteBufferSize>16</WriteBufferSize>
                    <SetCookie>true</SetCookie>
                    <Redirect enable="false" maxbuf="16384">
                            <Host port="80">:8080</Host>
                            <Host port="443">:8443</Host>
                    </Redirect>
                    <HttpProxy enable="true" maxbuf="16384">
                            <Host port="80">${HTTPPROXY.HOST}</Host>
                    </HttpProxy>
                    <NeedClose>true</NeedClose>
                    <MaxWriteDelay>20</MaxWriteDelay>
                    <MinWriteDelay>12</MinWriteDelay>
                    <MaxHeaderLineLength>1024</MaxHeaderLineLength>
    </HTTPTunnel>
    I've tried changing lighttpd configuration to handle KeepAlive session or not, it has no influence on the behaviour.
    If you spot a configuration mistake or have any idea, I'm ready to test it as soon as possible... Asa?
    Thanks

    Has this been fixed? What was done?
    We have been having the same issue. We worked on it with Adobe support and thought it might have been fixed with a "patched" version of FMS that was created to solve the problem. However, we still see the issue (recently we had a huge increase in load due to an annual event).
    Over time, when we run netstat, we see Apache connections (127.0.0.1:88134) stuck in a FIN_WAIT_1 state while the corresponding FMS processes (127.0.0.1:1025 to 5000) are in an ESTABLISHED state. It appears as though the connection is closed from the http proxy side while FMS doesn't acknowledge the close.
    We notice this behavior seems related to load. High load = connections getting hung more frequently. The only fix seems to be restarting the FMS service which restarts the embedded apache as well.
    I'm curious if you found a fix or even a workaround to help you cope with these connections. Even something to close them periodically would be a huge help. So far, we're resorting to an automatic restart of the server ever 2 days which is hardly a proper production solution.
    I would really appreciate any information you could provide with regards to your particular problem and whether or not it's been solved.
    An example (just a snippet) of the netstat monitor we have running each hour on the half-hour:
      Proto  Local Address          Foreign Address        State
      <snip FMS to Apache>
      TCP    127.0.0.1:2847         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2848         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2849         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2850         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2851         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2853         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2854         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2855         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2856         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2857         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2858         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2859         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2860         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2861         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2862         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2863         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2864         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2865         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2866         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2867         127.0.0.1:8134         ESTABLISHED
      TCP    127.0.0.1:2868         127.0.0.1:8134         ESTABLISHED
      </snip FMS to Apache>
      <snip Apache to FMS (corresponding entries)>
      TCP    127.0.0.1:8134         127.0.0.1:2847         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2848         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2849         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2850         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2851         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2853         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2854         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2855         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2856         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2857         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2858         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2859         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2860         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2861         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2862         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2863         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2864         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2865         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2866         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2867         FIN_WAIT_1
      TCP    127.0.0.1:8134         127.0.0.1:2868         FIN_WAIT_1
      </snip Apache to FMS>
    This particular log shows all ports between 1024 and 5000 in the same state as above. A restart resets all the connections and the process starts over. From my investigation, Apache seems to be acting properly. It tries to be a 'good citizen' and issue a graceful close that goes unacknowledged by FMS. Unfortunately, Apache doesn't go back to check a connection it considers closed, so they connection remains half-closed.
    Please, please let me know if you found anything out. Information on the web is scarce and I'm at my wit's end!

  • Future of FMS

    We want to purchase FMS but are in dilema because of flash streaming protocol is being depreciated. My question is what will happend when new HTML5 protocol will become standard for Android, IE, Mozilla, etc  (like HLS is now for iOS)? Will we just upgrade the FMS? What if WebM format will become standard? So my question is about the future...If we implement our video infrastructure with your FMS, would we need to abandon it after a year or two or will Adobe apply future protocol streaming standards for HTML5?

    Regarding the difference between FMS 4.5 and AMS 5 please see this excerpt from Product Manager's blog post
    Adobe Media Server 5 extends the innovation around Protected HTTP Dynamic Streaming (“PHDS”) which allows you to not worry about protection, just enable the encryption and protection and let Adobe do the rest. This release introduces Protected HLS streaming (“PHLS”) which uses the protection system to deliver the content license to the native IOS app without requiring a license server! So now you can deliver HTTP content to both native apps running on Apple devices and Flash-enabled devices using the same powerful Adobe Access client but without the Adobe Access license server. This technology is perfect for live events, news, sports or concerts, or if you just want to protect your video content without a complicated setup. We have juiced up the server with a much higher performing dynamic packager and encryption system that supports on demand and live streaming over both HDS and HLS that will power some of the most impressive events in 2012 that will change the way we think of multi-screen video. We have also extended the server’s utilities for offline media packaging to include HLS segmenting and encryption so you can prepare all your content in advance.
    Regd upgrade query, do you already have FMS 4.5 or were planning to buy one? AMS 5 is also available through Value Added reseller channel even now
    see the VAS list here - http://www.adobe.com/products/flashmediaserver/fmsp/var.html

  • .F4V support with FMS 3.5

    We're trying to stream Flash 9 .F4V files without any success so we upgraded to FMS 3.5, from 3.0, thinking that would do the trick, but they won't stream. I see MP4 support on Adobe's site, but not a word about .F4V support. Any advice out there? Thanks.

    F4V files are supported by FMS.  Have you run your particular files through FLV Check which is available for download from the FMS tools page?
    http://www.adobe.com/go/fms_tools
    The other issue may be that you need to put mp4: in front of the file name and .f4v at the end, which is not required for FLV files.

  • Slow stream start times/ or server not found with FMIS upgrade

    I recently upgraded from FMS 2 - FMIS 3.5.  Over our internal network videos stream like a dream!  However, accessing them from outside our own network means that they take about 20 seconds to load, or sometimes just get a message saying the server isn't found.
    This wasn't a problem with the FMS2 and there have been no changes to firewall settings or anything like that since the old server was up and running without problems.  I have the new server set to use exaclty the same ports, but wonder if there are some other settings which could be causing this?
    Networking isn't really my area of expertise, and I have no idea where to start looking to improve things.  Can anyone offer some suggestions as to why this would be happening?  Would appreciate any help.  Thanks

    That 20 second period makes me suspect and issue with port bindings. It's typical for the Flashplayer to take about 20 seconds for the attempt on port 1935 to time out and try port 80.
    In your fms.ini, what do you have the adaptor.hostport set to? Also, is there anything else running on the server that might occupy port 80... perhaps an HTTP server? If so, what's the environment? IIS, apache, windows, Linux, etc?
    Also, in your event logs, do you see any errors from FMS suggesting that it can't attach to a specific port? In windows, this will show up in your event viewer... not sure about Linux.
    You might try connecting to the server with a port defined in the url...
    rtmp://mydomain.com:1935/application/instance
    and
    rtmp://mydomain.com:80/application/instance
    If you find that either fail consistently, it would suggest that either a port is occupied by another application, or FMS isn't binding to all of the configured ports or IP addresses for some reason.

  • FMS 4.5 crashes on Centos  5.5 or above

    Hi,
    After upgrading to FMS 4.5.4 from FMS 4.0, we ran into this weird problem. FMScore started consuming 85 to 95 % of physical RAM. The drawback of it is after 3 to 4 days FMS crash down itself. Below are the  logs for the same. We are doing live streaming (kind of live video chat). There are almost 400 users and max 10 to 12 simultaneous video conf  during the busy hours.
    Core Hw/Sw Configuration:-
    Processor :- Interl Xeon E5620 2.40 Ghz
    Ram         :- 16GB
    OS           :- Centos 5.5
    Note:- We never faced this kind of issue with FMS 4.0
    Thanks,
    core.00.log
    #Date: 2012-11-14
    #Fields: date time x-pid x-status x-ctx x-comment
    2012-11-14 14:01:33 21477 (i)2581237 Starting admin app on core (21477). -
    2012-11-14 14:01:33 21477 (i)2581238 Core (21477) connecting to admin. -
    2012-11-14 14:01:33 21477 (i)2581231 Core (21477) connected to admin. -
    2012-11-14 14:01:33 21477 (i)2581234 Core (21477) connection to admin accepted. -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 127.0.0.1:19351 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 10.xxx.120.xxx:19351 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 10.xxx.120.xxx:19351 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 127.0.0.1:40001 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 10.xxx.120.xxx:40001 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 10.xxx.120.xxx:40001 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 127.0.0.1:40201 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 10.xxx.120.xxx:40201 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631174 Listener started ( _defaultRoot_ ) : 10.xxx.120.xxx:40201 (rtmfp-core)/v4 -
    2012-11-14 14:01:34 21477 (i)2631509 Public rtmfp-core addresses for listener _defaultRoot_ are: 127.0.0.1:19351;10.xxx.120.xxx:19351;10.xxx.120.xxx:19351;10.xxx.120.xxx:40001;
    2012-11-14 14:01:34 21477 (i)2581246 Core (21477) sending register cmd to edge. -
    2012-11-14 14:01:37 21477 (w)2581171 System memory load (99) is high. -
    2012-11-14 14:09:37 10632 (i)2581172 System memory load (1) is now below the maximum threshold. -
    2012-11-14 14:09:38 21477 (i)2581172 System memory load (1) is now below the maximum threshold. -
    #Date: 2012-11-14
    #Fields: date time x-pid x-status x-ctx x-comment
    2012-11-14 14:09:37 9534 (i)2581172 System memory load (1) is now below the maximum threshold. -
    #Date: 2012-11-14
    #Fields: date time x-pid x-status x-ctx x-comment
    2012-11-14 14:09:40 22301 (i)2581237 Starting admin app on core (22301). -
    2012-11-14 14:09:40 22301 (i)2581238 Core (22301) connecting to admin. -
    2012-11-14 14:09:40 22301 (i)2581231 Core (22301) connected to admin. -
    2012-11-14 14:09:40 22301 (i)2581234 Core (22301) connection to admin accepted. -
    master.00.log
    #Version: 1.0
    #Start-Date: 2012-11-14 14:01:30
    #Software: Adobe Flash Media Server 4.5.4 r3003 x64
    #Date: 2012-11-14
    #Fields: date time x-pid x-status x-ctx x-comment
    2012-11-14 14:01:27 9508 (i)2581223 Core (10170) is no longer active. -
    2012-11-14 14:01:30 9508 (w)2581256 Core (10170) _defaultRoot_:_defaultVHost_:::_0 experienced 1 failure[s]! -
    2012-11-14 14:01:31 9508 (i)2581221 Core (21477) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_0" -console  -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:::_0". -
    2012-11-14 14:09:37 9508 (i)2581172 System memory load (1) is now below the maximum threshold. -
    2012-11-14 14:09:37 9508 (i)2581223 Core (10631) is no longer active. -
    2012-11-14 14:09:37 9508 (w)2581256 Core (10631) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure[s]! -
    2012-11-14 14:09:37 9508 (i)2581221 Core (22301) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -console  -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

    Hi Vijay,
    Thanks for the reply. For now all of my core.xx.log files are filled with this error. I was searching for the below error and found it is already in discussion.
    plz check this.
    Below are my recent core.xx.log logs.
    #Fields: date   time    x-pid   x-status        x-ctx   x-comment
    2012-11-24      02:09:02        6403    (w)2611173      TSorensonVideoSmartQueue would have dropped H264 sequence header    
    2012-11-24      02:09:02        6403    (w)2611173      TSorensonVideoSmartQueue would have dropped H264 sequence header    
    2012-11-24      02:09:02        6403    (w)2611173      TSorensonVideoSmartQueue would have dropped H264 sequence header
    2012-11-24      02:09:02        6403    (w)2611173      TSorensonVideoSmartQueue would have dropped H264 sequence header    
    2012-11-24      02:09:02        6403    (w)2611173      TSorensonVideoSmartQueue would have dropped H264 sequence header    
    2012-11-24      17:36:03        6402    (w)2611173      TSorensonVideoSmartQueue would have dropped H264 sequence header     
    2012-11-24      17:42:29        6403    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696
    2012-11-24      17:48:41        6402    (e)2631109      Unknown exception caught in Operation not permitted.
    2012-11-24      17:48:41        6402    (e)2581279      Assert failed in tincan/server/rtmfp/eventloopbase.cpp line 492
    2012-11-24      18:50:30        6402    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696
    2012-11-24      20:24:46        6402    (e)2631109      Unknown exception caught in Operation not permitted.   
    2012-11-24      20:24:46        6402    (e)2581279      Assert failed in tincan/server/rtmfp/eventloopbase.cpp line 492
    2012-11-24      20:40:06        6402    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696    
    2012-11-24      20:40:06        6402    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696    
    2012-11-24      20:40:06        6402    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696    
    2012-11-24      20:40:30        6402    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696    
    2012-11-24      20:40:47        6402    (e)2631109      Unknown exception caught in Operation not permitted.   
    2012-11-24      20:40:47        6402    (e)2581279      Assert failed in tincan/server/rtmfp/eventloopbase.cpp line 492
    2012-11-24      21:02:15        6402    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696    
    2012-11-24      22:13:24        6402    (e)2581279      Assert failed in tincan/server/rtmfp/rtmfpcoresession.cpp line 1696    
    2012-11-24      22:36:50        6402    (e)2631109      Unknown exception caught in Operation not permitted.   
    2012-11-24      22:36:50        6402    (e)2581279      Assert failed in tincan/server/rtmfp/eventloopbase.cpp line 492
    #End-Date: 2012-11-25 00:58:55

  • Apache or Windows server for HTTP streaming

    Does is matter what HTTP server I use?
    In the process of upgrading from FMS 3.0 on Windows using IIS 5 to FMS 4.0. Will dynamic HTTP Streaming work from a Windows server?

    Hi,
    Thanks for your interest in HDS.
    HTTP Dynamic Streaming only works with Apache web server. The basic Apache web server is already bundled along with FMS from the 4.0 versions where the HTTP Dynamic streaming modules are loaded by default. Alternatively, any external apache installation also can be used, by copying the required module files and changing the configuration apache files to enable them..

  • Feature Requests for My Posts

    I would like to see a check box at the top of My Posts to filter the list to show just updated topics (those with (half) blue dots).
    Ideally, as with others, I would also like to see the return of "There are 3 replies and 5 new posts".

    Hello :)
    I have reading the FAQ of FMS3 ;) But for me it's important
    to speak
    with the dev FMS team because the actually FMS have some
    problems... and
    if the next version of FMS is AS3 compatible with E4X, etc...
    i think
    it's important to change the JS core engine with a JS 1.7
    version for
    example... in Flash CS3 the JSFL core engine is based on the
    JS 1.6 :
    http://robertpenner.com/flashblog/2007/08/jsfl-updated-to-javascript-16-gains-e4x.html
    Adobe can upgrade this FMS JS core engine now :)
    For me.. the more important is the upgrade of the
    application.registerClass method, etc...
    Note : You say "The major difference came from the "3" in the
    product
    name...."
    But in the next version you can read in the FAQ :
    Flash Media Server 3 will also introduce support for AMF3,
    allowing you
    to send bitmap data objects from one client to another.
    This difference is important isn't it ?
    EKA+ :)
    anonymous thing a écrit :
    > sorry to disappoint you but FMS 3 seems to be very, very
    similar to the FMS
    > capabilities. The major difference came from the "3" in
    the product name....
    >
    >
    http://www.adobe.com/aboutadobe/pressroom/pressmaterials/fms3/faq/
    >
    > In hope that final version will be better than the paper
    version!
    >

  • Instances crashing immediately in 3.5

    Just upgraded our FMS from 3.0 dev edition to licensed 3.5
    Interactive server. We have a few custom applications which were
    working fine running on the 3.0 server. On the licensed 3.5 server
    we are able to connect with the admin console, but if we attempt to
    connect to the application from a client side app, we get no
    response. If we try and start an application instance with the
    admin console, it shows up for a moment, but soon disappears and no
    output is sent from trace commands, and no errors messages are
    shown, and the log is empty.
    Any help solving this problem would be greatly appreciated.

    The master.01.log (from yesterday) is 6.19 mb and features
    these lines repeating for the entire day every 5 seconds:
    009-01-15 00:00:33 5573 (i)2581221 Core (22909) started,
    arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app
    "registry" -inst "registry" -tag -conf
    "/opt/adobe/fms/conf/Server.xml" -name
    "_defaultRoot_:_defaultVHost_:registry:registry:". -
    2009-01-15 00:00:38 5573 (i)2581223 Core (22909) is no longer
    active. -
    2009-01-15 00:00:38 5573 (i)2581221 Core (22930) started,
    arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app
    "registry" -inst "registry" -tag -conf
    "/opt/adobe/fms/conf/Server.xml" -name
    "_defaultRoot_:_defaultVHost_:registry:registry:". -
    2009-01-15 00:00:43 5573 (i)2581223 Core (22930) is no longer
    active. -
    2009-01-15 00:00:43 5573 (i)2581221 Core (22951) started,
    arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app
    "registry" -inst "registry" -tag -conf
    "/opt/adobe/fms/conf/Server.xml" -name
    "_defaultRoot_:_defaultVHost_:registry:registry:". -
    thoughts?
    thanks,
    J

  • ERROR "Application (vod) is not defined." when creating new vhosts

    I'm testing FMS 4.5 using the developer edition before upgrading our FMS 3.5 servers to 4.5 but for some reason creating new vhosts doesn't seem to work.
    I'm following the exact same steps I would take using v3.5 but 4.5 gives this error:
    Sep 29 03:34:24 eventstreaming Javascript[31564]: Connection rejected by server. Reason : [ Server.Reject ] : (_defaultRoot_, vhost1.somedomain.com) : Application (vod) is not defined.
    Here are the steps I've taken:
    Made a copy of folder   _defaultVHost_/   named   vhost1.somedomain.com/     ( inside conf/_defaultRoot_ )
    Made an exact copy of the default FMS4.5 applications/  folder  at  /home/vhost1/public_html/applications
    Edited  vhost1.somedomain.com/vhost.xml and changed
    <AppsDir>${VHOST.APPSDIR}</AppsDir>
    TO
    <AppsDir>/home/vhost1/public_html/applications</AppsDir>
    Edited /home/vhost1/public_html/applications/vod/Application.xml and changed the path to the media files. i.e.
    <Streams>/;${VOD_COMMON_DIR}</Streams>
    <Streams>/;${VOD_DIR}</Streams>
    TO
    <Streams>/;${VOD_COMMON_DIR}</Streams>
    <Streams>/;/home/vhost1/public_html/applications/vod/media</Streams>
    Restarted FMS
    The VOD application in the default FMS applications folder works fine but the one for the new vhost doesn't. When I try to connect to rtmp://vhost1.somedomain.com/vod/media/sample.flv I get the error
    Sep 29 03:34:24 eventstreaming Javascript[31564]: Connection rejected by server. Reason : [ Server.Reject ] : (_defaultRoot_, vhost1.somedomain.com) : Application (vod) is not defined.
    No other errors are reported in the logs when I strart FMS. Why is the VOD application not working for new vhosts? Either I'm missing something obvious or the developer edition is restricted to one vhost perhaps?

    I tried same scenario at my end and its working for me. Probably there is something wrong which you are doing. For developer edition you should be able to have 3 vhosts.
    Why are you using URI like this: rtmp://vhost1.somedomain.com/vod/media/sample.flv --> it should be rtmp://vhost1.somedomain.com/vod/sample.flv

  • HTML 5 and the use of the HTTP protocol.

    In our company we upgraded to fms 4 and installed the apache that comes bundle up with the installation. We had it configure and now we can play videos in html 5 by using the http protocol. The question I have is, can we use https protocol instead of rtmps? I've been doing a lot of research and I found documentation that says to put a minus sign in front of port 443 (-443) in the fms.ini file in the ADAPTOR.HOSTPORT line but it also says that with this configuration port 443 will only recieve rtmps connections. My next step is to put the minus sign in front of the port number and restart the server and just try to establish connection using https to see if i works. Any ideas are definetly welcome.

    Hi,
    It is possible to serve the content via the Apache that bundles with the FMS.
    For that you need to eneble mos_ssl.so module in httpd.conf and create a virtual host and give appropriate parameters ( refer any document for ssl configuration in apache ). Also make sure that the 443 port is not used by any other service (eg : RTMPS ).
    Thanks.

Maybe you are looking for

  • Aperture 3 and Nik Software tip

    One of Aperture 3's main new features is support for 64-bit processing under Snow Leopard. Like many other posters, I have seen a definite speed improvement in 64-bit mode (the default). My Nik plugins transferred automatically when installing Apertu

  • BiB Tutorial - WindowUtils not found

    Hi, I am using BiBeans v2.5/JDev 9.0.2 and RDBMS 9.0.1.3.0; I stuck at the excercise no.3 of Developing a Java Client Application/Customizing Bi Objects of the BiBtutorial; while adding an Action Listener for the graph title customizer and compiling

  • How to automatically delete archivelogs on standby using RMAN?

    Hello team. I just setup a physical standby on windows environment. The primary database is been backed up via RMAN and everything works fine except that the archivelogs moved to standby site are not been deleted. I couldn't find some rman option to

  • Crystal off Query Builder

    can you create a crystal report off this query builder statment? SELECT SI_ID, SI_NAME, SI_Webi, SI_OWNER FROM CI_INFOOBJECTS, CI_SYSTEMOBJECTS, CI_APPOBJECTS Where PARENTS("SI_NAME='CrystalReport-BusinessView'","SI_NAME ='Xtreme Business View'")

  • Where can I see SAP Message numbers for Errors.

    Dear all, Where can I Message No's in SAP. for Some error messages, when I click F1 help, system is showing nothing but one message numbers. Could you tell me whre can I see all these messages. Your advice will be highly rewarded. Thank you, Raghu ra