Available in English Only

We apologize for the inconvenience, but this document is only available in English. The English version is shown below.

Error starting server: Application /path/to/sc_serv does not exist

Question:

When attempting to start my streaming server or source, I get the following error:

Error starting server: Application /path/to/sc_serv does not exist

How do I fix this?

Answer:

This error indicates that the pathname for the streaming server/source that you specified during installation is no longer valid and/or accessible. Please check the following, in order:

  1. Does the specified pathname exist? If not, this is the problem, and you'll need to put the relevant program (i.e., your streaming server or source application) in the specified directory.

  2. Is the specified pathname an application (rather than a directory)? A common mistake is to specify only the PATH to the application, without the filename. The pathname MUST include the filename of the streaming server/source application (i.e., /home/shoutcast/sc_serv instead of just /home/shoutcast/).

  3. Are the permissions on the specified program set such that it's readable and executable by the centovacast account? The permissions should be 0755 (rwxr-xr-x). You can change this by running:

    chmod 0755 /path/to/sc_serv
    

    (where /path/to/sc_serv is the pathname indicated in the error message)

  4. Are the permissions on the parent directories set such that they're readable and executable by the centovacast account? For example, if the pathname is /home/jsmith/sc_serv, the /home/ and /home/jsmith/ directories must be readable and executable by the centovacast account, otherwise the program will appear not to exist. You can change this by running:

    chmod 0755 /home/jsmith
    

    (where /home/jsmith is the path -- without filename -- indicated in the error message) You may need to repeat this for each parent directory (e.g., chmod 0755 /home, then chmod 0755 /home/jsmith, etc.)

If the problem still persists, please ask your systems administrator to try logging in to a root shell (e.g., login as root via SSH) and then run:

su - centovacast -s /bin/bash

This will execute a shell under the centovacast user account, allowing your administrator to browse the filesystem as Centova Cast sees it. From here, your administrator should try to access the directory noted in the error message and verify that the server or source application is accessible and executable. When your administrator has determined the problem, he should type exit to return to the root shell, then make any permissions and/or ownership changes that may be needed.