Skip to main content
Participating Frequently
September 25, 2008
Question

Cannot Connect to Server

  • September 25, 2008
  • 2 replies
  • 953 views
Hi Everyone,

I have FMS3 installed on a Linux machine running Red Hat 4. I am able to connect to the admin console and it shows me that the server is running and everything looks fine. But when I try to stream video, it just wont establish a connection. I tried using fmscheck to see if I can connect. When I type:

./fmscheck --host localhost --app vod --logfile output.txt

I get this:

#Version 1.0.0 r15
#2008-09-25 12:47:05
#Software: Adobe Flash Media Server Check 1.0.0 r15
#2008-09-25
#Fields: date time x-event x-sname
2008-09-25 12:47:05 Connect rtmp://localhost:1935/vod
2008-09-25 12:47:21 Timeout -

The admin console shows that no connection has been made and there's nothing displayed in the server log (viewed in the admin console). Also, when I restart the server and check the logs, it appears that the creation of the process mutex has failed:

Sep 25 12:49:14 serverName Service[5369]: Server stopped .
Sep 25 12:49:14 serverName Service[23886]: Server starting...
Sep 25 12:49:14 serverName Service[23886]: Server started (/var/opt/adobe/fms/conf/Server.xml).
Sep 25 12:49:14 serverName Adaptor[23906]: Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4
Sep 25 12:49:14 serverName Server[23909]: Failed to create process mutex.
Sep 25 12:49:15 serverName Adaptor[23906]: Listener started ( _defaultRoot__edge1 ) : 1935/v4
Sep 25 12:49:19 serverName Service[24014]: Server starting...
Sep 25 12:49:19 serverName Adaptor[24014]: Listener started ( FCSAdminIpcProtocol ) : localhost:11110/v4
Sep 25 12:49:20 serverName Adaptor[24014]: Listener started ( FCSAdminAdaptor ) : 1111/v4
Sep 25 12:49:21 serverName Service[24014]: Server started (./conf/Server.xml)

Has anyone encountered this before or have any suggestions on what to try? I all out of ideas. The only thing I can think of now is to uninstall and re-install.

Any help is appreciated.

Thanks,
Ryan


    This topic has been closed for replies.

    2 replies

    Participant
    February 5, 2009
    You usually get the "Failed to create process mutex" error message in /var/log/syslog if the FMS user (the one specified in fms.ini with the SERVER.PROCESS_UID and SERVER.PROCESS_GID parameters) has no write permission to the ${FMS_DIR}/tmp directory (where FMS_DIR is the directory where you installed FMS in - usually /opt/adobe/fms). Don't forget to check the whole path leading to that "tmp" directory!
    If the user has no permission to enter eg. /opt/adobe, then it will not be able to reach the /opt/adobe/fms/tmp directory either.

    To check the permissions on your setup, run the following command sequence as root (replace ${FMS_USER} with the name of the OS user that FMS is running with and ${FMS_TMP_DIR} with the path of the "tmp" subdir in your FMS directory):

    su - ${FMS_USER} -s /bin/bash
    for path_element in $(echo "${FMS_TMP_DIR}" | tr '/' ' '); do fms_path=${fms_path}/${path_element}; if [ ! -x "${fms_path}" ]; then echo "Error: execute permission is needed on directory ${fms_path}"; fi; done

    This sets the current user to ${FMS_USER} and checks each directory in the path of ${FMS_TMP_DIR} for accessibility by that user. Repeat running the script each time you fix a permission error. Keep repeating until you can run the script without any error messages.

    You can mimic the script's behaviour manually with something like this (assuming the user is "fms" and the directory is "/opt/adobe/fms/tmp"):

    su - fms -s /bin/bash
    cd /opt
    cd /opt/adobe
    cd /opt/adobe/fms
    cd /opt/adobe/fms/tmp

    If any of the "cd" commands gives a "permission denied", then fix it by adding the required permissions. Usually you would set something like this:
    chown root.root /opt /opt/adobe
    chmod u=rwx,go=rx /opt /opt/adobe
    chown -R fms.fms /opt/adobe/fms
    chmod -R u+rwX,go+rX /opt/adobe/fms

    And of course to create a file in that "tmp" dir, the FMS user has to have write permissions to the "tmp" dir too.
    Participating Frequently
    September 25, 2008
    hey everyone,

    I just finished reinstalling and everything is working now. One thing I did differently this time was -- I left the default installation directory the same (opt/adobe/fms). I cant say this is the solution - it really shouldnt be - but its working now.

    Thanks,
    Ryan

    September 25, 2008
    You also get the MUTEX error when the user running the FMS Server account is different to the one running the FMS Admin account, they need to be the same, at least on Windows.
    Participating Frequently
    September 26, 2008
    yeah I read about that too. maybe that was it.. I actually didnt do the first install.