You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Manoj Sharma (JIRA)" <ji...@apache.org> on 2016/12/08 06:26:58 UTC

[jira] [Commented] (OPENMEETINGS-1519) Shows: Could not find key in configurations: OM313 not working on CENTOS7

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731281#comment-15731281 ] 

Manoj Sharma commented on OPENMEETINGS-1519:
--------------------------------------------

Thanks Maxim,

but there is no firewall in between, OM is installed on VMware hosted on
same PC from where i am trying to access the OM GUI. Also there is no
antivirus installed on it.

Regards

MANOJ SHARMA
MBA, B.E (Electronics & comm)
9810874356 , 27537150
manoj.electronics@gmail.com

On Thu, Dec 8, 2016 at 11:50 AM, Maxim Solodovnik (JIRA) <ji...@apache.org>



> Shows:  Could not find key in configurations: OM313 not working on CENTOS7
> --------------------------------------------------------------------------
>
>                 Key: OPENMEETINGS-1519
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1519
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: BuildsAndReleases
>    Affects Versions: 3.1.3
>         Environment: CENTOS 7 GNOM1511
> Openmeetin 3.1.3
> VMware with 4GB RAM
>            Reporter: Manoj Sharma
>            Assignee: Maxim Solodovnik
>              Labels: build, documentation
>         Attachments: OMputty20161207, image.png, openmeetings.log, red5.log
>
>
> Dear Team,
> I am trying to install OM313 on CENTOS 7 GNOM1511. After running the command :
> /etc/init.d/red5-3 start
> inbetween logs in shell it shows : Could not find key in configurations: 
> after getting : “clearSessionTable: 0”, 
> Nothing comes when i tried to open the GUI:
> http://192.168.1.20:5080/openmeetings/install
> in openmeeting Logs i found below:
> [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-3] - ... resetSendingStatus done.
>  WARN 12-07 14:38:22.451 o.a.o.d.d.b.ConfigurationDao:118 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - Could not find key in configurations: smtp_server
>  WARN 12-07 14:38:22.482 o.a.o.d.d.b.ConfigurationDao:118 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - Could not find key in configurations: smtp_port
>  WARN 12-07 14:38:22.485 o.a.o.d.d.b.ConfigurationDao:118 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - Could not find key in configurations: system_email_addr
>  WARN 12-07 14:38:22.489 o.a.o.d.d.b.ConfigurationDao:118 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - Could not find key in configurations: email_username
>  WARN 12-07 14:38:22.514 o.a.o.d.d.b.ConfigurationDao:118 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - Could not find key in configurations: email_userpass
>  WARN 12-07 14:38:22.516 o.a.o.d.d.b.ConfigurationDao:118 [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4] - Could not find key in configurations: mail.smtp.starttls.enable
>  WARN 12-07 14:38:22.518 
> Please help
> Regards



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)