You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by George Kirkham <gk...@co2crc.com.au> on 2012/09/06 00:11:30 UTC
RE: red5 start script not work for me vps-1105323-11088
Jean-Marie,
>From the output of "netstat -anp | grep java" it seems that OpenMeetings is running for you now.
Specifically the following shows that Openmeetings is running (and would need to be stopped before trying to start it again);
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
This means that if on a PC you try to connect to your server using;
http://serveraddress:5080/openmeetings/install you should get at least some kind of web page being displayed.
Note that "serveraddress" is either the domain name of your server or the ip address of your server for example;
http://mydomainname.com:5080/openmeetings/install
or
http://58.45.123.11:5080/openmeetings/install
or
http://vps-1105323-11088:5080/openmeetings/install that is as long as your PC is on the same network as your server "vps-1105323-11088".
I do find this statement a bit of a concern "-bash: red5: command not found" and wonder why or how this gets reported.
If the above URLs do not work, can you please try this command and let me know the output;
ls -al /usr/lib/red5
If you following the instructions you should see something like the following;
# ls -al /usr/lib/red5
total 1160
drwxrwxr-x 8 nobody root 4096 Jun 27 15:48 .
drwxr-xr-x 201 root root 73728 Jun 27 10:32 ..
-rwxrwxr-x 1 nobody root 1090 Jun 26 09:38 admin.bat
-rwxrwxr-x 1 nobody root 1073 Jun 26 09:38 admin.sh
-rwxrwxr-x 1 nobody root 16671 Jun 26 09:38 boot.jar
-rwxrwxr-x 1 nobody root 41123 Jun 26 09:38 commons-cli-jar-1.2.jar
drwxrwxr-x 2 nobody root 4096 Jun 27 15:19 conf
drwxrwxr-x 2 nobody root 4096 Jun 27 10:33 lib
-rwxrwxr-x 1 nobody root 1284 Jun 26 09:38 license.txt
drwxrwxr-x 2 nobody root 4096 Aug 6 16:17 log
drwxrwxr-x 2 nobody root 4096 Jun 27 10:33 plugins
-rwxrwxr-x 1 nobody root 1110 Jun 26 09:38 red5.bat
-rwxrwxr-x 1 nobody root 168 Jun 26 09:38 red5-debug.bat
-rwxrwxr-x 1 nobody root 220 Jun 26 09:38 red5-debug.sh
-rwxrwxr-x 1 nobody root 1181 Jun 26 09:38 red5-highperf.bat
-rwxrwxr-x 1 nobody root 417 Jun 26 09:38 red5-highperf.sh
-rwxrwxr-x 1 nobody root 964093 Jun 26 09:38 red5.jar
-rwxrwxr-x 1 nobody root 1297 Jun 26 09:38 red5.sh
-rwxrwxr-x 1 nobody root 308 Jun 26 09:38 red5-shutdown.bat
-rwxrwxr-x 1 nobody root 344 Jun 26 09:38 red5-shutdown.sh
drwxrwxr-x 4 nobody root 4096 Jun 27 10:35 webapps
drwxr-xr-x 4 nobody nogroup 4096 Jun 27 10:43 work
The above path should exist because of
Step 10: Install compiled\Pre-Built OM 2.x
Now we need to move the compiled source into the correct location, in this system we are using
/usr/lib/red5, so issue the following commands to move the root folder over:
cd /usr/adm/2.0/dist
mv red5/ /usr/lib/
And set some permissions and ownerships
chown -R nobody /usr/lib/red5
chmod +x /usr/lib/red5/red5.sh
chmod +x /usr/lib/red5/red5-debug.sh
Thanks,
George Kirkham
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 7:38 AM
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me
Hello George and thank you
my answer below in red text
On Wed, Sep 5, 2012 at 9:46 PM, George Kirkham <gk...@co2crc.com.au> wrote:
Jean-Marie,
Can you please tell me a bit more detail about your OpenMeetings server;
1) What is the URL to the documentation that you used to build your OpenMeetings server? (which would therefore also be the documentation that you used to get the instructions on how to write your red5 script in your /etc/init.d/ folder.
https://cwiki.apache.org/confluence/download/attachments/27838216/Installing+OM2.x+On+Debian64+-+Headless.pdf
2) What is the URL which you used to download your OpenMeetings?
svn checkout http://svn.apache.org/repos/asf/incubator/openmeetings/branches/2.0/
3) What Operating system are you using? Maybe Ubuntu 10 or 12, or Debian Squeeze ?
vps Debian
4) What is the output if you run "ls -al /etc/init.d/red5" ?
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
5) Could you please zip your /etc/init.d/red5 file and then attach this zip file to your email. I will then unzip it here and inspect it for you.
6) What is the output if you run the two following commands?
netstat -anp | grep soffice
netstat -anp | grep java
root@vps-1105323-11088:~# netstat -anp | grep soffice
root@vps-1105323-11088:~# 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 1 0 216.224.171.20:5080 66.249.73.21:49052 CLOSE_WAIT 30842/java
tcp6 4 0 216.224.171.20:8088 96.254.171.2:50456 CLOSE_WAIT 30842/java
tcp6 0 0 127.0.0.1:34435 127.0.0.1:3306 ESTABLISHED 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 127.0.0.1:34433 127.0.0.1:3306 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
I have attached a zip file which contains three versions of the red5 script that I use, for Ubuntu 12 (red5.ubuntu), for Debian Squeeze (red5.squeeze), and red5.all should work on either Ubuntu 10 or 12, or Debian Squeeze.
Simply rename the script you want to use to red5 and copy it to your OpenMeetings server's /etc/init.d folder. Set it to be executable and then run it via;
cd /etc/init.d
red5
i used red5.debian from the zip file you attached
root@vps-1105323-11088:~# cd /etc/init.d
root@vps-1105323-11088:/etc/init.d# red5
-bash: red5: command not found
If this works and you run;
netstat -anp | grep java
You should get a number of lines, some of which will have something like the below text.
tcp6 0 0 :::1935 :::* LISTEN 1187/java
tcp6 0 0 :::42447 :::* LISTEN 1187/java
tcp6 0 0 :::5080 :::* LISTEN 1187/java
tcp6 0 0 :::8443 :::* LISTEN 1187/java
tcp6 0 0 :::9980 :::* LISTEN 1187/java
Thanks,
George Kirkham
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:26 AM
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me
no Sir i can not and i cant start red5
On Wed, Sep 5, 2012 at 10:01 PM, greenes <zu...@gmail.com> wrote:
...yes, "This does not matter"
it works fine. These lines does not matter.
Try to connect to OM...can you access with your browser??
Alvaro
El mié, 05-09-2012 a las 19:58 +0200, Jean-Marie Landri escribió:
> but nothing happened Sir, i get -
>
> start-stop-daemon: --start needs --exec or --startas
> Try 'start-stop-daemon --help' for more information.
>
>
> On Wed, Sep 5, 2012 at 9:52 PM, greenes <zu...@gmail.com> wrote:
> ...yes Jean-Marie..
>
>
>
> El mié, 05-09-2012 a las 19:50 +0200, Jean-Marie Landri
> escribió:
> > you mean from:
> > root@vps-1105323-11088:~# /etc/init.d/red5 start
> > start-stop-daemon: --start needs --exec or --startas
> > Try 'start-stop-daemon --help' for more information.
> >
> > root@vps-1105323-11088:~#
> >
> > On Wed, Sep 5, 2012 at 9:35 PM, greenes <zu...@gmail.com>
> wrote:
> > Jean-Marie,
> >
> > You must not go to:
> >
> > cd /usr/lib/red5
> >
> > ...to run the script file /etc/init.d/red5
> >
> > Please run it from:
> >
> > cd /home/your-user-name
> >
> > ...and now:
> >
> > /etc/init.d/red5 start
> >
> >
> > Alvaro
> >
> >
> > El mié, 05-09-2012 a las 18:54 +0200, Jean-Marie
> Landri
> > escribió:
> >
> > > Sorry Sir
> > > tha result
> > > -root@vps-1105323-11088:~# /etc/init.d/red5 start
> > > start-stop-daemon: --start needs --exec or
> --startas
> > > Try 'start-stop-daemon --help' for more
> information.
> > > /etc/init.d/red5: line 26: --chdir: command not
> found
> > >
> > >
> > > On Wed, Sep 5, 2012 at 6:49 PM, Jean-Marie Landri
> > > <je...@gmail.com> wrote:
> > > Hello Sir,
> > > i attached the new red5 file
> > > as i get the same result
> > >
> > > thank you sir
> > >
> > >
> > > On Wed, Sep 5, 2012 at 5:30 PM, Stephen
> Cottham
> > > <St...@robertbird.com.au> wrote:
> > > Hi Jean,
> > >
> > >
> > >
> > > Seems your cut and paste from the
> document
> > into the
> > > red5 script has not recognised
> character
> > returns,
> > > looks thru the script in an editor
> and make
> > sure that
> > > each line is correct, the
> tell-tale sign is
> > this part
> > >
> > >
> > >
> > > /etc/init.d/red5: line 9: Stephen:
> command
> > not found
> > >
> > >
> > >
> > >
> > > Best Regards
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > From: Jean-Marie Landri
> > > [mailto:jeanmarielandri@gmail.com]
> > > Sent: 05 September 2012 16:14
> > > To:
> openmeetings-user@incubator.apache.org
> > > Subject: red5 start script not
> work for me
> > >
> > >
> > >
> > > Hello
> > > to start red5 i'm using -
> cd /usr/lib/red5
> > > && ./red5-debug.sh - no problems
> > > now i'm trying to enable red5 auto
> start
> > script to
> > > work but with no succeed.
> > > i have attached the file...red5
> > > in shell:
> > >
> > > root@vps-1105323-11088:~# chmod
> > +x /etc/init.d/red5
> > >
> > > root@vps-1105323-11088:~#
> update-rc.d red5
> > defaults
> > > update-rc.d: using dependency
> based boot
> > sequencing
> > > insserv: warning: script
> 'K01drwebd' missing
> > LSB tags
> > > and overrides
> > > insserv: warning: script 'drwebd'
> missing
> > LSB tags and
> > > overrides
> > > insserv: script red5-OLD: service
> red5
> > already
> > > provided!
> > > insserv: script vzquota: service
> vzreboot
> > already
> > > provided!
> > > insserv: script sendmail: service
> sendmail
> > already
> > > provided!
> > >
> > >
> root@vps-1105323-11088:~# /etc/init.d/red5
> > start
> > > /etc/init.d/red5: line 9: Stephen:
> command
> > not found
> > > start-stop-daemon: --start needs
> --exec or
> > --startas
> > > Try 'start-stop-daemon --help' for
> more
> > information.
> > > /etc/init.d/red5: line 27:
> --chdir: command
> > not found
> > >
> > > thank you
> > >
> > >
> > >
> > >
> > > Stephen Cottham
> > > Group IT Manager (Associate)
> > >
> > > Robert Bird Group
> > > Level 5, 333 Ann St
> > > Brisbane, Queensland, 4000,
> Australia
> > >
> > > Phone: +6173 319 2777 <tel:%2B6173%20319%202777> (AUS)
> > >
> > > Phone: +44207 592 8000 <tel:%2B44207%20592%208000> (UK)
> > >
> > > Fax: +6173 319 2799 <tel:%2B6173%20319%202799>
> > >
> > >
> > >
> > > Mobile: +61400 756 963 <tel:%2B61400%20756%20963> (AUS)
> > >
> > > Mobile: +447900 918 616 <tel:%2B447900%20918%20616> (UK)
> > >
> > > Web: www.robertbird.com
> > >
> > >
> > >
> >
> > > This email and any attachments are
> > confidential and
> > > may contain legally privileged
> information
> > or
> > > copyright material. Unless
> expressly stated,
> > > confidentiality and/or legal
> privilege is
> > not intended
> > > to be waived by the sending of
> this email.
> > The
> > > contents of this email, including
> any
> > attachments, are
> > > intended solely for the use of the
> > individual or
> > > entity to whom they are addressed.
> If you
> > are not an
> > > intended recipient, please contact
> us
> > immediately by
> > > return email and then delete both
> messages.
> > You may
> > > not otherwise read, forward, copy,
> use or
> > disclose
> > > this email or any attachments. Any
> views
> > expressed in
> > > this email are those of the
> individual
> > sender except
> > > where the sender expressly, and
> with
> > authority, states
> > > otherwise. It is your
> responsibility to
> > check any
> > > attachments for viruses or defects
> before
> > opening or
> > > sending them on. None of the
> sender or its
> > related
> > > entities accepts any liability for
> any
> > consequential
> > > damage resulting from this email
> containing
> > computer
> > > viruses.
> > >
> > >
> > >
> > >
> >
> > > Disclaimer added by CodeTwo
> Exchange Rules
> > > www.codetwo.com
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by Stephen Cottham <St...@robertbird.com.au>.
To find the PID use
ps -ef | grep red5
This will show you the process for the red5 instance, then use
Kill -9 xxxxx where xxxx is the PID
From: George Kirkham [mailto:gkirkham@co2crc.com.au]
Sent: 06 September 2012 08:31
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 stop
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 start
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
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
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 (AUS)
Phone: +44207 592 8000 (UK)
Fax: +6173 319 2799
Mobile: +61400 756 963 (AUS)
Mobile: +447900 918 616 (UK)
Web: www.robertbird.com
This email and any attachments are confidential and may contain legally privileged information or copyright material. Unless expressly stated, confidentiality and/or legal privilege is not intended to be waived by the sending of this email. The contents of this email, including any attachments, are intended solely for the use of the individual or entity to whom they are addressed. If you are not an intended recipient, please contact us immediately by return email and then delete both messages. You may not otherwise read, forward, copy, use or disclose this email or any attachments. Any views expressed in this email are those of the individual sender except where the sender expressly, and with authority, states otherwise. It is your responsibility to check any attachments for viruses or defects before opening or sending them on. None of the sender or its related entities accepts any liability for any consequential damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
http://www.codetwo.com
-----Original Message-----
From: Seth Galitzer [mailto:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by Stephen Cottham <St...@robertbird.com.au>.
Did you copy over the red5 scripts that George sent to you yesterday? -
These are tested and working and should be the ones to use.
If you have done that then make sure it has execute permissions and yes
you can start the service again and continue your testing.
Best Regards
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 09:27
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
done!
root@vps-1105323-11088:~# kill -9 1569
root@vps-1105323-11088:~#
now to use the command - /etc/init.d/red5 start?
On Thu, Sep 6, 2012 at 10:06 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
No, the command in this case is
kill -9 1569
that will stop the instance running.
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 09:01
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
thank you sir
root@vps-1105323-11088:~# ps -ef | grep red5
nobody 1569 1 6 03:52 ? 00:00:20 /usr/bin/java
-Dpython.home=lib -Dred5.root=/usr/lib/red5
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -cp
/usr/lib/red5/boot.jar:/usr/lib/red5/conf: org.red5.server.Bootstrap
root 2246 1820 0 03:57 pts/0 00:00:00 grep red5
so the command is - kill -9 2246 ?
On Thu, Sep 6, 2012 at 9:51 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
I think its best if you don't copy and paste Jean-marie
You see you have .p instead of -p
The command should be
ps -ef | grep red5
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 08:48
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
Hello Sir
when-
root@vps-1105323-11088:~# ps .ef | grep red5
ERROR: Garbage option.
********* simple selection ********* ********* selection by list
*********
-A all processes -C by command name
-N negate selection -G by real group ID (supports
names)
-a all w/ tty except session leaders -U by real user ID (supports
names)
-d all except session leaders -g by session OR by effective
group name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports
names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options
***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy
it seems that there is ERROR: Garbage option
thank you
On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
Example
:~# ps -ef | grep red5
root 1207 1 0 Aug23 ? 00:24:06 /usr/bin/java
-Dpython.home=lib -Dred5.root=.
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
-Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
-XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
-XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none
-cp ./boot.jar:./conf: org.red5.server.Bootstrap
in this case the process is 1207
Then
kill -9 1207
Cheers
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 <tel:%2B6173%20319%202777> (AUS)
Phone: +44207 592 8000 <tel:%2B44207%20592%208000> (UK)
Fax: +6173 319 2799 <tel:%2B6173%20319%202799>
Mobile: +61400 756 963 <tel:%2B61400%20756%20963> (AUS)
Mobile: +447900 918 616 <tel:%2B447900%20918%20616> (UK)
Web: www.robertbird.com <http://www.robertbird.com/>
<http://www.robertbird.com.au/>
This email and any attachments are confidential and may contain legally
privileged information or copyright material. Unless expressly stated,
confidentiality and/or legal privilege is not intended to be waived by
the sending of this email. The contents of this email, including any
attachments, are intended solely for the use of the individual or entity
to whom they are addressed. If you are not an intended recipient, please
contact us immediately by return email and then delete both messages.
You may not otherwise read, forward, copy, use or disclose this email or
any attachments. Any views expressed in this email are those of the
individual sender except where the sender expressly, and with authority,
states otherwise. It is your responsibility to check any attachments for
viruses or defects before opening or sending them on. None of the sender
or its related entities accepts any liability for any consequential
damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
www.codetwo.com
From: Stephen Cottham
Sent: 06 September 2012 08:37
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
To find the PID use
ps -ef | grep red5
This will show you the process for the red5 instance, then use
Kill -9 xxxxx where xxxx is the PID
From: George Kirkham [mailto:gkirkham@co2crc.com.au]
Sent: 06 September 2012 08:31
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 stop
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 start
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
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
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 (AUS)
Phone: +44207 592 8000 (UK)
Fax: +6173 319 2799
Mobile: +61400 756 963 (AUS)
Mobile: +447900 918 616 (UK)
Web: www.robertbird.com
This email and any attachments are confidential and may contain legally privileged information or copyright material. Unless expressly stated, confidentiality and/or legal privilege is not intended to be waived by the sending of this email. The contents of this email, including any attachments, are intended solely for the use of the individual or entity to whom they are addressed. If you are not an intended recipient, please contact us immediately by return email and then delete both messages. You may not otherwise read, forward, copy, use or disclose this email or any attachments. Any views expressed in this email are those of the individual sender except where the sender expressly, and with authority, states otherwise. It is your responsibility to check any attachments for viruses or defects before opening or sending them on. None of the sender or its related entities accepts any liability for any consequential damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
http://www.codetwo.com
-----Original Message-----
From: Seth Galitzer [mailto:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
Re: Turkish Localization/Translation is OK
Posted by Maxim Solodovnik <so...@gmail.com>.
You have created issue against
"Jetspeed<https://issues.apache.org/jira/browse/JS1>"
project not Openmeetings (Jetspeed developers will be surprised :))
Could you please create issue at
https://issues.apache.org/jira/browse/OPENMEETINGS
On Thu, Sep 6, 2012 at 4:54 PM, bilgin yazar <bi...@hotmail.com>wrote:
>
> added to following for today
>
> https://issues.apache.org/jira/browse/JS1-417
>
>
>
> ------------------------------
> Date: Thu, 6 Sep 2012 16:47:26 +0700
> Subject: Re: Turkish Localization/Translation is OK
> From: solomax666@gmail.com
> To: openmeetings-user@incubator.apache.org
> CC: karalar88@gmail.com
>
> Hello Bilgin,
>
> I see no translation attached to your e-mail.
> Can you please create JIRA issue at
> https://issues.apache.org/jira/browse/OPENMEETINGS and attach translation
> to it.
>
> 2012/9/6 bilgin yazar <bi...@hotmail.com>
>
>
> Hi All
>
>
> Turkish Localization is attached.
> It was performed by ETGi Grup by Bilgin Yazar & Mehmet Karalar
>
>
> BR
>
> Bilgin Yazar
> Genel Müdür | President
> ETGI Grup | M:+90 555 448 53 85 | bilginyazar@etgigrup.com
> T:+90 (312) 344 88 83 | F: +90 (312) 344 88 84 | http://www.etgigrup.com
> A: Necatibey Mah. Mazi (Kastamonu) Sokak No:17/5
> 06250 Ulus Altındag ANKARA TURKEY
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
RE: Turkish Localization/Translation is OK
Posted by bilgin yazar <bi...@hotmail.com>.
added to following for today
https://issues.apache.org/jira/browse/JS1-417
Date: Thu, 6 Sep 2012 16:47:26 +0700
Subject: Re: Turkish Localization/Translation is OK
From: solomax666@gmail.com
To: openmeetings-user@incubator.apache.org
CC: karalar88@gmail.com
Hello Bilgin,
I see no translation attached to your e-mail.Can you please create JIRA issue at https://issues.apache.org/jira/browse/OPENMEETINGS and attach translation to it.
2012/9/6 bilgin yazar <bi...@hotmail.com>
Hi All
Turkish Localization is attached.
It was performed by ETGi Grup by Bilgin Yazar & Mehmet Karalar
BR
Bilgin Yazar
Genel Müdür | President
ETGI Grup | M:+90 555 448 53 85 | bilginyazar@etgigrup.com
T:+90 (312) 344 88 83 | F: +90 (312) 344 88 84 | http://www.etgigrup.com
A: Necatibey Mah. Mazi (Kastamonu) Sokak No:17/5
06250 Ulus Altındag ANKARA TURKEY
--
WBR
Maxim aka solomax
Re: Turkish Localization/Translation is OK
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello Bilgin,
I see no translation attached to your e-mail.
Can you please create JIRA issue at
https://issues.apache.org/jira/browse/OPENMEETINGS and attach translation
to it.
2012/9/6 bilgin yazar <bi...@hotmail.com>
> Hi All
>
>
> Turkish Localization is attached.
> It was performed by ETGi Grup by Bilgin Yazar & Mehmet Karalar
>
>
> BR
>
> Bilgin Yazar
> Genel Müdür | President
> ETGI Grup | M:+90 555 448 53 85 | bilginyazar@etgigrup.com
> T:+90 (312) 344 88 83 | F: +90 (312) 344 88 84 | http://www.etgigrup.com
> A: Necatibey Mah. Mazi (Kastamonu) Sokak No:17/5
> 06250 Ulus Altındag ANKARA TURKEY
>
>
--
WBR
Maxim aka solomax
Turkish Localization/Translation is OK
Posted by bilgin yazar <bi...@hotmail.com>.
Hi All
Turkish Localization is attached.
It was performed by ETGi Grup by Bilgin Yazar & Mehmet Karalar
BR
Bilgin Yazar
Genel Müdür | President
ETGI Grup | M:+90 555 448 53 85 | bilginyazar@etgigrup.com
T:+90 (312) 344 88 83 | F: +90 (312) 344 88 84 | http://www.etgigrup.com
A: Necatibey Mah. Mazi (Kastamonu) Sokak No:17/5
06250 Ulus Altındag ANKARA TURKEY
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by George Kirkham <gk...@co2crc.com.au>.
Jean-Marie,
I suggest doing the "netstat -anp | grep java" first to ensure that
there are no "java" processes still running. I assume this will be the
case.
But I also suggest running this sequence and it will show what is
happening quite clearly;
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
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 6:27 PM
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
done!
root@vps-1105323-11088:~# kill -9 1569
root@vps-1105323-11088:~#
now to use the command - /etc/init.d/red5 start?
On Thu, Sep 6, 2012 at 10:06 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
No, the command in this case is
kill -9 1569
that will stop the instance running.
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 09:01
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
thank you sir
root@vps-1105323-11088:~# ps -ef | grep red5
nobody 1569 1 6 03:52 ? 00:00:20 /usr/bin/java
-Dpython.home=lib -Dred5.root=/usr/lib/red5
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -cp
/usr/lib/red5/boot.jar:/usr/lib/red5/conf: org.red5.server.Bootstrap
root 2246 1820 0 03:57 pts/0 00:00:00 grep red5
so the command is - kill -9 2246 ?
On Thu, Sep 6, 2012 at 9:51 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
I think its best if you don't copy and paste Jean-marie
You see you have .p instead of -p
The command should be
ps -ef | grep red5
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 08:48
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
Hello Sir
when-
root@vps-1105323-11088:~# ps .ef | grep red5
ERROR: Garbage option.
********* simple selection ********* ********* selection by list
*********
-A all processes -C by command name
-N negate selection -G by real group ID (supports
names)
-a all w/ tty except session leaders -U by real user ID (supports
names)
-d all except session leaders -g by session OR by effective
group name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports
names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options
***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy
it seems that there is ERROR: Garbage option
thank you
On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
Example
:~# ps -ef | grep red5
root 1207 1 0 Aug23 ? 00:24:06 /usr/bin/java
-Dpython.home=lib -Dred5.root=.
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
-Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
-XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
-XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none
-cp ./boot.jar:./conf: org.red5.server.Bootstrap
in this case the process is 1207
Then
kill -9 1207
Cheers
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 <tel:%2B6173%20319%202777> (AUS)
Phone: +44207 592 8000 <tel:%2B44207%20592%208000> (UK)
Fax: +6173 319 2799 <tel:%2B6173%20319%202799>
Mobile: +61400 756 963 <tel:%2B61400%20756%20963> (AUS)
Mobile: +447900 918 616 <tel:%2B447900%20918%20616> (UK)
Web: www.robertbird.com <http://www.robertbird.com/>
<http://www.robertbird.com.au/>
This email and any attachments are confidential and may contain legally
privileged information or copyright material. Unless expressly stated,
confidentiality and/or legal privilege is not intended to be waived by
the sending of this email. The contents of this email, including any
attachments, are intended solely for the use of the individual or entity
to whom they are addressed. If you are not an intended recipient, please
contact us immediately by return email and then delete both messages.
You may not otherwise read, forward, copy, use or disclose this email or
any attachments. Any views expressed in this email are those of the
individual sender except where the sender expressly, and with authority,
states otherwise. It is your responsibility to check any attachments for
viruses or defects before opening or sending them on. None of the sender
or its related entities accepts any liability for any consequential
damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
www.codetwo.com
From: Stephen Cottham
Sent: 06 September 2012 08:37
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
To find the PID use
ps -ef | grep red5
This will show you the process for the red5 instance, then use
Kill -9 xxxxx where xxxx is the PID
From: George Kirkham [mailto:gkirkham@co2crc.com.au]
Sent: 06 September 2012 08:31
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 stop
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 start
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
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:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
Re: red5 start script not work for me vps-1105323-11088 netstat -anp
| grep java
Posted by Jean-Marie Landri <je...@gmail.com>.
done!
root@vps-1105323-11088:~# kill -9 1569
root@vps-1105323-11088:~#
now to use the command - /etc/init.d/red5 start?
On Thu, Sep 6, 2012 at 10:06 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
> No, the command in this case is****
>
> ** **
>
> *kill -9 1569*
>
> ** **
>
> that will stop the instance running.****
>
> ** **
>
> *From:* Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
> *Sent:* 06 September 2012 09:01
>
> *To:* openmeetings-user@incubator.apache.org
> *Subject:* Re: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ** **
>
> thank you sir
>
> root@vps-1105323-11088:~# ps -ef | grep red5
> nobody 1569 1 6 03:52 ? 00:00:20 /usr/bin/java
> -Dpython.home=lib -Dred5.root=/usr/lib/red5
> -Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
> -Dcatalina.useNaming=true -Djava.security.debug=failure -cp
> /usr/lib/red5/boot.jar:/usr/lib/red5/conf: org.red5.server.Bootstrap
> root 2246 1820 0 03:57 pts/0 00:00:00 grep red5
>
> so the command is - *kill -9 2246 ?
>
> *****
>
> On Thu, Sep 6, 2012 at 9:51 AM, Stephen Cottham <
> Stephen.Cottham@robertbird.com.au> wrote:****
>
> I think its best if you don’t copy and paste Jean-marie****
>
> ****
>
> You see you have .p instead of -p****
>
> ****
>
> The command should be****
>
> ****
>
> ps -ef | grep red5****
>
> ****
>
> *From:* Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
> *Sent:* 06 September 2012 08:48****
>
>
> *To:* openmeetings-user@incubator.apache.org
> *Subject:* Re: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ****
>
> Hello Sir
> when-
> root@vps-1105323-11088:~# ps .ef | grep red5
> ERROR: Garbage option.
> ********* simple selection ********* ********* selection by list *********
> -A all processes -C by command name
> -N negate selection -G by real group ID (supports names)
> -a all w/ tty except session leaders -U by real user ID (supports names)
> -d all except session leaders -g by session OR by effective group
> name
> -e all processes -p by process ID
> T all processes on this terminal -s processes in the sessions given
> a all w/ tty, including other users -t by tty
> g OBSOLETE -- DO NOT USE -u by effective user ID (supports
> names)
> r only running processes U processes for specified users
> x processes w/o controlling ttys t by tty
> *********** output format ********** *********** long options ***********
> -o,o user-defined -f full --Group --User --pid --cols --ppid
> -j,j job control s signal --group --user --sid --rows --info
> -O,O preloaded -o v virtual memory --cumulative --format --deselect
> -l,l long u user-oriented --sort --tty --forest --version
> -F extra full X registers --heading --no-heading --context
> ********* misc options *********
> -V,V show version L list format codes f ASCII art forest
> -m,m,-L,-T,H threads S children in sum -y change -l format
> -M,Z security data c true command name -c scheduling class
> -w,w wide output n numeric WCHAN,UID -H process hierarchy
> it seems that there is ERROR: Garbage option
>
> thank you****
>
> On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
> Stephen.Cottham@robertbird.com.au> wrote:****
>
> Example****
>
> ****
>
> :~# *ps -ef | grep red5*****
>
> root *1207* 1 0 Aug23 ? 00:24:06 /usr/bin/java
> -Dpython.home=lib -Dred5.root=.
> -Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
> -Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
> -Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
> -XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
> -XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none -cp
> ./boot.jar:./conf: org.red5.server.Bootstrap****
>
> ****
>
> in this case the process is *1207*****
>
> * *****
>
> Then****
>
> * *****
>
> *kill -9 1207*****
>
> * *****
>
> Cheers****
>
> * *****
>
> * *****
>
> * *****
>
> ****
>
> *Stephen Cottham
> *Group IT Manager (Associate)
>
> Robert Bird Group
> Level 5, 333 Ann St
> Brisbane, Queensland, 4000, Australia****
>
> *Phone: +6173 319 2777 (AUS)*****
>
> *Phone: +44207 592 8000 (UK)*****
>
> *Fax: +6173 319 2799*****
>
> ****
>
> *Mobile: +61400 756 963 (AUS)*****
>
> *Mobile: +447900 918 616 (UK)*****
>
> *Web: **www.robertbird.com* <http://www.robertbird.com/>****
>
> <http://www.robertbird.com.au/>
>
> This email and any attachments are confidential and may contain legally
> privileged information or copyright material. Unless expressly stated,
> confidentiality and/or legal privilege is not intended to be waived by the
> sending of this email. The contents of this email, including any
> attachments, are intended solely for the use of the individual or entity to
> whom they are addressed. If you are not an intended recipient, please
> contact us immediately by return email and then delete both messages. You
> may not otherwise read, forward, copy, use or disclose this email or any
> attachments. Any views expressed in this email are those of the individual
> sender except where the sender expressly, and with authority, states
> otherwise. It is your responsibility to check any attachments for viruses
> or defects before opening or sending them on. None of the sender or its
> related entities accepts any liability for any consequential damage
> resulting from this email containing computer viruses. ****
>
> ****
>
>
> Disclaimer added by *CodeTwo Exchange Rules*
> www.codetwo.com****
>
> ****
>
> *From:* Stephen Cottham
> *Sent:* 06 September 2012 08:37
> *To:* openmeetings-user@incubator.apache.org
> *Subject:* RE: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ****
>
> To find the PID use****
>
> ****
>
> ps –ef | grep red5****
>
> ****
>
> This will show you the process for the red5 instance, then use ****
>
> ****
>
> Kill -9 xxxxx where xxxx is the PID****
>
> ****
>
> ****
>
> ****
>
> *From:* George Kirkham [mailto:gkirkham@co2crc.com.au] ****
>
> *Sent:* 06 September 2012 08:31
> *To:* openmeetings-user@incubator.apache.org****
>
> *Subject:* RE: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ****
>
> 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:jeanmarielandri@gmail.com]
> *Sent:* Thursday, 6 September 2012 4:54 PM
> *To:* openmeetings-user@incubator.apache.org
> *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# <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>
>
> 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>
>
> 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>
>
> 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# <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>
>
> 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# <root@vps-1105323-11088:/etc/init.d>**
> **
>
> On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
> 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# <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:sgsax@ksu.edu]
> Sent: Thursday, 6 September 2012 8:23 AM
> To: openmeetings-user@incubator.apache.org
> 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# <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****
>
> sgsax@ksu.edu****
>
> 785-532-7790****
>
> ****
>
> ****
>
> ****
>
> ** **
>
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by George Kirkham <gk...@co2crc.com.au>.
Stephen,
Thanks for the "ps -ef | grep red5" command, most useful. I had not
used the -ef previously.
# ps -ef | grep red5
_red5 1187 1 0 Aug14 ? 00:28:03
/usr/lib/jvm/java-6-openjdk//bin/java -Dpython.home=lib
-Dred5.root=/usr/share/red5/
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -cp
/usr/share/red5//boot.jar:/usr/share/red5//conf:
org.red5.server.Bootstrap
root 27662 27645 0 18:23 pts/2 00:00:00 grep red5
# ps aux | grep java
_red5 1187 0.0 2.0 701096 84708 ? Sl Aug14 28:03
/usr/lib/jvm/java-6-openjdk//bin/java -Dpython.home=lib
-Dred5.root=/usr/share/red5/
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -cp
/usr/share/red5//boot.jar:/usr/share/red5//conf:
org.red5.server.Bootstrap
root 27712 0.0 0.0 3304 756 pts/2 S+ 18:26 0:00 grep
java
# netstat -anp red5 | grep java
tcp6 0 0 :::1935 :::*
LISTEN 1187/java
tcp6 0 0 :::42447 :::*
LISTEN 1187/java
tcp6 0 0 :::5080 :::*
LISTEN 1187/java
tcp6 0 0 :::8443 :::*
LISTEN 1187/java
tcp6 0 0 :::9980 :::*
LISTEN 1187/java
Thanks,
George Kirkham
From: Stephen Cottham [mailto:Stephen.Cottham@robertbird.com.au]
Sent: Thursday, 6 September 2012 6:06 PM
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
No, the command in this case is
kill -9 1569
that will stop the instance running.
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 09:01
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
thank you sir
root@vps-1105323-11088:~# ps -ef | grep red5
nobody 1569 1 6 03:52 ? 00:00:20 /usr/bin/java
-Dpython.home=lib -Dred5.root=/usr/lib/red5
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -cp
/usr/lib/red5/boot.jar:/usr/lib/red5/conf: org.red5.server.Bootstrap
root 2246 1820 0 03:57 pts/0 00:00:00 grep red5
so the command is - kill -9 2246 ?
On Thu, Sep 6, 2012 at 9:51 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
I think its best if you don't copy and paste Jean-marie
You see you have .p instead of -p
The command should be
ps -ef | grep red5
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 08:48
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
Hello Sir
when-
root@vps-1105323-11088:~# ps .ef | grep red5
ERROR: Garbage option.
********* simple selection ********* ********* selection by list
*********
-A all processes -C by command name
-N negate selection -G by real group ID (supports
names)
-a all w/ tty except session leaders -U by real user ID (supports
names)
-d all except session leaders -g by session OR by effective
group name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports
names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options
***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy
it seems that there is ERROR: Garbage option
thank you
On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
Example
:~# ps -ef | grep red5
root 1207 1 0 Aug23 ? 00:24:06 /usr/bin/java
-Dpython.home=lib -Dred5.root=.
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
-Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
-XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
-XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none
-cp ./boot.jar:./conf: org.red5.server.Bootstrap
in this case the process is 1207
Then
kill -9 1207
Cheers
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 <tel:%2B6173%20319%202777> (AUS)
Phone: +44207 592 8000 <tel:%2B44207%20592%208000> (UK)
Fax: +6173 319 2799 <tel:%2B6173%20319%202799>
Mobile: +61400 756 963 <tel:%2B61400%20756%20963> (AUS)
Mobile: +447900 918 616 <tel:%2B447900%20918%20616> (UK)
Web: www.robertbird.com <http://www.robertbird.com/>
<http://www.robertbird.com.au/>
This email and any attachments are confidential and may contain legally
privileged information or copyright material. Unless expressly stated,
confidentiality and/or legal privilege is not intended to be waived by
the sending of this email. The contents of this email, including any
attachments, are intended solely for the use of the individual or entity
to whom they are addressed. If you are not an intended recipient, please
contact us immediately by return email and then delete both messages.
You may not otherwise read, forward, copy, use or disclose this email or
any attachments. Any views expressed in this email are those of the
individual sender except where the sender expressly, and with authority,
states otherwise. It is your responsibility to check any attachments for
viruses or defects before opening or sending them on. None of the sender
or its related entities accepts any liability for any consequential
damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
www.codetwo.com
From: Stephen Cottham
Sent: 06 September 2012 08:37
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
To find the PID use
ps -ef | grep red5
This will show you the process for the red5 instance, then use
Kill -9 xxxxx where xxxx is the PID
From: George Kirkham [mailto:gkirkham@co2crc.com.au]
Sent: 06 September 2012 08:31
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 stop
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 start
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
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:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by Stephen Cottham <St...@robertbird.com.au>.
No, the command in this case is
kill -9 1569
that will stop the instance running.
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 09:01
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
thank you sir
root@vps-1105323-11088:~# ps -ef | grep red5
nobody 1569 1 6 03:52 ? 00:00:20 /usr/bin/java
-Dpython.home=lib -Dred5.root=/usr/lib/red5
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -cp
/usr/lib/red5/boot.jar:/usr/lib/red5/conf: org.red5.server.Bootstrap
root 2246 1820 0 03:57 pts/0 00:00:00 grep red5
so the command is - kill -9 2246 ?
On Thu, Sep 6, 2012 at 9:51 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
I think its best if you don't copy and paste Jean-marie
You see you have .p instead of -p
The command should be
ps -ef | grep red5
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 08:48
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
Hello Sir
when-
root@vps-1105323-11088:~# ps .ef | grep red5
ERROR: Garbage option.
********* simple selection ********* ********* selection by list
*********
-A all processes -C by command name
-N negate selection -G by real group ID (supports
names)
-a all w/ tty except session leaders -U by real user ID (supports
names)
-d all except session leaders -g by session OR by effective
group name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports
names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options
***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy
it seems that there is ERROR: Garbage option
thank you
On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
Example
:~# ps -ef | grep red5
root 1207 1 0 Aug23 ? 00:24:06 /usr/bin/java
-Dpython.home=lib -Dred5.root=.
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
-Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
-XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
-XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none
-cp ./boot.jar:./conf: org.red5.server.Bootstrap
in this case the process is 1207
Then
kill -9 1207
Cheers
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 <tel:%2B6173%20319%202777> (AUS)
Phone: +44207 592 8000 <tel:%2B44207%20592%208000> (UK)
Fax: +6173 319 2799 <tel:%2B6173%20319%202799>
Mobile: +61400 756 963 <tel:%2B61400%20756%20963> (AUS)
Mobile: +447900 918 616 <tel:%2B447900%20918%20616> (UK)
Web: www.robertbird.com <http://www.robertbird.com/>
<http://www.robertbird.com.au/>
This email and any attachments are confidential and may contain legally
privileged information or copyright material. Unless expressly stated,
confidentiality and/or legal privilege is not intended to be waived by
the sending of this email. The contents of this email, including any
attachments, are intended solely for the use of the individual or entity
to whom they are addressed. If you are not an intended recipient, please
contact us immediately by return email and then delete both messages.
You may not otherwise read, forward, copy, use or disclose this email or
any attachments. Any views expressed in this email are those of the
individual sender except where the sender expressly, and with authority,
states otherwise. It is your responsibility to check any attachments for
viruses or defects before opening or sending them on. None of the sender
or its related entities accepts any liability for any consequential
damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
www.codetwo.com
From: Stephen Cottham
Sent: 06 September 2012 08:37
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
To find the PID use
ps -ef | grep red5
This will show you the process for the red5 instance, then use
Kill -9 xxxxx where xxxx is the PID
From: George Kirkham [mailto:gkirkham@co2crc.com.au]
Sent: 06 September 2012 08:31
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 stop
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 start
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
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
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 (AUS)
Phone: +44207 592 8000 (UK)
Fax: +6173 319 2799
Mobile: +61400 756 963 (AUS)
Mobile: +447900 918 616 (UK)
Web: www.robertbird.com
This email and any attachments are confidential and may contain legally privileged information or copyright material. Unless expressly stated, confidentiality and/or legal privilege is not intended to be waived by the sending of this email. The contents of this email, including any attachments, are intended solely for the use of the individual or entity to whom they are addressed. If you are not an intended recipient, please contact us immediately by return email and then delete both messages. You may not otherwise read, forward, copy, use or disclose this email or any attachments. Any views expressed in this email are those of the individual sender except where the sender expressly, and with authority, states otherwise. It is your responsibility to check any attachments for viruses or defects before opening or sending them on. None of the sender or its related entities accepts any liability for any consequential damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
http://www.codetwo.com
-----Original Message-----
From: Seth Galitzer [mailto:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
Re: red5 start script not work for me vps-1105323-11088 netstat -anp
| grep java
Posted by Jean-Marie Landri <je...@gmail.com>.
thank you sir
root@vps-1105323-11088:~# ps -ef | grep red5
nobody 1569 1 6 03:52 ? 00:00:20 /usr/bin/java
-Dpython.home=lib -Dred5.root=/usr/lib/red5
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -cp
/usr/lib/red5/boot.jar:/usr/lib/red5/conf: org.red5.server.Bootstrap
root 2246 1820 0 03:57 pts/0 00:00:00 grep red5
so the command is - *kill -9 2246 ?
*
On Thu, Sep 6, 2012 at 9:51 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
> I think its best if you don’t copy and paste Jean-marie****
>
> ** **
>
> You see you have .p instead of -p****
>
> ** **
>
> The command should be****
>
> ** **
>
> ps -ef | grep red5****
>
> ** **
>
> *From:* Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
> *Sent:* 06 September 2012 08:48
>
> *To:* openmeetings-user@incubator.apache.org
> *Subject:* Re: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ** **
>
> Hello Sir
> when-
> root@vps-1105323-11088:~# ps .ef | grep red5
> ERROR: Garbage option.
> ********* simple selection ********* ********* selection by list *********
> -A all processes -C by command name
> -N negate selection -G by real group ID (supports names)
> -a all w/ tty except session leaders -U by real user ID (supports names)
> -d all except session leaders -g by session OR by effective group
> name
> -e all processes -p by process ID
> T all processes on this terminal -s processes in the sessions given
> a all w/ tty, including other users -t by tty
> g OBSOLETE -- DO NOT USE -u by effective user ID (supports
> names)
> r only running processes U processes for specified users
> x processes w/o controlling ttys t by tty
> *********** output format ********** *********** long options ***********
> -o,o user-defined -f full --Group --User --pid --cols --ppid
> -j,j job control s signal --group --user --sid --rows --info
> -O,O preloaded -o v virtual memory --cumulative --format --deselect
> -l,l long u user-oriented --sort --tty --forest --version
> -F extra full X registers --heading --no-heading --context
> ********* misc options *********
> -V,V show version L list format codes f ASCII art forest
> -m,m,-L,-T,H threads S children in sum -y change -l format
> -M,Z security data c true command name -c scheduling class
> -w,w wide output n numeric WCHAN,UID -H process hierarchy
> it seems that there is ERROR: Garbage option
>
> thank you****
>
> On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
> Stephen.Cottham@robertbird.com.au> wrote:****
>
> Example****
>
> ****
>
> :~# *ps -ef | grep red5*****
>
> root *1207* 1 0 Aug23 ? 00:24:06 /usr/bin/java
> -Dpython.home=lib -Dred5.root=.
> -Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
> -Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
> -Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
> -XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
> -XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none -cp
> ./boot.jar:./conf: org.red5.server.Bootstrap****
>
> ****
>
> in this case the process is *1207*****
>
> * *****
>
> Then****
>
> * *****
>
> *kill -9 1207*****
>
> * *****
>
> Cheers****
>
> * *****
>
> * *****
>
> * *****
>
> ****
>
> *Stephen Cottham
> *Group IT Manager (Associate)
>
> Robert Bird Group
> Level 5, 333 Ann St
> Brisbane, Queensland, 4000, Australia****
>
> *Phone: +6173 319 2777 (AUS)*****
>
> *Phone: +44207 592 8000 (UK)*****
>
> *Fax: +6173 319 2799*****
>
> ****
>
> *Mobile: +61400 756 963 (AUS)*****
>
> *Mobile: +447900 918 616 (UK)*****
>
> *Web: **www.robertbird.com* <http://www.robertbird.com/>****
>
> <http://www.robertbird.com.au/>
>
> This email and any attachments are confidential and may contain legally
> privileged information or copyright material. Unless expressly stated,
> confidentiality and/or legal privilege is not intended to be waived by the
> sending of this email. The contents of this email, including any
> attachments, are intended solely for the use of the individual or entity to
> whom they are addressed. If you are not an intended recipient, please
> contact us immediately by return email and then delete both messages. You
> may not otherwise read, forward, copy, use or disclose this email or any
> attachments. Any views expressed in this email are those of the individual
> sender except where the sender expressly, and with authority, states
> otherwise. It is your responsibility to check any attachments for viruses
> or defects before opening or sending them on. None of the sender or its
> related entities accepts any liability for any consequential damage
> resulting from this email containing computer viruses. ****
>
> ****
>
>
> Disclaimer added by *CodeTwo Exchange Rules*
> www.codetwo.com****
>
> ** **
>
> *From:* Stephen Cottham
> *Sent:* 06 September 2012 08:37
> *To:* openmeetings-user@incubator.apache.org
> *Subject:* RE: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ****
>
> To find the PID use****
>
> ****
>
> ps –ef | grep red5****
>
> ****
>
> This will show you the process for the red5 instance, then use ****
>
> ****
>
> Kill -9 xxxxx where xxxx is the PID****
>
> ****
>
> ****
>
> ****
>
> *From:* George Kirkham [mailto:gkirkham@co2crc.com.au] ****
>
> *Sent:* 06 September 2012 08:31
> *To:* openmeetings-user@incubator.apache.org****
>
> *Subject:* RE: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ****
>
> 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:jeanmarielandri@gmail.com]
> *Sent:* Thursday, 6 September 2012 4:54 PM
> *To:* openmeetings-user@incubator.apache.org
> *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# <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>
>
> 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>
>
> 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>
>
> 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# <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>
>
> 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# <root@vps-1105323-11088:/etc/init.d>**
> **
>
> On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
> 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# <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:sgsax@ksu.edu]
> Sent: Thursday, 6 September 2012 8:23 AM
> To: openmeetings-user@incubator.apache.org
> 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# <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****
>
> sgsax@ksu.edu****
>
> 785-532-7790****
>
> ****
>
> ****
>
> ** **
>
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by Stephen Cottham <St...@robertbird.com.au>.
I think its best if you don't copy and paste Jean-marie
You see you have .p instead of -p
The command should be
ps -ef | grep red5
From: Jean-Marie Landri [mailto:jeanmarielandri@gmail.com]
Sent: 06 September 2012 08:48
To: openmeetings-user@incubator.apache.org
Subject: Re: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
Hello Sir
when-
root@vps-1105323-11088:~# ps .ef | grep red5
ERROR: Garbage option.
********* simple selection ********* ********* selection by list
*********
-A all processes -C by command name
-N negate selection -G by real group ID (supports
names)
-a all w/ tty except session leaders -U by real user ID (supports
names)
-d all except session leaders -g by session OR by effective
group name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports
names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options
***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy
it seems that there is ERROR: Garbage option
thank you
On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
Example
:~# ps -ef | grep red5
root 1207 1 0 Aug23 ? 00:24:06 /usr/bin/java
-Dpython.home=lib -Dred5.root=.
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
-Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
-XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
-XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none
-cp ./boot.jar:./conf: org.red5.server.Bootstrap
in this case the process is 1207
Then
kill -9 1207
Cheers
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 <tel:%2B6173%20319%202777> (AUS)
Phone: +44207 592 8000 <tel:%2B44207%20592%208000> (UK)
Fax: +6173 319 2799 <tel:%2B6173%20319%202799>
Mobile: +61400 756 963 <tel:%2B61400%20756%20963> (AUS)
Mobile: +447900 918 616 <tel:%2B447900%20918%20616> (UK)
Web: www.robertbird.com <http://www.robertbird.com/>
<http://www.robertbird.com.au/>
This email and any attachments are confidential and may contain legally
privileged information or copyright material. Unless expressly stated,
confidentiality and/or legal privilege is not intended to be waived by
the sending of this email. The contents of this email, including any
attachments, are intended solely for the use of the individual or entity
to whom they are addressed. If you are not an intended recipient, please
contact us immediately by return email and then delete both messages.
You may not otherwise read, forward, copy, use or disclose this email or
any attachments. Any views expressed in this email are those of the
individual sender except where the sender expressly, and with authority,
states otherwise. It is your responsibility to check any attachments for
viruses or defects before opening or sending them on. None of the sender
or its related entities accepts any liability for any consequential
damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
www.codetwo.com
From: Stephen Cottham
Sent: 06 September 2012 08:37
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
To find the PID use
ps -ef | grep red5
This will show you the process for the red5 instance, then use
Kill -9 xxxxx where xxxx is the PID
From: George Kirkham [mailto:gkirkham@co2crc.com.au]
Sent: 06 September 2012 08:31
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 stop
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 start
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
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
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 (AUS)
Phone: +44207 592 8000 (UK)
Fax: +6173 319 2799
Mobile: +61400 756 963 (AUS)
Mobile: +447900 918 616 (UK)
Web: www.robertbird.com
This email and any attachments are confidential and may contain legally privileged information or copyright material. Unless expressly stated, confidentiality and/or legal privilege is not intended to be waived by the sending of this email. The contents of this email, including any attachments, are intended solely for the use of the individual or entity to whom they are addressed. If you are not an intended recipient, please contact us immediately by return email and then delete both messages. You may not otherwise read, forward, copy, use or disclose this email or any attachments. Any views expressed in this email are those of the individual sender except where the sender expressly, and with authority, states otherwise. It is your responsibility to check any attachments for viruses or defects before opening or sending them on. None of the sender or its related entities accepts any liability for any consequential damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
http://www.codetwo.com
-----Original Message-----
From: Seth Galitzer [mailto:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
Re: red5 start script not work for me vps-1105323-11088 netstat -anp
| grep java
Posted by Jean-Marie Landri <je...@gmail.com>.
Hello Sir
when-
root@vps-1105323-11088:~# ps .ef | grep red5
ERROR: Garbage option.
********* simple selection ********* ********* selection by list *********
-A all processes -C by command name
-N negate selection -G by real group ID (supports names)
-a all w/ tty except session leaders -U by real user ID (supports names)
-d all except session leaders -g by session OR by effective group
name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports
names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options ***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy
it seems that there is ERROR: Garbage option
thank you
On Thu, Sep 6, 2012 at 9:38 AM, Stephen Cottham <
Stephen.Cottham@robertbird.com.au> wrote:
> Example****
>
> ** **
>
> :~# *ps -ef | grep red5*****
>
> root *1207* 1 0 Aug23 ? 00:24:06 /usr/bin/java
> -Dpython.home=lib -Dred5.root=.
> -Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
> -Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
> -Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
> -XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
> -XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none -cp
> ./boot.jar:./conf: org.red5.server.Bootstrap****
>
> ** **
>
> in this case the process is *1207*
>
> * *
>
> Then****
>
> * *
>
> *kill -9 1207*
>
> * *
>
> Cheers****
>
> * *
>
> * *
>
> * *
>
> ** **
>
> *Stephen Cottham**
> *Group IT Manager (Associate)
>
> Robert Bird Group
> Level 5, 333 Ann St
> Brisbane, Queensland, 4000, Australia****
>
> *Phone: +6173 319 2777 (AUS)*
>
> *Phone: +44207 592 8000 (UK)*****
>
> *Fax: +6173 319 2799*
>
> ******
>
> *Mobile: +61400 756 963 (AUS)*
>
> *Mobile: +447900 918 616 (UK)*
>
> *Web: **www.robertbird.com* <http://www.robertbird.com/>****
>
> ********************************************************************<http://www.robertbird.com.au/><http://www.robertbird.com.au/>
>
> This email and any attachments are confidential and may contain legally
> privileged information or copyright material. Unless expressly stated,
> confidentiality and/or legal privilege is not intended to be waived by the
> sending of this email. The contents of this email, including any
> attachments, are intended solely for the use of the individual or entity to
> whom they are addressed. If you are not an intended recipient, please
> contact us immediately by return email and then delete both messages. You
> may not otherwise read, forward, copy, use or disclose this email or any
> attachments. Any views expressed in this email are those of the individual
> sender except where the sender expressly, and with authority, states
> otherwise. It is your responsibility to check any attachments for viruses
> or defects before opening or sending them on. None of the sender or its
> related entities accepts any liability for any consequential damage
> resulting from this email containing computer viruses.
>
>
> Disclaimer added by *CodeTwo Exchange Rules*
> www.codetwo.com
>
> *From:* Stephen Cottham
> *Sent:* 06 September 2012 08:37
> *To:* openmeetings-user@incubator.apache.org
> *Subject:* RE: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ** **
>
> To find the PID use****
>
> ** **
>
> ps –ef | grep red5****
>
> ** **
>
> This will show you the process for the red5 instance, then use ****
>
> ** **
>
> Kill -9 xxxxx where xxxx is the PID****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* George Kirkham [mailto:gkirkham@co2crc.com.au]
> *Sent:* 06 September 2012 08:31
> *To:* openmeetings-user@incubator.apache.org
> *Subject:* RE: red5 start script not work for me vps-1105323-11088
> netstat -anp | grep java****
>
> ** **
>
> 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:jeanmarielandri@gmail.com]
> *Sent:* Thursday, 6 September 2012 4:54 PM
> *To:* openmeetings-user@incubator.apache.org
> *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# <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>
>
> 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>
>
> 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>
>
> 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# <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>
>
> 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# <root@vps-1105323-11088:/etc/init.d>**
> **
>
> On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
> 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# <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:sgsax@ksu.edu]
> Sent: Thursday, 6 September 2012 8:23 AM
> To: openmeetings-user@incubator.apache.org
> 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# <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****
>
> sgsax@ksu.edu****
>
> 785-532-7790****
>
> ****
>
> ** **
>
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by Stephen Cottham <St...@robertbird.com.au>.
Example
:~# ps -ef | grep red5
root 1207 1 0 Aug23 ? 00:24:06 /usr/bin/java
-Dpython.home=lib -Dred5.root=.
-Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
-Dcatalina.useNaming=true -Djava.security.debug=failure -Xrs -Xms512M
-Xmx1024M -Xss128K -XX:NewSize=256m -XX:SurvivorRatio=16
-XX:MinHeapFreeRatio=20 -XX:+ExplicitGCInvokesConcurrent
-XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Xverify:none
-cp ./boot.jar:./conf: org.red5.server.Bootstrap
in this case the process is 1207
Then
kill -9 1207
Cheers
From: Stephen Cottham
Sent: 06 September 2012 08:37
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
To find the PID use
ps -ef | grep red5
This will show you the process for the red5 instance, then use
Kill -9 xxxxx where xxxx is the PID
From: George Kirkham [mailto:gkirkham@co2crc.com.au]
Sent: 06 September 2012 08:31
To: openmeetings-user@incubator.apache.org
Subject: RE: red5 start script not work for me vps-1105323-11088 netstat
-anp | grep java
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 stop
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d> /etc/init.d/red5 start
root@vps-1105323-11088:/etc/init.d#
<mailto:root@vps-1105323-11088:/etc/init.d>
root@vps-1105323-11088:/etc/init.d#
<mailto: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#
<mailto:root@vps-1105323-11088:/etc/init.d>
On Thu, Sep 6, 2012 at 12:44 AM, George Kirkham <gk...@co2crc.com.au>
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
Stephen Cottham
Group IT Manager (Associate)
Robert Bird Group
Level 5, 333 Ann St
Brisbane, Queensland, 4000, Australia
Phone: +6173 319 2777 (AUS)
Phone: +44207 592 8000 (UK)
Fax: +6173 319 2799
Mobile: +61400 756 963 (AUS)
Mobile: +447900 918 616 (UK)
Web: www.robertbird.com
This email and any attachments are confidential and may contain legally privileged information or copyright material. Unless expressly stated, confidentiality and/or legal privilege is not intended to be waived by the sending of this email. The contents of this email, including any attachments, are intended solely for the use of the individual or entity to whom they are addressed. If you are not an intended recipient, please contact us immediately by return email and then delete both messages. You may not otherwise read, forward, copy, use or disclose this email or any attachments. Any views expressed in this email are those of the individual sender except where the sender expressly, and with authority, states otherwise. It is your responsibility to check any attachments for viruses or defects before opening or sending them on. None of the sender or its related entities accepts any liability for any consequential damage resulting from this email containing computer viruses.
Disclaimer added by CodeTwo Exchange Rules
http://www.codetwo.com
-----Original Message-----
From: Seth Galitzer [mailto:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by George Kirkham <gk...@co2crc.com.au>.
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:jeanmarielandri@gmail.com]
Sent: Thursday, 6 September 2012 4:54 PM
To: openmeetings-user@incubator.apache.org
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 <gk...@co2crc.com.au>
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:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
Re: red5 start script not work for me vps-1105323-11088 netstat -anp
| grep java
Posted by Jean-Marie Landri <je...@gmail.com>.
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 <gk...@co2crc.com.au>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# <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:sgsax@ksu.edu]
> Sent: Thursday, 6 September 2012 8:23 AM
> To: openmeetings-user@incubator.apache.org
> 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# 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****
>
> sgsax@ksu.edu****
>
> 785-532-7790****
>
> ** **
>
RE: red5 start script not work for me vps-1105323-11088 netstat -anp | grep java
Posted by George Kirkham <gk...@co2crc.com.au>.
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:sgsax@ksu.edu]
Sent: Thursday, 6 September 2012 8:23 AM
To: openmeetings-user@incubator.apache.org
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>
sgsax@ksu.edu <ma...@ksu.edu>
785-532-7790
Re: red5 start script not work for me vps-1105323-11088
Posted by Seth Galitzer <sg...@ksu.edu>.
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# 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
sgsax@ksu.edu
785-532-7790