Skip to main content
O
ozgolith
Participant
June 10, 2008
Question

FMS3 dies on start (linux)

  • June 10, 2008
  • 2 replies
  • 1413 views
FMS dies immediately after starting the services. Checking top shows that fmsmaster stays running but fmscore, fmsadmin, fmsedge all die a couple of seconds after they appear and there is no real error logging.

I'm running Ubuntu Linux 7.04 and installing FMS 3.0.1r123 in development mode.
Using Ubuntu patch from http://www.bluetwanger.de/blog/2008/02/11/flash-media-server-3-on-ubuntu-710-gutsy/

Thanks to this post http://www.ecinteractive.co.uk/blog/?p=25 and it's comments I used ldd on the various packages to show all the dependencies are satisfied. I found I had the same issue mentioned there where libasneu.so.1 was not loading so I followed the comment and the dependency error went away. I've also read the http://www.adobe.com/go/c533ee36 support topic and that isn't the issue.

I'm no guru so here is all the info I've been able to gather. -

Starting FMS in console mode:

# ./fmsmaster -console

Adobe Flash Media Server (Master)Console mode.
Host: host.net IPv4: 209.135.140.223
Server starting...
Failed to create process condition: errno(28).


Staring the FMS server normally gives:

# ./fmsmgr server fms start
Server:fms command:start
./server: line 19: ulimit: open files: cannot modify limit: Operation not permitted
error: "Operation not permitted" setting key "kernel.sem"
NPTL 2.5
Starting Adobe Flash Media Server (please check /var/log/messages)


Likewise shutting down the FMS server normally gives:

# ./fmsmgr server fms stop
Server:fms command:stop
./server: line 19: ulimit: open files: cannot modify limit: Operation not permitted
error: "Operation not permitted" setting key "kernel.sem"
NPTL 2.5
Stopping Adobe Flash Media Server (please check /var/log/messages)
Server has shutdown...


Logs:

/var/log/messages has only the following:

Jun 10 14:59:14 mcdev Service[12882]: Server starting...
Jun 10 14:59:14 mcdev Service[12882]: Server started (/opt/adobe/fms/conf/Server.xml).


In /opt/adobe/fms/logs

#Date: 2008-06-10
#Fields: date time x-pid x-status x-ctx x-comment
2008-06-10 14:59:14 12882 (i)2581173 Host: host.net IPv4: 209.135.140.223 -
2008-06-10 14:59:14 12882 (i)2571011 Server starting... -
2008-06-10 14:59:14 12882 (i)2581224 Edge (12902) started, arguments : -edgeports ":1935" -coreports "localhost:19350" -conf "/opt/adobe/fms/conf/Server.xml" -adaptor "_defaultRoot_" -name "_defaultRoot__edge1". -
2008-06-10 14:59:14 12882 (i)2581221 Core (12905) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app "registry" -inst "registry" -tag -console -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:registry:registry:". -
2008-06-10 14:59:14 12882 (i)2571111 Server started (/opt/adobe/fms/conf/Server.xml) -
2008-06-10 14:59:19 12882 (i)2581226 Edge (12902) is no longer active. -
2008-06-10 14:59:19 12882 (i)2581223 Core (12905) is no longer active. -


Any help would be much appreciated.
    This topic has been closed for replies.

    2 replies

    A
    Anonymous
    October 31, 2008
    Hi guys,

    I stumbled to this topic as I have found the same issue and Im running it from Ubuntu 8.04
    I am starting the server as root and everytime I try to launch it with ./fmsmgr server fms start I get the ulimit messages. I then went to check my ulimits and all ulimit -f or ulimit -v are responding with unlimited.
    Any help?

    Cheers
    O
    ozgolithAuthor
    Participant
    October 31, 2008
    @rootalien

    Are you on your own server or is this a VPS or other hotsted account? That turned out to be my issue. Even with and unlimited ulimit the VPS I was developing on had a limit on server processes.

    quote:
    Originally posted by: rootalien
    Hi guys,

    I stumbled to this topic as I have found the same issue and Im running it from Ubuntu 8.04
    I am starting the server as root and everytime I try to launch it with ./fmsmgr server fms start I get the ulimit messages. I then went to check my ulimits and all ulimit -f or ulimit -v are responding with unlimited.
    Any help?

    Cheers


    A
    Anonymous
    June 12, 2008
    Hrms... It does look like you are starting it from root, is that correct? If not, you have to be root to start it. I do know that the /opt/adobe/fms/server script sets some sysctl and ulimit requirements prior to starting FMS. I'm not sure if Ubuntu supports ulimit or sysctl, but you should at least add those settings in some how.

    ulimit -n 64536
    ulimit -s 1024
    ulimit -u 32768
    /sbin/sysctl -q -w kernel.sem="250 32000 32 1024"

    There are a few other things the server script does such as initalizing shared memory. You do not need to run "./fmsmaster -console" as fmsmgr starts that for you. I honestly have found it always better to execute from fmsmgr (as you did do) rather than to use the init script Adobe provides in /etc/init.d.

    Does Ubuntu have the strace package/rpm available? I often use that to debug program errors. It shows the entire background start up for a process. If you have it, run it with strace fmscore;strace fmsmaster... etc.

    I really think the problem in your case is the ulimit/sysctl required settings just aren't being met.

    g'luck,
    O
    ozgolithAuthor
    Participant
    June 12, 2008
    Thanks for the reply. I finally got some answers from tech support about the clients server last night only to find the server just couldn't support enough processes due to hosting limitations. It was nerve wracking but I learned a few things along the way. I started fmsmgr in console mode just to get the startup output which was a little help during a couple of setup checks.

    I will note here in case someone else stumbles across my post looking for similar answers that FMS2 and FMS3 will run on Ubuntu using the patches I mention above as well as Debian and some other derivatives. Library dependencies are the main problem so using the ldd command against each script was a huge help in narrowing those down ie:
    #ldd fmsadmin
    #ldd fmscore
    #ldd fmsmaster
    etc.

    Now I've switched over to my own dev environment using Redhat and have issues making a connection from the admin page, I may be making another post soon ;-)

    Thanks again for responding.

    quote:
    Originally posted by: anthryan
    Hrms... It does look like you are starting it from root, is that correct? If not, you have to be root to start it. I do know that the /opt/adobe/fms/server script sets some sysctl and ulimit requirements prior to starting FMS. I'm not sure if Ubuntu supports ulimit or sysctl, but you should at least add those settings in some how.

    ulimit -n 64536
    ulimit -s 1024
    ulimit -u 32768
    /sbin/sysctl -q -w kernel.sem="250 32000 32 1024"

    There are a few other things the server script does such as initalizing shared memory. You do not need to run "./fmsmaster -console" as fmsmgr starts that for you. I honestly have found it always better to execute from fmsmgr (as you did do) rather than to use the init script Adobe provides in /etc/init.d.

    Does Ubuntu have the strace package/rpm available? I often use that to debug program errors. It shows the entire background start up for a process. If you have it, run it with strace fmscore;strace fmsmaster... etc.

    I really think the problem in your case is the ulimit/sysctl required settings just aren't being met.

    g'luck,


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