You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by "K, Amit (MIND)" <Am...@mind-infotech.com> on 2018/04/02 05:31:34 UTC
RE: Warning!!!PossibleSpam Re: Let's Encrypt and OM and Ubuntu
Another possibility can be: certificate is not imported successfully. You need to verify the certificate by using command line.
From: Alan Johnson [mailto:merchant@argentwolf.org]
Sent: Monday, April 2, 2018 10:50 AM
To: user@openmeetings.apache.org
Subject: Warning!!!PossibleSpam Re: Let's Encrypt and OM and Ubuntu
I did/its there. No joy. I'll wrestle with it more tomorrow. Time for sleep. Thanks for the help.
On 4/2/2018 1:13 AM, Maxim Solodovnik wrote:
My best guess here:
You have created keystore ...
But not truststore ....
please copy keystore to trustore + check path/password in red5.properties
On Mon, Apr 2, 2018 at 12:11 PM, Alan Johnson <me...@argentwolf.org>> wrote:
From the log file:
culprit appears to be here:
Caused by: java.lang.IllegalArgumentException: the trustAnchors parameter must be non-empty
2018-04-02 05:05:45,730 [main] INFO o.a.c.core.AprLifecycleListener - The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/opt/red5402/lib/native]
2018-04-02 05:05:45,741 [main] INFO o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-0.0.0.0-5080"]
2018-04-02 05:05:45,755 [main] INFO o.a.tomcat.util.net<http://o.a.tomcat.util.net>.NioSelectorPool - Using a shared selector for servlet write/read
2018-04-02 05:05:45,773 [main] INFO o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["https-jsse-nio-0.0.0.0-5443"]
2018-04-02 05:05:46,232 [main] ERROR o.a.catalina.util.LifecycleBase - Failed to initialize component [Connector[HTTP/1.1-5443]]
org.apache.catalina.LifecycleException: Protocol handler initialization failed
at org.apache.catalina.connector.Connector.initInternal(Connector.java:935)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:530)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:852)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:173)
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:371)
at org.red5.server.tomcat.TomcatLoader.start(TomcatLoader.java:440)
at org.red5.server.tomcat.TomcatLoader.afterPropertiesSet(TomcatLoader.java:179)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:220)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveNamedBean(DefaultListableBeanFactory.java:1018)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBean(DefaultListableBeanFactory.java:345)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBean(DefaultListableBeanFactory.java:340)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1092)
at org.red5.server.service.ShutdownServer.afterPropertiesSet(ShutdownServer.java:116)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
at org.red5.server.Launcher.launch(Launcher.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.red5.server.Bootstrap.bootStrap(Bootstrap.java:122)
at org.red5.server.Bootstrap.main(Bootstrap.java:50)
Caused by: java.lang.IllegalArgumentException: the trustAnchors parameter must be non-empty
at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:114)
at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.AbstractJsseEndpoint.initialiseSsl(AbstractJsseEndpoint.java:85)
at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.NioEndpoint.bind(NioEndpoint.java:216)
at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.AbstractEndpoint.init(AbstractEndpoint.java:1043)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:540)
at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:74)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:932)
... 40 common frames omitted
Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:157)
at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:130)
at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.jsse.JSSEUtil.getParameters(JSSEUtil.java:389)
at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.jsse.JSSEUtil.getTrustManagers(JSSEUtil.java:313)
at org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:112)
... 46 common frames omitted
2018-04-02 05:05:46,255 [main] INFO o.a.catalina.core.StandardService - Starting service [Tomcat]
2018-04-02 05:05:46,256 [main] INFO o.a.catalina.core.StandardEngine - Starting Servlet Engine: Apache Tomcat/9.0.5
2018-04-02 05:05:46,506 [main] INFO o.a.catalina.startup.ContextConfig - No global web.xml found
2018-04-02 05:05:46,640 [main] INFO o.a.c.c.C.[.[0.0.0.0].[/] - No Spring WebApplicationInitializer types detected on classpath
On 4/2/2018 1:03 AM, Maxim Solodovnik wrote:
Hmmm,
The default HTTPS port is 5443 ...
Have you change it in red5.properties? if not you probably handshaking the wrong service :)
On Mon, Apr 2, 2018 at 12:01 PM, Alan Johnson <me...@argentwolf.org>> wrote:
Ok I commented out the RTMP proxy and it loaded. When I connect to port 443 it tries to do a TLS handshake and times out. There is an error unable to init HTTP connector. I may try to extract a fresh copy of the files and just add the keystore and conf files as necessary.
On 4/2/2018 12:51 AM, Maxim Solodovnik wrote:
Of cause it's up to you
But I would strongly recommend you to perform configuration step-by-step
so change only
jee-container+keystore/truststore
and red5.properties if necessary
red5-core.xml modification is required only for native RTMPS
On Mon, Apr 2, 2018 at 11:47 AM, Alan Johnson <me...@argentwolf.org>> wrote:
Ok I fixed that and a couple others in red5-core.xml.
I think we are making progress. New debug output attached.
Log below:
root@freki:/opt/red5402# cat /opt/red5402/log/red5.log
2018-04-02 04:45:03,877 [main] INFO org.red5.server.Launcher - Red5 Server 1.0.10 (https://github.com/Red5)
2018-04-02 04:45:03,970 [main] INFO o.s.c.s.FileSystemXmlApplicationContext - Refreshing org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@6b26e945: startup date [Mon Apr 02 04:45:03 UTC 2018]; root of context hierarchy
2018-04-02 04:45:04,060 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [red5.xml]
2018-04-02 04:45:04,322 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [jee-container.xml]
2018-04-02 04:45:04,703 [main] INFO o.r.spring.Red5ApplicationContext - setApplicationContext: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@6b26e945: startup date [Mon Apr 02 04:45:03 UTC 2018]; root of context hierarchy
2018-04-02 04:45:04,703 [main] INFO o.r.spring.Red5ApplicationContext - Red5ApplicationContext init
2018-04-02 04:45:04,704 [main] INFO o.r.spring.Red5ApplicationContext - Refreshing ApplicationContext 'red5.common': startup date [Mon Apr 02 04:45:04 UTC 2018]; parent: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@6b26e945
2018-04-02 04:45:04,704 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [red5-common.xml]
2018-04-02 04:45:05,013 [main] INFO org.quartz.impl.StdSchedulerFactory - Using default implementation for ThreadExecutor
2018-04-02 04:45:05,034 [main] INFO o.quartz.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2018-04-02 04:45:05,034 [main] INFO org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.3.0 created.
2018-04-02 04:45:05,035 [main] INFO org.quartz.simpl.RAMJobStore - RAMJobStore initialized.
2018-04-02 04:45:05,036 [main] INFO org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v2.3.0) 'Red5_Scheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 32 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
2018-04-02 04:45:05,036 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler 'Red5_Scheduler' initialized from the specified file : '/opt/red5402/conf/quartz.properties'
2018-04-02 04:45:05,036 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler version: 2.3.0
2018-04-02 04:45:05,036 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED started.
2018-04-02 04:45:05,861 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Registering beans for JMX exposure on startup
2018-04-02 04:45:05,864 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Bean with name 'schedulingService' has been autodetected for JMX exposure
2018-04-02 04:45:05,865 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Bean with name 'clientBroadcastStream' has been autodetected for JMX exposure
2018-04-02 04:45:06,264 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Located MBean 'schedulingService': registering with JMX server as MBean [org.red5.server:name=schedulingService,type=QuartzSchedulingService]
2018-04-02 04:45:06,297 [main] INFO o.r.spring.Red5ApplicationContext - setApplicationContext: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@6b26e945: startup date [Mon Apr 02 04:45:03 UTC 2018]; root of context hierarchy
2018-04-02 04:45:06,298 [main] INFO o.r.spring.Red5ApplicationContext - Red5ApplicationContext init
2018-04-02 04:45:06,298 [main] INFO o.r.spring.Red5ApplicationContext - Refreshing ApplicationContext 'red5.core': startup date [Mon Apr 02 04:45:06 UTC 2018]; parent: ApplicationContext 'red5.common'
2018-04-02 04:45:06,298 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [red5-core.xml]
2018-04-02 04:45:06,576 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP will be bound to [0.0.0.0:1935<http://0.0.0.0:1935>]
2018-04-02 04:45:06,578 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport Settings
Acceptor style: default I/O threads: 16
TCP no-delay: true keep-alive: false
2018-04-02 04:45:06,624 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - Traffic class modification is disabled
2018-04-02 04:45:06,624 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - Send buffer size: 65536 recv buffer size: 65536 so linger: -1 traffic class: 0
2018-04-02 04:45:07,329 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP will be bound to [0.0.0.0:8443<http://0.0.0.0:8443>]
2018-04-02 04:45:07,329 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport Settings
Acceptor style: default I/O threads: 16
TCP no-delay: true keep-alive: false
2018-04-02 04:45:07,332 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - Send buffer size: 65536 recv buffer size: 65536 so linger: -1 traffic class: 24
2018-04-02 04:45:07,335 [main] WARN o.r.spring.Red5ApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'rtmpProxyTransport' defined in class path resource [red5-core.xml]: Cannot resolve reference to bean 'debugProxyIoHandler' while setting bean property 'ioHandler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'debugProxyIoHandler' defined in class path resource [red5-core.xml]: Cannot resolve reference to bean 'rtmpCodecFactory' while setting bean property 'codecFactory'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'rtmpCodecFactory' available
2018-04-02 04:45:07,335 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport stop
2018-04-02 04:45:07,339 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport stop
2018-04-02 04:45:07,342 [main] WARN o.s.c.s.FileSystemXmlApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'red5.core' defined in class path resource [red5.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'rtmpProxyTransport' defined in class path resource [red5-core.xml]: Cannot resolve reference to bean 'debugProxyIoHandler' while setting bean property 'ioHandler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'debugProxyIoHandler' defined in class path resource [red5-core.xml]: Cannot resolve reference to bean 'rtmpCodecFactory' while setting bean property 'codecFactory'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'rtmpCodecFactory' available
2018-04-02 04:45:07,342 [main] INFO o.r.spring.Red5ApplicationContext - Closing ApplicationContext 'red5.common': startup date [Mon Apr 02 04:45:04 UTC 2018]; parent: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@6b26e945
2018-04-02 04:45:07,342 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans on shutdown
2018-04-02 04:45:07,342 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans
2018-04-02 04:45:07,343 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED shutting down.
2018-04-02 04:45:07,345 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED paused.
2018-04-02 04:45:07,346 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED shutdown complete.
root@freki:/opt/red5402#
On 4/2/2018 12:37 AM, Maxim Solodovnik wrote:
It should be clear:
Line 67 in XML document from class path resource [jee-container.xml] is invalid;
Please do exactly what I wrote in my previous email
On Mon, Apr 2, 2018 at 11:35 AM, Alan Johnson <me...@argentwolf.org>> wrote:
Debug output attached.
On 4/2/2018 12:31 AM, Maxim Solodovnik wrote:
Can you:
1) stop OM
2) clean log folder
3) run red5-debug.sh
check console?
On Mon, Apr 2, 2018 at 11:28 AM, Alan Johnson <me...@argentwolf.org>> wrote:
I fixed that and now It's not working under http or https. under http it redirects to a page not found. HTTPS is no connection.
Log file:
root@freki:~# cat /opt/red5402/log/red5.log
2018-04-02 04:25:25,519 [main] INFO org.red5.server.Launcher - Red5 Server 1.0.10 (https://github.com/Red5)
2018-04-02 04:25:25,615 [main] INFO o.s.c.s.FileSystemXmlApplicationContext - Refreshing org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@548b7f67: startup date [Mon Apr 02 04:25:25 UTC 2018]; root of context hierarchy
2018-04-02 04:25:25,680 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [red5.xml]
2018-04-02 04:25:25,901 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [jee-container.xml]
On 4/2/2018 12:20 AM, Maxim Solodovnik wrote:
jee-container looks mailformed: extra "-->" at the end
On Mon, Apr 2, 2018 at 11:18 AM, Alan Johnson <me...@argentwolf.org>> wrote:
Maxim,
So, I went back to my original files. Here are the jee-container and red5.properties.
If you could take a look at them I would appreciate it.
Alan
On 4/2/2018 12:09 AM, Maxim Solodovnik wrote:
According to your log:
XmlBeanDefinitionStoreException: Line 250 in XML document from class path resource [red5-core.xml] is invalid
The only files you need to change are:
1) jee-container.xml (required)
2) keystore/trustore (required)
3) red5.propertes (optional)
Modify this https://github.com/apache/openmeetings/blob/4.0.x/openmeetings-server/src/main/assembly/conf/jee-container.xml#L32
line to be
<!-- Tomcat without SSL enabled
Modify this https://github.com/apache/openmeetings/blob/4.0.x/openmeetings-server/src/main/assembly/conf/jee-container.xml#L70
line to be
</bean> -->
Delete this line https://github.com/apache/openmeetings/blob/4.0.x/openmeetings-server/src/main/assembly/conf/jee-container.xml#L73
line to be
Delete this line https://github.com/apache/openmeetings/blob/4.0.x/openmeetings-server/src/main/assembly/conf/jee-container.xml#L132
Some reading about XML commenting: https://stackoverflow.com/questions/2757396/how-do-i-comment-out-a-block-of-tags-in-xml
On Mon, Apr 2, 2018 at 11:00 AM, Alan Johnson <me...@argentwolf.org>> wrote:
Aaron,
Thanks for the file. It did not seem to fix the issue, it still started but it did populate the log file with a bunch of stuff:
root@freki:/opt/red5402/conf# cat /opt/red5402/log/red5.log
2018-04-02 03:52:04,799 [main] INFO org.red5.server.Launcher - Red5 Server 1.0.10 (https://github.com/Red5)
2018-04-02 03:52:04,873 [main] INFO o.s.c.s.FileSystemXmlApplicationContext - Refreshing org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@548b7f67: startup date [Mon Apr 02 03:52:04 UTC 2018]; root of context hierarchy
2018-04-02 03:52:04,938 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [red5.xml]
2018-04-02 03:52:05,191 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [jee-container.xml]
2018-04-02 03:52:05,539 [main] INFO o.r.spring.Red5ApplicationContext - setApplicationContext: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@548b7f67: startup date [Mon Apr 02 03:52:04 UTC 2018]; root of context hierarchy
2018-04-02 03:52:05,539 [main] INFO o.r.spring.Red5ApplicationContext - Red5ApplicationContext init
2018-04-02 03:52:05,544 [main] INFO o.r.spring.Red5ApplicationContext - Refreshing ApplicationContext 'red5.common': startup date [Mon Apr 02 03:52:05 UTC 2018]; parent: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@548b7f67
2018-04-02 03:52:05,545 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [red5-common.xml]
2018-04-02 03:52:05,815 [main] INFO org.quartz.impl.StdSchedulerFactory - Using default implementation for ThreadExecutor
2018-04-02 03:52:05,839 [main] INFO o.quartz.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2018-04-02 03:52:05,839 [main] INFO org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.3.0 created.
2018-04-02 03:52:05,840 [main] INFO org.quartz.simpl.RAMJobStore - RAMJobStore initialized.
2018-04-02 03:52:05,841 [main] INFO org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v2.3.0) 'Red5_Scheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 32 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
2018-04-02 03:52:05,841 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler 'Red5_Scheduler' initialized from the specified file : '/opt/red5402/conf/quartz.properties'
2018-04-02 03:52:05,841 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler version: 2.3.0
2018-04-02 03:52:05,841 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED started.
2018-04-02 03:52:06,528 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Registering beans for JMX exposure on startup
2018-04-02 03:52:06,534 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Bean with name 'schedulingService' has been autodetected for JMX exposure
2018-04-02 03:52:06,539 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Bean with name 'clientBroadcastStream' has been autodetected for JMX exposure
2018-04-02 03:52:06,928 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Located MBean 'schedulingService': registering with JMX server as MBean [org.red5.server:name=schedulingService,type=QuartzSchedulingService]
2018-04-02 03:52:06,960 [main] INFO o.r.spring.Red5ApplicationContext - setApplicationContext: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@548b7f67: startup date [Mon Apr 02 03:52:04 UTC 2018]; root of context hierarchy
2018-04-02 03:52:06,960 [main] INFO o.r.spring.Red5ApplicationContext - Red5ApplicationContext init
2018-04-02 03:52:06,960 [main] INFO o.r.spring.Red5ApplicationContext - Refreshing ApplicationContext 'red5.core': startup date [Mon Apr 02 03:52:06 UTC 2018]; parent: ApplicationContext 'red5.common'
2018-04-02 03:52:06,961 [main] INFO o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [red5-core.xml]
2018-04-02 03:52:07,081 [main] WARN o.s.c.s.FileSystemXmlApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'red5.core' defined in class path resource [red5.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 250 in XML document from class path resource [red5-core.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 250; columnNumber: 9; cvc-complex-type.2.3: Element 'beans' cannot have character [children], because the type's content type is element-only.
2018-04-02 03:52:07,082 [main] INFO o.r.spring.Red5ApplicationContext - Closing ApplicationContext 'red5.common': startup date [Mon Apr 02 03:52:05 UTC 2018]; parent: org.springframework.context.su<http://org.springframework.context.su>pport.FileSystemXmlApplicationContext@548b7f67
2018-04-02 03:52:07,085 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans on shutdown
2018-04-02 03:52:07,085 [main] INFO o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans
2018-04-02 03:52:07,088 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED shutting down.
2018-04-02 03:52:07,088 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED paused.
2018-04-02 03:52:07,091 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$_NON_CLUSTERED shutdown complete.
On 3/30/2018 12:30 PM, Aaron Hepp wrote:
attached is my working XML file. I would suggest once you get the all the files configured and working:
red5-core.xml
red5.properties
jee-container.xml
That you copy them into a new folder inside /opt (mine is /opt/files) as this will save you from having to redo all the changes each time you implement a new build.
On 3/30/2018 12:16 PM, merchant@argentwolf.org<ma...@argentwolf.org> wrote:
I had added a space and it turned it all yellow in bash.
Sent from my android device.
-----Original Message-----
From: Aaron Hepp <aa...@gmail.com>
To: user@openmeetings.apache.org<ma...@openmeetings.apache.org>, Alan Johnson <me...@argentwolf.org>, Maxim Solodovnik <so...@gmail.com>
Sent: Fri, 30 Mar 2018 12:12
Subject: Re: Let's Encrypt and OM and Ubuntu
Looks like you did not comment out the <!-- Tomcat without SSL enabled
-- > section.
That has to be commented out to force SSL.
remove the --> from that line and add it right above this line
<!-- Tomcat with SSL enabled -->
That will comment out the entire "non-SSL" portion.
On 3/30/2018 12:02 PM, Alan Johnson wrote:
> I have done both of those steps.
>
> I created the keystore via the email chain you sent the link to. That
> seemed to work with no errors.
>
> I had previously enabled/disabled tomcat.
>
> I tried an experiment and changed the comment on the file and it
> seemed to like it better (included below) and seems to have fixed the
> errors in the log file, but it isn't answering on any of the expected
> ports (5443/8443/443<tel:8443443>).
>
>
> From red5.properties<http://red5.properties>:
>
> # Socket policy
> policy.host<http://policy.host>=0.0.0.0
> policy.port=843
>
> # HTTP
> http.host<http://http.host>=0.0.0.0
> http.port=5080
> https.port=443
> http.URIEncoding=UTF-8
> http.max_headers_size=8192
> http.max_keep_alive_requests=-1
> http.max_threads=20
> http.acceptor_thread_count=10
> http.processor_cache=20
>
> # RTMPS
> rtmps.host<http://rtmps.host>=0.0.0.0
> rtmps.port=8443
>
>
> root@freki:/opt/red5402/log# ufw status
> Status: active
>
> To Action From
> -- ------ ----
> OpenSSH ALLOW Anywhere
> 5080 ALLOW Anywhere
> 1935 ALLOW Anywhere
> 80 ALLOW Anywhere
> 5443 ALLOW Anywhere
> 8443 ALLOW Anywhere
> 443 ALLOW Anywhere
> OpenSSH (v6) ALLOW Anywhere (v6)
> 5080 (v6) ALLOW Anywhere (v6)
> 1935 (v6) ALLOW Anywhere (v6)
> 80 (v6) ALLOW Anywhere (v6)
> 5443 (v6) ALLOW Anywhere (v6)
> 8443 (v6) ALLOW Anywhere (v6)
> 443 (v6) ALLOW Anywhere (v6)
>
> This is what is in the red5.log file, if it helps:
>
> root@freki:/opt/red5402/log# cat red5.log
> 2018-03-30 01:20:35,450 [main] INFO org.red5.server.Launcher - Red5
> Server 1.0.10 (https://github.com/Red5)
> 2018-03-30 01:20:35,570 [main] INFO
> o.s.c.s.FileSystemXmlApplicationContext - Refreshing
> org.springframework.context.support<http://org.springframework.context.support>.FileSystemXmlApplicationContext@548b7f67:
> startup date [Fri Mar 30 01:20:35 UTC 2018]; root of context hierarchy
> 2018-03-30 01:20:35,687 [main] INFO
> o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions
> from class path resource [red5.xml]
> 2018-03-30 01:20:36,074 [main] INFO
> o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions
> from class path resource [jee-container.xml]
> 2018-03-30 01:21:36,609 [http-nio-0.0.0.0-5080-exec-4] INFO
> o.a.coyote.http11.Http11Processor - Error parsing HTTP request header
> Note: further occurrences of HTTP request parsing errors will be
> logged at DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method
> name. HTTP method names must be tokens
> at
> org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:410<http://Http11InputBuffer.java:410>)
> at
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:291<http://Http11Processor.java:291>)
> at
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66<http://AbstractProcessorLight.java:66>)
> at
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:754<http://AbstractProtocol.java:754>)
> at
> org.apache.tomcat.util.net<http://org.apache.tomcat.util.net>.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1376<http://NioEndpoint.java:1376>)
> at
> org.apache.tomcat.util.net.SocketProcessorBase.run<http://org.apache.tomcat.util.net.SocketProcessorBase.run>(SocketProcessorBase.java:49<http://SocketProcessorBase.java:49>)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149<http://ThreadPoolExecutor.java:1149>)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run<http://Worker.run>(ThreadPoolExecutor.java:624<http://ThreadPoolExecutor.java:624>)
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run<http://WrappingRunnable.run>(TaskThread.java:61<http://TaskThread.java:61>)
> at java.lang.Thread.run<http://java.lang.Thread.run>(Thread.java:748<http://Thread.java:748>)
>
> Full Jee-container.xml if it helps:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!--
> Licensed to the Apache Software Foundation (ASF) under one or more
> contributor license agreements. See the NOTICE file distributed with
> this work for additional information regarding copyright ownership.
> The ASF licenses this file to You under the Apache License, Version
> 2.0
> (the "License"); you may not use this file except in compliance with
> the License. You may obtain a copy of the License at
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing, software
> distributed under the License is distributed on an "AS IS" BASIS,
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> See the License for the specific language governing permissions and
> limitations under the License.
> -->
> <beans xmlns="http://www.springframework.org/schema/beans"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:lang="http://www.springframework.org/schema/lang"
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/lang
> http://www.springframework.org/schema/lang/spring-lang.xsd
> ">
> <!--
> The tomcat connectors may be blocking or non-blocking. Select
> between either option via the protocol property.
> Blocking I/O:
> <property name="protocol"
> value="org.apache.coyote.http11.Http11Protocol" />
> Non-blocking I/O:
> <property name="protocol"
> value="org.apache.coyote.http11.Http11NioProtocol" />
> -->
> <!-- Tomcat without SSL enabled -- >
> <bean id="tomcat.server"
> class="org.red5.server.tomcat.TomcatLoader"
> depends-on="context.loader" lazy-init="true">
> <property name="webappFolder"
> value="${red5.root}/webapps" />
> <property name="connectors">
> <list>
> <bean name="httpConnector"
> class="org.red5.server.tomcat.TomcatConnector">
> <property name="protocol"
> value="org.apache.coyote.http11.Http11NioProtocol" />
> <property name="address"
> value="${http.host<http://http.host>}:${http.port}" />
> <property name="redirectPort"
> value="${https.port}" />
> <property
> name="connectionProperties">
> <map>
> <entry
> key="maxKeepAliveRequests" value="${http.max_keep_alive_requests}"/>
> <entry
> key="keepAliveTimout" value="-1"/>
> </map>
> </property>
> </bean>
> </list>
> </property>
> <property name="baseHost">
> <bean
> class="org.apache.catalina.core.StandardHost">
> <property name="name"
> value="${http.host<http://http.host>}" />
> </bean>
> </property>
> <property name="valves">
> <list>
> <bean id="valve.access"
> class="org.apache.catalina.valves.AccessLogValve">
> <property name="directory"
> value="log" />
> <property name="prefix"
> value="${http.host<http://http.host>}_access." />
> <property name="suffix"
> value=".log" />
> <property name="pattern"
> value="common" />
> <property name="rotatable"
> value="true" />
> </bean>
> <bean id="valve.error"
> class="org.apache.catalina.valves.ErrorReportValve">
> <property name="showReport"
> value="false" />
> <property
> name="showServerInfo" value="false" />
> </bean>
> </list>
> </property>
> </bean>
>
> <!-- Tomcat with SSL enabled -->
>
> <bean id="tomcat.server"
> class="org.red5.server.tomcat.TomcatLoader"
> depends-on="context.loader" lazy-init="true">
> <property name="webappFolder"
> value="${red5.root}/webapps" />
> <property name="connectors">
> <list>
> <bean name="httpConnector"
> class="org.red5.server.tomcat.TomcatConnector">
> <property name="protocol"
> value="org.apache.coyote.http11.Http11NioProtocol" />
> <property name="address"
> value="${http.host<http://http.host>}:${http.port}" />
> <property name="redirectPort"
> value="${https.port}" />
> </bean>
> <bean name="httpsConnector"
> class="org.red5.server.tomcat.TomcatConnector">
> <property name="secure"
> value="true" />
> <property name="protocol"
> value="org.apache.coyote.http11.Http11NioProtocol" />
> <property name="address"
> value="${http.host<http://http.host>}:${https.port}" />
> <property name="redirectPort"
> value="${http.port}" />
> <property
> name="connectionProperties">
> <map>
> <entry
> key="port" value="${https.port}" />
> <entry
> key="redirectPort" value="${http.port}" />
> <entry
> key="SSLEnabled" value="true" />
> <entry
> key="sslProtocol" value="TLS" />
> <entry
> key="keystoreFile" value="${rtmps.keystorefile}" />
> <entry
> key="keystorePass" value="${rtmps.keystorepass}" />
> <entry
> key="truststoreFile" value="${rtmps.truststorefile}" />
> <entry
> key="truststorePass" value="${rtmps.truststorepass}" />
> <entry
> key="clientAuth" value="false" />
> <entry
> key="allowUnsafeLegacyRenegotiation" value="true" />
> <entry
> key="maxKeepAliveRequests" value="${http.max_keep_alive_requests}"/>
> <entry
> key="keepAliveTimout" value="-1"/>
> <entry
> key="useExecutor" value="true"/>
> <entry
> key="maxThreads" value="${http.max_threads}"/>
> <entry
> key="acceptorThreadCount" value="${http.acceptor_thread_count}"/>
> <entry
> key="processorCache" value="${http.processor_cache}"/>
> </map>
> </property>
> </bean>
> </list>
> </property>
> <property name="baseHost">
> <bean
> class="org.apache.catalina.core.StandardHost">
> <property name="name"
> value="${http.host<http://http.host>}" />
> </bean>
> </property>
> <property name="valves">
> <list>
> <bean id="valve.access"
> class="org.apache.catalina.valves.AccessLogValve">
> <property name="directory"
> value="log" />
> <property name="prefix"
> value="${http.host<http://http.host>}_access." />
> <property name="suffix"
> value=".log" />
> <property name="pattern"
> value="common" />
> <property name="rotatable"
> value="true" />
> </bean>
> <bean id="valve.error"
> class="org.apache.catalina.valves.ErrorReportValve">
> <property name="showReport"
> value="false" />
> <property
> name="showServerInfo" value="false" />
> </bean>
> </list>
> </property>
> </bean>
> -->
> </beans>
>
>
> On 3/30/2018 2:37 AM, Maxim Solodovnik wrote:
>> Hello Alan,
>>
>> To eneble HTTPS for OM you need to do 2 things:
>>
>> 1) create valid keystore/truststore (ensure filename/path is correctly
>> defined in red5.properties<http://red5.properties>)
>> 2) Edit red5/conf/jee-container.xml file:
>> Comment Tomcat without SSL enabled section
>> UNComment Tomcat with SSL enabled section
>>
>> On Fri, Mar 30, 2018 at 5:30 AM, Alan Johnson
>> <me...@argentwolf.org>> wrote:
>>> So I tried using the steps in the email, and they successfully
>>> created the
>>> keystore.
>>>
>>> However the steps to enable HTTPS web interface appear to be
>>> incorrect/have
>>> changed.
>>>
>>> Edit red5/webapps/openmeetings/public/config.xml and set
>>> <protocol>https</protocol>
>>> Edit red5/webapps/openmeetings/public/config.xml and set
>>> red5httpport to
>>> https port
>>>
>>> These files (Config.xml) are missing from the directory.
>>>
>>> root@freki:/opt/red5402/webapps/openmeetings/public# ls -al
>>> total 968
>>> drwxr-xr-x 3 nobody root 4096 Mar 29 22:29 .
>>> drwxr-xr-x 15 nobody root 4096 Mar 28 21:08 ..
>>> -rw-rw-r-- 1 nobody root 4597 Feb 1 23:17 chat_message.mp3
>>> drwxrwxr-x 2 nobody root 4096 Feb 24 23:00 cliparts
>>> -rw-rw-r-- 1 nobody root 11294 Feb 1 23:17 favicon.ico
>>> -rw-rw-r-- 1 nobody root 572587 Feb 24 23:00 main.swf
>>> -rw-rw-r-- 1 nobody root 384036 Feb 24 23:01 networktest.swf
>>>
>>> Please advise.
>>>
>>>
>>>
>>> On 3/29/2018 2:52 AM, Maxim Solodovnik wrote:
>>>
>>> What preventing you from using this script?
>>>
>>> On Thu, Mar 29, 2018 at 1:41 PM, Anis Aliev <al...@gmail.com>>
>>> wrote:
>>>
>>> Guys from bigbluebutton aleady developed a script for installing
>>> with lE
>>>
>>> чт, 29 марта 2018 г., 9:32 Maxim Solodovnik <so...@gmail.com>>:
>>>
>>> great :)
>>>
>>> ps please CC user@ list :)
>>>
>>>
>>> On Thu, Mar 29, 2018 at 11:18 AM, Alan Johnson
>>> <me...@argentwolf.org>>
>>> wrote:
>>>
>>> Thank you for pointing it out. I will try the steps listed in the 18
>>> Oct
>>> 2017 email tomorrow.
>>>
>>> I might suggest that given the number of other emails asking about
>>> it to
>>> update the guide and / or build in certbot functionality to simplify
>>> the
>>> configuration. If I had my preference, the installer would offer LE
>>> https as
>>> a default option for installation.
>>>
>>>
>>> On 3/29/2018 12:13 AM, Maxim Solodovnik wrote:
>>>
>>> This topic was discussed many times:
>>>
>>>
>>> https://openmeetings.markmail.org/search/?q=letsencrypt#query:letsencrypt+page:1+mid:ik4qdhdychl364bp+state:results
>>>
>>>
>>> What steps are not work for you?
>>>
>>> On Thu, Mar 29, 2018 at 10:14 AM, Anis Aliev <al...@gmail.com>>
>>> wrote:
>>>
>>> This is why I am asking community to arrange tutorial for SSL based on
>>> LE.
>>>
>>> FYI
>>>
>>> 2018-03-29 7:22 GMT+05:00 Alan Johnson <me...@argentwolf.org>>:
>>>
>>> I saw a recent thread regarding windows 10 and Let's Encrypt. Has
>>> anyone
>>> had any success with Ubuntu and LE?
>>>
>>> I was using this guide
>>>
>>>
>>> (https://openmeetings.apache.org/RTMPSAndHTTPS.html#SSL_for_the_web_interface)
>>>
>>> after getting OM up and running, but I had no luck figuring out how
>>> to
>>> convert the LE certs to appropriate formats for OM?
>>>
>>> Thanks,
>>>
>>> Alan
>>>
>>>
>>> --
>>>
>>> IT Manager,e-learning specialist
>>> Skype:aliev_anis
>>> www.facebook.com/anis.aliev<http://www.facebook.com/anis.aliev>
>>> Тел:989010012
>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>>
>>
>>
>
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
________________________________
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus/trojan/worms/malicious code transmitted by this email. www.motherson.com