Jean-Marie,
If you noticed, even though you ran "/etc/init.d/red5 stop", for some reason red5 was still running (as shown by "tcp6 0 0 :::5080 :::* LISTEN 30842/java"). This could be part of your current problem. I believe you need to find some way to stop the current red5 from running so you can then start and stop it by your new (i.e. the current) red5 script (which I think came from red5.debian). I would suggest rebooting the server and then running "netstat -anp | grep java" to ensure that it does not report any 5080 LISTEN. Instead of rebooting, I believe (but it has been awhile so I am not certain), that you can kill the process by going "kill 30842" but before doing so you can verify if java is process 30842 by entering "ps aux | grep java" which lists all the currently running processes, and pipes the output through grep, asking grep to only return lines containing the word "java". Please forgive me if you already know this, but it is easier to give more information than needed. I believe that once you have stopped openmeetings, you should be able to start and stop openmeetings via the red5 script. I am working on the assumption that there are no other systems on your server that are using red5 ? By the way, what is the time zone in your area, and how much longer will you be available to test with ? In about an hour I could give you more time to try to sort this out. Thanks, George Kirkham From: Jean-Marie Landri [mailto:[email protected]] Sent: Thursday, 6 September 2012 4:54 PM To: [email protected] Subject: Re: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java hello George root@vps-1105323-11088:/etc/init.d# netstat -anp | grep java tcp 0 0 0.0.0.0:8787 0.0.0.0:* LISTEN 30842/java tcp6 0 0 :::48608 :::* LISTEN 30842/java tcp6 0 0 :::1935 :::* LISTEN 30842/java tcp6 0 0 :::9999 :::* LISTEN 30842/java tcp6 0 0 :::8088 :::* LISTEN 30842/java tcp6 0 0 :::5080 :::* LISTEN 30842/java tcp6 442 0 216.224.171.20:5080 94.159.213.24:51694 ESTABLISHED 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:50456 CLOSE_WAIT 30842/java tcp6 11 0 216.224.171.20:8088 96.254.171.2:47376 CLOSE_WAIT 30842/java tcp6 2 0 216.224.171.20:8088 96.254.171.2:37223 CLOSE_WAIT 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:54905 CLOSE_WAIT 30842/java tcp6 0 0 216.224.171.20:5080 94.159.213.24:51689 ESTABLISHED 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:39332 CLOSE_WAIT 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:43465 CLOSE_WAIT 30842/java root@vps-1105323-11088:/etc/init.d# root@vps-1105323-11088:/etc/init.d# netstat -anp | grep java tcp 0 0 0.0.0.0:8787 0.0.0.0:* LISTEN 30842/java tcp6 0 0 :::48608 :::* LISTEN 30842/java tcp6 0 0 :::1935 :::* LISTEN 30842/java tcp6 0 0 :::9999 :::* LISTEN 30842/java tcp6 0 0 :::8088 :::* LISTEN 30842/java tcp6 0 0 :::5080 :::* LISTEN 30842/java tcp6 442 0 216.224.171.20:5080 94.159.213.24:51694 ESTABLISHED 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:50456 CLOSE_WAIT 30842/java tcp6 11 0 216.224.171.20:8088 96.254.171.2:47376 CLOSE_WAIT 30842/java tcp6 2 0 216.224.171.20:8088 96.254.171.2:37223 CLOSE_WAIT 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:54905 CLOSE_WAIT 30842/java tcp6 0 0 216.224.171.20:5080 94.159.213.24:51689 ESTABLISHED 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:39332 CLOSE_WAIT 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:43465 CLOSE_WAIT 30842/java root@vps-1105323-11088:/etc/init.d# root@vps-1105323-11088:/etc/init.d# /etc/init.d/red5 stop root@vps-1105323-11088:/etc/init.d# root@vps-1105323-11088:/etc/init.d# netstat -anp | grep java tcp 0 0 0.0.0.0:8787 0.0.0.0:* LISTEN 30842/java tcp6 0 0 :::48608 :::* LISTEN 30842/java tcp6 0 0 :::1935 :::* LISTEN 30842/java tcp6 0 0 :::9999 :::* LISTEN 30842/java tcp6 0 0 :::8088 :::* LISTEN 30842/java tcp6 0 0 :::5080 :::* LISTEN 30842/java tcp6 443 0 216.224.171.20:5080 94.159.213.24:51694 CLOSE_WAIT 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:50456 CLOSE_WAIT 30842/java tcp6 11 0 216.224.171.20:8088 96.254.171.2:47376 CLOSE_WAIT 30842/java tcp6 2 0 216.224.171.20:8088 96.254.171.2:37223 CLOSE_WAIT 30842/java tcp6 1 0 216.224.171.20:5080 94.159.213.24:51705 CLOSE_WAIT 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:54905 CLOSE_WAIT 30842/java tcp6 0 0 216.224.171.20:5080 94.159.213.24:51689 ESTABLISHED 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:39332 CLOSE_WAIT 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:43465 CLOSE_WAIT 30842/java root@vps-1105323-11088:/etc/init.d# /etc/init.d/red5 start root@vps-1105323-11088:/etc/init.d# root@vps-1105323-11088:/etc/init.d# netstat -anp | grep java tcp 0 0 0.0.0.0:8787 0.0.0.0:* LISTEN 30842/java tcp6 0 0 :::48608 :::* LISTEN 30842/java tcp6 0 0 :::1935 :::* LISTEN 30842/java tcp6 0 0 :::9999 :::* LISTEN 30842/java tcp6 0 0 :::8088 :::* LISTEN 30842/java tcp6 0 0 :::5080 :::* LISTEN 30842/java tcp6 443 0 216.224.171.20:5080 94.159.213.24:51694 CLOSE_WAIT 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:50456 CLOSE_WAIT 30842/java tcp6 11 0 216.224.171.20:8088 96.254.171.2:47376 CLOSE_WAIT 30842/java tcp6 2 0 216.224.171.20:8088 96.254.171.2:37223 CLOSE_WAIT 30842/java tcp6 1 0 216.224.171.20:5080 94.159.213.24:51705 CLOSE_WAIT 30842/java tcp6 4 0 216.224.171.20:8088 96.254.171.2:54905 CLOSE_WAIT 30842/java tcp6 0 0 216.224.171.20:5080 94.159.213.24:51689 ESTABLISHED 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:39332 CLOSE_WAIT 30842/java tcp6 459 0 216.224.171.20:8088 96.254.171.2:43465 CLOSE_WAIT 30842/java root@vps-1105323-11088:/etc/init.d# On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <[email protected]> wrote: Seth, Jean-Marie should not have to specific the path when running "red5" script from within the path where the script is located. This indicates that the script "red5" exists in the directory "/etc/init.d" and that the script is executable; root@vps-1105323-11088:~# ls -al /etc/init.d/red5 -rwxr-xr-x 1 root root 2169 Sep 5 17:21 /etc/init.d/red5 And therefore running the following command paces the terminal into the "/etc/init.d" directory; root@vps-1105323-11088:~# cd /etc/init.d The fact that the current directory is in fact "/etc/init.d" is indicated by "/etc/init.d" in the below command, and the current user is "root", which to me says that the command "red5" should be able to be executed, so why is "-bash: red5: command not found" reported. root@vps-1105323-11088:/etc/init.d# <mailto:root@vps-1105323-11088:/etc/init.d> red5 -bash: red5: command not found Jean-Marie, You could try Seth's suggestion of running "/etc/init.d/red5 start" but to get an idea of what is happening in the server I would suggest you run this sequence of commands, and then email us the output, if they are giving any error messages; ls -al /etc/init.d/red5 netstat -anp | grep java /etc/init.d/red5 stop netstat -anp | grep java /etc/init.d/red5 start netstat -anp | grep java Thanks, George Kirkham -----Original Message----- From: Seth Galitzer [mailto:[email protected]] Sent: Thursday, 6 September 2012 8:23 AM To: [email protected] Subject: Re: red5 start script not work for me vps-1105323-11088 On 09/05/2012 05:11 PM, George Kirkham wrote: > I do find this statement a bit of a concern "-bash: red5: command not > found" and wonder why or how this gets reported. > [SNIP] > > root@vps-1105323-11088:~# cd /etc/init.d > root@vps-1105323-11088:/etc/init.d# <mailto:root@vps-1105323-11088:/etc/init.d> red5 > -bash: red5: command not found > You must include the full path to run this command: # /etc/init.d/red5 start In most (maybe all?) linux/unix distros, the current directory is not in the search path. So when you did ~# cd /etc/init.d /etc/init.d# red5 the shell did not know where to find the command. By including the full path, you are telling the shell where to find it. Looking at the rest of your output, it does look like the service is running just fine and you should be able to access it using the proper URL as suggested by George Kirkham. Seth -- Seth Galitzer Systems Coordinator Computing and Information Sciences Kansas State University http://www.cis.ksu.edu/~sgsax <http://www.cis.ksu.edu/~sgsax> [email protected] <mailto:[email protected]> 785-532-7790
