I'm usually using start_stop_daemon to start stop jobs, but

I would recommend to
1) check process details after service is started
2) add HOME=$RED5_HOME to the script (sometimes scripts are not working in
case HOME is not set)


Cosmetics:
start_red5="$RED5_HOME/red5.sh start"
should be
start_red5=$RED5_HOME/red5.sh

and
stop_red5="$RED5_HOME/red5-shutdown.sh stop"
should be
stop_red5=$RED5_HOME/red5-shutdown.sh

On Mon, Sep 7, 2015 at 3:46 AM, Milan Pesic <[email protected]> wrote:

> I checked the file/folder ownerships, both /etc/init.d/red5 file and OM
> folder is owned by root user. I applied chmod 777 to both, just in case. I
> changed ownership of /opt/red5303 folder to root and applied chmod 777 as
> well and still got the same problem.
>
> Here is the script I use (i tried several different ones and ended with
> the same problem):
>
> #
>
> #!/bin/sh -e
>
> #
>
> # chkconfig: 2345 20 80
>
> # description: Startup script for Red5/openmeetings
>
>
>
> export RED5_HOME=/opt/red5303
>
> start_red5="$RED5_HOME/red5.sh start"
>
> stop_red5="$RED5_HOME/red5-shutdown.sh stop"
>
>
>
> start() {
>
>             echo -n "Starting Red5: "
>
>         ${start_red5} &
>
>         echo "done."
>
> }
>
> stop() {
>
>         echo -n "Shutting down Red5: "
>
>         ${stop_red5}
>
>         echo "done."
>
> }
>
>
>
> case "$1" in
>
>   start)
>
>         start
>
>             ;;
>
>   stop)
>
>             stop
>
>             ;;
>
>   restart)
>
>             stop
>
>             sleep 10
>
>         start
>
>             ;;
>
>   *)
>
>             echo "Usage: $0 {start|stop|restart}"
>
> esac
>
>
>
> exit 0
>
> case "$1" in
>
>   start)
>
>         start
>
>             ;;
>
>   stop)
>
>             stop
>
>             ;;
>
>   restart)
>
>             stop
>
>             sleep 10
>
>         start
>
>             ;;
>
>   *)
>
>             echo "Usage: $0 {start|stop|restart}"
>
> esac
>
>
>
> exit 0
>
>
>
> On Sun, Sep 6, 2015 at 5:29 PM, Maxim Solodovnik <[email protected]>
> wrote:
>
>> I'm not sure what script are you using.
>> I saw issues like this, it was caused by user being used by autostart
>> script. Are you explicitly setting the user inside /etc/init.d/red5?
>>
>> According misconfigure, it seems I read you problem not very accurate.
>>
>> I would investigate permissions.
>>
>>
>> On Sun, Sep 6, 2015 at 9:24 PM, Milan Pesic <[email protected]> wrote:
>>
>>> I am using CentOS 7, and the user used for autostart is root. Users
>>> without root privilege can access OM folder and files.
>>>
>>> Misconfigured how? Everything is working well when i run the script with
>>> #/etc/init.d/red5 start command,
>>> but if I use #service red5 start, the same problem occurs like when I
>>> autostart the script. Is there a difference between these two commands?
>>>
>>> Thank you for your answers,
>>> Milan
>>>
>>> On Sun, Sep 6, 2015 at 6:38 AM, Maxim Solodovnik <[email protected]>
>>> wrote:
>>>
>>>> What OS are you using?
>>>> What user is being used to start OM in autostart script?
>>>> What are file/folder permissions/owner of OM?
>>>>
>>>> According doc/ppt: you have jodconverter and/or OpenOffice
>>>> misconfigured, you need to check those
>>>>
>>>> On Sun, Sep 6, 2015 at 8:47 AM, Milan Pesic <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi, I have a problem making red5 script auto start properly.
>>>>>
>>>>> When I make the script start through rc.local it starts with the
>>>>> system boot and everything is working except uploading ppt, doc and 
>>>>> similar
>>>>> files (jpeg and pdf is working).  Same problem if I make the script start
>>>>> with system boot via Webmin.
>>>>>
>>>>> When I start the script manually through terminal, everything is
>>>>> working like it should.
>>>>>
>>>>> I hope somebody can help.
>>>>>
>>>>> Regards,
>>>>> Milan
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>


-- 
WBR
Maxim aka solomax

Reply via email to