Skip to main content
Participant
January 14, 2009
Question

Instances crashing immediately in 3.5

  • January 14, 2009
  • 4 replies
  • 1649 views
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.

    This topic has been closed for replies.

    4 replies

    Inspiring
    January 22, 2009
    Im having the same probem, except that the fms 3.5 worked well for a day.

    Someone found a solution?
    Participant
    January 22, 2009
    I discovered the source of the problem I was having. The owner of the fms install directory and its sub-directories were changed from the user that was chosen as the owner of fms. once i changed it back, everything worked. hope this helps.
    Participant
    January 15, 2009
    none of the application logs have been updated since the new server was installed. I don't think the app instances are alive long enough to log anything, if they are starting at all. Also, I tried starting an app with only one trace command onAppStart and nothing else, and no go.

    also, when I start the server, I get this in messages:

    Jan 15 11:51:07 www Service[22979]: Server starting...
    Jan 15 11:51:07 www Adaptor[23002]: Invalid configuration file : Adaptor.xml ( _defaultRoot_ )
    Jan 15 11:51:07 www Adaptor[22999]: Failed to create listener for adaptor _defaultRoot_, IP , port 80: .
    Jan 15 11:51:07 www Adaptor[22999]: Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4
    Jan 15 11:51:07 www Service[22979]: Server started (/opt/adobe/fms/conf/Server.xml).
    Jan 15 11:51:08 www Adaptor[22999]: Listener started ( _defaultRoot__edge1 ) : 1935/v4
    Jan 15 11:51:12 www Adaptor[23094]: Invalid configuration file : Adaptor.xml ( _defaultRoot_ )

    No changes have been made to the default Adaptor.xml afaik.
    Participating Frequently
    January 16, 2009
    I would make sure that something wasn't modified accidentally in your Adaptor.xml; check to make sure it is in a valid xml format; and that the new tag HttpProxy doesn't conflict with other server settings.
    January 15, 2009
    Hmm... that sounds like FMS choking on the SSAS code on app start and crashing the core.

    I would also take a look in the application logs (logs/[vhost name]/[application name] to see if there is anything about an actionscript error.
    January 15, 2009
    Just to confirm.. Is there no useful log entry in core00.log/master00.log and similar files?

    Are you able to run rtmp streams from FMS3.5 start screen i.e. Flash Media Server 3.5/webroot/index.html ?
    Participant
    January 15, 2009
    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