You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Robert Steinmetz AIA <ro...@steinmetznet.com> on 2015/03/06 22:44:58 UTC
Re: Installation issues - Progress!
Thank you for your help.
I think a lot of the information on the web is for older versions
The web page on Installation still refers to JRE 6
http://openmeetings.apache.org/installation.html
I now have red5 running and am getting some information in the logs.
The init script seems to be working to start/stop and restart red5.
But I think had/have some kind of problem with SSL. When I access by
http://FQDN:5080/openmeetings I get a response. When I access by
https://IP address:5080/openmeetings I get an SSL error.
> SSL received a record that exceeded the maximum permissible length.
> (Error code: ssl_error_rx_record_too_long)
Maxim Solodovnik wrote:
> Hello Robert,
>
> Java7 is required to run OM 3.0.4+ (I can fix the documentation if you
> can point me which page still referring Java6)
> According to the latest observations OM works as expected with both
> OpenJDK and Sun Java.
>
> To eliminate all configuration issues I usually start OM manually,
> make it working, then switch to autostart script
>
> "Address already in use" usually mean OM was already started
> No new log entries after running auto-start script might be caused by
> file permission issue: auto-start script working as "nobody:nogroup"
> user, you need to recursively change ownership of OM folder to use it
>
> I would recommend you
> sudo killall java
> ps -ef|grep java (to ensure no-one still working)
> manually run OM, ensure everything is OK
> change ownership
> auto-start
> have fun :)))
>
>
>
> On Fri, Mar 6, 2015 at 1:54 AM, Robert Steinmetz AIA
> <rob@steinmetznet.com <ma...@steinmetznet.com>> wrote:
>
> Thank you, I'm poking around in the dark here.
>
> Apparently it's not starting, but only seems like it is.
>
> # /etc/init.d/red5 start
> Starting Red5 flash streaming server: red5
>
>
> This should run red5.sh but apparently it's not.
>
>
> There are no entries in the logs in /opt/red5/log
>
> Looking at the /etc/init.d/red5 file it seems everything ought to
> be in place.
>
>
> Doing a manual start the key error seems to be:
>
> Bootstrap exception: org/red5/server/Launcher : Unsupported
> major.minor version 51.0
> java.lang.UnsupportedClassVersionError:
> org/red5/server/Launcher : Unsupported major.minor version 51.0
>
> This seems to mean I either don't have the correct version of JAVA
> or the config is pointing to the wrong one.
> red5.sh points to /opt/local/java/sun6
>
> I know the openmeetings documentation say to use sun Java 6 not
> openJDK, however several newer installation guides indicate using
> openJDK.
> I'm not sure if the use of official Java is necessary, even if it
> not supported.
> what Java version will actually work under Ubuntu 12.04 (soon to
> be 14.04.)
>
> I poked around and found that open JDK 6 was still installed and
> apparently the default. I can now start red5 without error.
>
> # ps -ef|grep red5
> root 10284 21984 0 14:45 pts/7 00:00:00 grep red5
> nobody 23464 1 0 Mar04 ? 00:03:42 /usr/bin/java
> -Dred5.root=/opt/red5
> -Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
> -Dcatalina.useNaming=true -Djava.security.debug=failure
> -Xverify:none -XX:+TieredCompilation -XX:+UseBiasedLocking
> -XX:InitialCodeCacheSize=8m -XX:ReservedCodeCacheSize=32m
> -Dorg.terracotta.quartz.skipUpdateCheck=true -Dpython.home=lib
> -cp /opt/red5/red5-service.jar:/opt/red5/conf:
> org.red5.server.Bootstrap
>
> The logs are now getting info in them, but I still can't connect.
> The errors in the logs are:
>
> [main] ERROR o.a.coyote.http11.Http11NioProtocol - Failed to
> initialize end point associated with ProtocolHandler
> ["http-nio-0.0.0.0-5080"]
> java.net.BindException: Address already in use
>
> [main] ERROR o.a.catalina.core.StandardService - Failed to
> initialize connector
> [Connector[org.apache.coyote.http11.Http11NioProtocol-5080]]
>
>
>
> Maxim Solodovnik wrote:
>
> Actually OM is standalone web server (based on Tomcat)
> in case you run it (ps -ef|grep red5) it should be available
> on port 5080 (by default, netstat -an|grep 5080)
> It has it's own logs in $RED5_HOME/log, can you check these logs?
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
--
Robert Steinmetz AIA
Principal
Steinmetz & Associates
New Orleans & Atlanta
Re: Installation issues - Progress!
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks for the reference!
I'll correct the documentation!
According to HTTPS: it need to be additionally configured:
http://openmeetings.apache.org/RTMPSAndHTTPS.html
On Sat, Mar 7, 2015 at 3:44 AM, Robert Steinmetz AIA <ro...@steinmetznet.com>
wrote:
> Thank you for your help.
>
> I think a lot of the information on the web is for older versions
>
> The web page on Installation still refers to JRE 6
> http://openmeetings.apache.org/installation.html
>
> I now have red5 running and am getting some information in the logs. The
> init script seems to be working to start/stop and restart red5.
> But I think had/have some kind of problem with SSL. When I access by
> http://FQDN:5080/openmeetings I get a response. When I access by
> https://IP address:5080/openmeetings I get an SSL error.
>
> SSL received a record that exceeded the maximum permissible length. (Error
> code: ssl_error_rx_record_too_long)
>
>
>
> Maxim Solodovnik wrote:
>
> Hello Robert,
>
> Java7 is required to run OM 3.0.4+ (I can fix the documentation if you
> can point me which page still referring Java6)
> According to the latest observations OM works as expected with both
> OpenJDK and Sun Java.
>
> To eliminate all configuration issues I usually start OM manually, make
> it working, then switch to autostart script
>
> " Address already in use" usually mean OM was already started
> No new log entries after running auto-start script might be caused by file
> permission issue: auto-start script working as "nobody:nogroup" user, you
> need to recursively change ownership of OM folder to use it
>
> I would recommend you
> sudo killall java
> ps -ef|grep java (to ensure no-one still working)
> manually run OM, ensure everything is OK
> change ownership
> auto-start
> have fun :)))
>
>
>
>
> On Fri, Mar 6, 2015 at 1:54 AM, Robert Steinmetz AIA <rob@steinmetznet.com
> > wrote:
>
>> Thank you, I'm poking around in the dark here.
>>
>> Apparently it's not starting, but only seems like it is.
>>
>>> # /etc/init.d/red5 start
>>> Starting Red5 flash streaming server: red5
>>>
>>
>> This should run red5.sh but apparently it's not.
>>
>>
>> There are no entries in the logs in /opt/red5/log
>>
>> Looking at the /etc/init.d/red5 file it seems everything ought to be in
>> place.
>>
>>
>> Doing a manual start the key error seems to be:
>>
>> Bootstrap exception: org/red5/server/Launcher : Unsupported major.minor
>>> version 51.0
>>> java.lang.UnsupportedClassVersionError: org/red5/server/Launcher :
>>> Unsupported major.minor version 51.0
>>>
>> This seems to mean I either don't have the correct version of JAVA or the
>> config is pointing to the wrong one.
>> red5.sh points to /opt/local/java/sun6
>>
>> I know the openmeetings documentation say to use sun Java 6 not openJDK,
>> however several newer installation guides indicate using openJDK.
>> I'm not sure if the use of official Java is necessary, even if it not
>> supported.
>> what Java version will actually work under Ubuntu 12.04 (soon to be
>> 14.04.)
>>
>> I poked around and found that open JDK 6 was still installed and
>> apparently the default. I can now start red5 without error.
>>
>> # ps -ef|grep red5
>>> root 10284 21984 0 14:45 pts/7 00:00:00 grep red5
>>> nobody 23464 1 0 Mar04 ? 00:03:42 /usr/bin/java
>>> -Dred5.root=/opt/red5
>>> -Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector
>>> -Dcatalina.useNaming=true -Djava.security.debug=failure -Xverify:none
>>> -XX:+TieredCompilation -XX:+UseBiasedLocking -XX:InitialCodeCacheSize=8m
>>> -XX:ReservedCodeCacheSize=32m -Dorg.terracotta.quartz.skipUpdateCheck=true
>>> -Dpython.home=lib -cp /opt/red5/red5-service.jar:/opt/red5/conf:
>>> org.red5.server.Bootstrap
>>>
>> The logs are now getting info in them, but I still can't connect. The
>> errors in the logs are:
>>
>> [main] ERROR o.a.coyote.http11.Http11NioProtocol - Failed to initialize
>> end point associated with ProtocolHandler ["http-nio-0.0.0.0-5080"]
>> java.net.BindException: Address already in use
>>
>> [main] ERROR o.a.catalina.core.StandardService - Failed to initialize
>> connector [Connector[org.apache.coyote.http11.Http11NioProtocol-5080]]
>>
>>
>>
>> Maxim Solodovnik wrote:
>>
>>> Actually OM is standalone web server (based on Tomcat)
>>> in case you run it (ps -ef|grep red5) it should be available on port
>>> 5080 (by default, netstat -an|grep 5080)
>>> It has it's own logs in $RED5_HOME/log, can you check these logs?
>>>
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
> --
>
> Robert Steinmetz AIA
> Principal
> Steinmetz & Associates
>
> New Orleans & Atlanta
>
--
WBR
Maxim aka solomax