Hello Maxim,

below is the log-file (red5.log) content, that i received when i try to
start the Server after configuration for RTMPS and HTTPS.
The Server starts and goes down 1 second later...
Could you please help me, to find the mistake.


2015-02-04 15:40:44,792 [main] INFO  org.red5.server.Launcher - Red5 Server
1.0.3-SNAPSHOT (http://code.google.com/p/red5/)
2015-02-04 15:40:44,881 [main] INFO
o.s.c.s.FileSystemXmlApplicationContext - Refreshing
org.springframework.context.support.FileSystemXmlApplicationContext@3cf9edf3:
startup date [Wed Feb 04 15:40:44 CET 2015]; root of context hierarc$
2015-02-04 15:40:44,905 [main] INFO  o.s.b.f.xml.XmlBeanDefinitionReader -
Loading XML bean definitions from class path resource [red5.xml]
2015-02-04 15:40:45,062 [main] INFO  o.s.b.f.xml.XmlBeanDefinitionReader -
Loading XML bean definitions from class path resource [jee-container.xml]
2015-02-04 15:40:45,150 [main] INFO
o.s.b.f.c.PropertyPlaceholderConfigurer - Loading properties file from
class path resource [red5.properties]
2015-02-04 15:40:45,175 [main] INFO  o.r.spring.Red5ApplicationContext -
setApplicationContext:
org.springframework.context.support.FileSystemXmlApplicationContext@3cf9edf3:
startup date [Wed Feb 04 15:40:44 CET 2015]; root of context h$
2015-02-04 15:40:45,176 [main] INFO  o.r.spring.Red5ApplicationContext -
Red5ApplicationContext init
2015-02-04 15:40:45,177 [main] INFO  o.r.spring.Red5ApplicationContext -
Refreshing ApplicationContext 'red5.common': startup date [Wed Feb 04
15:40:45 CET 2015]; parent:
org.springframework.context.support.FileSystemXmlApplicationConte$
2015-02-04 15:40:45,178 [main] INFO  o.s.b.f.xml.XmlBeanDefinitionReader -
Loading XML bean definitions from class path resource [red5-common.xml]
2015-02-04 15:40:45,271 [main] INFO
o.s.b.f.c.PropertyPlaceholderConfigurer - Loading properties file from
class path resource [red5.properties]
2015-02-04 15:40:45,306 [main] INFO  org.quartz.impl.StdSchedulerFactory -
Using default implementation for ThreadExecutor
2015-02-04 15:40:45,329 [main] INFO  o.quartz.core.SchedulerSignalerImpl -
Initialized Scheduler Signaller of type: class
org.quartz.core.SchedulerSignalerImpl
2015-02-04 15:40:45,329 [main] INFO  org.quartz.core.QuartzScheduler -
Quartz Scheduler v.2.1.7 created.
2015-02-04 15:40:45,330 [main] INFO  org.quartz.simpl.RAMJobStore -
RAMJobStore initialized.
2015-02-04 15:40:45,330 [main] INFO  org.quartz.core.QuartzScheduler -
Scheduler meta-data: Quartz Scheduler (v2.1.7) '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.

2015-02-04 15:40:45,331 [main] INFO  org.quartz.impl.StdSchedulerFactory -
Quartz scheduler 'Red5_Scheduler' initialized from the specified file :
'/usr/lib/red5/conf/quartz.properties'
2015-02-04 15:40:45,331 [main] INFO  org.quartz.impl.StdSchedulerFactory -
Quartz scheduler version: 2.1.7
2015-02-04 15:40:45,331 [main] INFO  org.quartz.core.QuartzScheduler -
Scheduler Red5_Scheduler_$_NON_CLUSTERED started.
2015-02-04 15:40:45,342 [main] INFO  o.s.r.rmi.RmiRegistryFactoryBean -
Creating new RMI registry
2015-02-04 15:40:45,534 [main] INFO  o.s.j.s.ConnectorServerFactoryBean -
JMX connector server started:
javax.management.remote.rmi.RMIConnectorServer@7fa1dd69
2015-02-04 15:40:45,546 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter -
Registering beans for JMX exposure on startup
2015-02-04 15:40:45,547 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter -
Bean with name
'org.springframework.jmx.support.ConnectorServerFactoryBean#0' has been
autodetected for JMX exposure
2015-02-04 15:40:45,551 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter -
Bean with name 'schedulingService' has been autodetected for JMX exposure
2015-02-04 15:40:45,572 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter -
Bean with name 'clientBroadcastStream' has been autodetected for JMX
exposure
2015-02-04 15:40:45,601 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter -
Located MBean
'org.springframework.jmx.support.ConnectorServerFactoryBean#0': registering
with JMX server as MBean [org.red5.server:name=org.springframework.jmx.su$
2015-02-04 15:40:45,603 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter -
Located MBean 'schedulingService': registering with JMX server as MBean
[org.red5.server:name=schedulingService,type=QuartzSchedulingService]
2015-02-04 15:40:45,888 [main] INFO  org.red5.server.service.WarDeployer -
War deployer service created
2015-02-04 15:40:45,921 [main] INFO  o.r.spring.Red5ApplicationContext -
setApplicationContext:
org.springframework.context.support.FileSystemXmlApplicationContext@3cf9edf3:
startup date [Wed Feb 04 15:40:44 CET 2015]; root of context h$
2015-02-04 15:40:45,921 [main] INFO  o.r.spring.Red5ApplicationContext -
Red5ApplicationContext init
2015-02-04 15:40:45,921 [main] INFO  o.r.spring.Red5ApplicationContext -
Refreshing ApplicationContext 'red5.core': startup date [Wed Feb 04
15:40:45 CET 2015]; parent: ApplicationContext 'red5.common'
2015-02-04 15:40:45,922 [main] INFO  o.s.b.f.xml.XmlBeanDefinitionReader -
Loading XML bean definitions from class path resource [red5-core.xml]
2015-02-04 15:40:45,951 [main] INFO  o.r.spring.Red5ApplicationContext -
Closing ApplicationContext 'red5.common': startup date [Wed Feb 04 15:40:45
CET 2015]; parent:
org.springframework.context.support.FileSystemXmlApplicationContext@$
2015-02-04 15:40:45,952 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter -
Unregistering JMX-exposed beans on shutdown
2015-02-04 15:40:45,952 [main] INFO  o.s.j.s.ConnectorServerFactoryBean -
Stopping JMX connector server:
javax.management.remote.rmi.RMIConnectorServer@7fa1dd69
2015-02-04 15:40:45,954 [main] INFO  o.s.r.rmi.RmiRegistryFactoryBean -
Unexporting RMI registry
2015-02-04 15:40:45,955 [main] INFO  org.quartz.core.QuartzScheduler -
Scheduler Red5_Scheduler_$_NON_CLUSTERED shutting down.
2015-02-04 15:40:45,955 [main] INFO  org.quartz.core.QuartzScheduler -
Scheduler Red5_Scheduler_$_NON_CLUSTERED paused.
2015-02-04 15:40:45,955 [main] INFO  org.quartz.core.QuartzScheduler -
Scheduler Red5_Scheduler_$_NON_CLUSTERED shutdown complete.

2015-02-02 8:59 GMT+01:00 Maxim Solodovnik <[email protected]>:

> for testing purposes I would recommend you to do the following
> 1) create own CA (self signed)
> 2) add created CA to java trusted authorities
> 3) add CA to the browser trusted authorities with pernission to auth the
> sites etc.
> 4) create certificate as described here:
> http://openmeetings.apache.org/RTMPSAndHTTPS.html
> 5) sign certificate created on 4) using CA created in 1)
>
> it works as expected on my testing server
>
>
> On Mon, Feb 2, 2015 at 1:49 PM, Lionel Djeukam <[email protected]>
> wrote:
>
>> Hello Maxim,
>>
>> actually i use self-signed certificate for test purposes in our
>> laboratory.
>> Could this be the cause of the problem, because i did verify almost tree
>> time the RTMPS configuration.
>>
>> 2015-02-02 5:07 GMT+01:00 Maxim Solodovnik <[email protected]>:
>>
>>> I'm afraid your RTMPS settings are not good enough :(
>>> You should have exception in red5.log.
>>>
>>> Are you using "real" certificate of "self-signed"?
>>>
>>> On Sat, Jan 31, 2015 at 6:21 PM, Lionel Djeukam <[email protected]>
>>> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> i did receive the following error message, after setting up RTMPS:
>>>>
>>>> "NetConnection.Connect.Failed"
>>>> It's actually coming when i try to start a conference room.
>>>> There was no problem to connect with HTTPs.
>>>>
>>>> I joint to this mail a screeshot for a better overview.
>>>>
>>>> Thanks in advance for any solutions proposals
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Lionel
>>>> Master-Student Communication systems and Networks
>>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>>
>> --
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
DJOMATCHO Djeukam, Lionel
*Master-Student Kommunikationssysteme und Netze*
Tel-Nummer: (+49) 176 996 248 93
Deutzer Ring 5
50679 Köln

Reply via email to