You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Stefan Kühl <st...@quatrekuehl.eu> on 2019/04/14 09:36:32 UTC
Update 404 Apache to 5.0
Morning,
try to update my 4.0.4 running on apache2 to version 5.0
but I cannot connect to web-installer, because of insecure connection
(using HSTS). I copied all the neccessary certifiacte files into the new
OM folder. Is there any other differenz I need to take care of in using
Apache2 instead of tomcat?
Greetz
Stefan
Am 14.04.2019 10:36, schrieb Stefan Kühl:
> Morning@ everybody,
>
> tested it three times. Installation of kms directly on a 18.04. LTS Ubuntu works very well.
>
> Maybe for Alvaro and his great Tutorials (!) it would be worth to add a paragraph for native installation with the commands:
>
> sudo apt update
> sudo apt install --no-install-recommends --yes gnupg #to be sure that gnupg is installed#
> DISTRO="bionic" #verify the name of the distribution#
> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
> #in the following we are building the kms sources.list#
> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
> # server answers with > #
> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
> EOF
> # server returns to normal prompt #
> sudo apt update && sudo apt install --yes kurento-media-server
>
> ## thats all ##
>
> Greetz
>
> Stefan
>
> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
>
>> Hello All,
>>
>> recently new Kurento server with native 18.04 support is out [1 [1]]
>> So overall installation should be more stable :)
>>
>> [1] https://www.kurento.org/blog/kurento-610-bionic-support
Links:
------
[1] https://www.kurento.org/blog/kurento-610-bionic-support
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Ok, got it so far ;-)
Need to restart apache, mysql and OM.
Now the database check worked.
Try to move on and promise to be silence today ;-)
Thanks a lot!
Am 15.04.2019 09:59, schrieb Maxim Solodovnik:
> This should be enough
> Can you confirm you have stop OM
> Perform change and start it again?
>
> On Mon, 15 Apr 2019 at 14:54, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> OK, Maxim,
>
> thanks a lot for the hint.
> No i found the error:
>
> Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
>
> After that I've added the server timezone in the mysql-persistence.xml:
>
> Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&serverTimezone=Europe/Berlin&....
>
> Restart tomcat3 script and mysql.
>
> Error stays. Is there any other place I need to add the serverTimezone?
>
> Greetz
>
> Stefan
>
> Am 15.04.2019 07:58, schrieb Maxim Solodovnik:
> Additional NOTE: please check log file is writable
> i.e. sometimes OM is being run as root for the first time, then user is changed, but log dir/file is not writable ...
>
> On Mon, 15 Apr 2019 at 12:50, Maxim Solodovnik <so...@gmail.com> wrote:
> You MUST have huge stack-trace in the log in this case .....
>
> On Mon, 15 Apr 2019 at 12:47, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Hey ;-)
>
> could it be so easy?
>
> Unfortunately not:
>
> Am 15.04.2019 07:15, schrieb Maxim Solodovnik:
> "No hint for MySql connection" === no errors, everything works as expected :)))
> Old driver will not work (unless you will change class name)
>
> On Mon, 15 Apr 2019 at 12:14, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Hey Maxim,
>
> as I wrote, I've tried the newest java-connector (and to be sure also the old one ;-))
>
> Here my openmeetingslog from the last try:
>
> INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root WebApplicationContext: initialization started
> INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415 [main] - Initialized JPA EntityManagerFactory for persistence unit 'openmeetings'
> INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] - Initializing ExecutorService 'taskExecutor'
> INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191 [rbeatExec-e1-t0] - [KurentoClient] Connecting native client
> INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220 [rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308 [rbeatExec-e1-t0] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] - [KurentoClient] Error sending heartbeat to server. Exception: [KurentoClient] Exception connecting to WebSocket server ws://127.0.0.1:8888/kurento [1]
> INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main] - [KurentoClient] Connecting native client
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] - [KurentoClient] Stopping heartbeat and closing client: failure during heartbeat mechanism
> INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to create Kurento client, will re-try in 10000 ms
> INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using default implementation for ThreadExecutor
> INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
> INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz Scheduler v.2.2.0 created.
> INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore initialized.
> INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler meta-data: Quartz Scheduler (v2.2.0) 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10 threads.
> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
>
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' initialized from an externally provided properties instance.
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz scheduler version: 2.2.0
> INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory set to: org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
> INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] - Starting Quartz Scheduler now
> INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED started.
> INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root WebApplicationContext initialized in 7740 ms
> INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url mapping found for filter with name OpenmeetingsApplication: [/*]
> INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket jQuery UI initializer
> INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket core library initializer
> INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket extensions initializer
> INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket Kendo UI initializer
> INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: DevUtils DebugBar Initializer
> INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket Kendo UI initializer (theme-default)
> DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] - Application::init
> DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath : /opt/open500/webapps/openmeetings
> WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: max.upload.size
> WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: crypt.class.name [2]
> WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: application.name [3]
> WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.lang.id [4]
> WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: application.base.url
> WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: sip.enable
> WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: google.analytics.code
> WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.audio.rate
> WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.audio.bitrate
> WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.video.preset
> WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.timezone
> WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: rest.allow.origin
> WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: video.arrange.keycode
> WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mute.others.keycode
> DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] - getInstanceOfCrypt:: configKeyCryptClassName: null
> WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mute.keycode
> WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: cam.fps
> WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.rate
> WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.echo.cancellation
> WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.noise.suppression
> WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.group.id [5]
> WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: sip.exten.context
> WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.fname.minimum.length
> WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.lname.minimum.length
> WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: chat.send.on.enter
> WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.frontend.register
> WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.soap.register
> WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.oauth.register
> WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: send.email.with.verfication
> WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: send.email.at.register
> WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: header.csp.frame.options
> WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: header.content.security.policy
> WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: chrome.sharing.ext.url
> WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: display.name.editable
> WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: external.process.ttl
> DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
> ################################################################################
> # Openmeetings is up #
> # 5.0.0-M1 c88fce9 2019-03-29T14:46:44Z #
> # and ready to use #
> ################################################################################
>
> INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] - [OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT mode
> INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /
> INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService [6] from class org.apache.openmeetings.webservice.CalendarWebService
> INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /CalendarService
> INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService [7] from class org.apache.openmeetings.webservice.ErrorWebService
> INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /ErrorService
> INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService [8] from class org.apache.openmeetings.webservice.GroupWebService
> INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /GroupService
> INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService [9] from class org.apache.openmeetings.webservice.InfoWebService
> INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /InfoService
> INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService [10] from class org.apache.openmeetings.webservice.FileWebService
> INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191 [pool-1-thread-1] - [KurentoClient] Connecting native client
> INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220 [pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308 [pool-1-thread-1] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create Kurento client, will re-try in 10000 ms
> WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] - [KurentoClient] Error sending heartbeat to server. Exception: InterruptedException while trying to acquire lock
> WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] - [KurentoClient] Stopping heartbeat and closing client: failure during heartbeat mechanism
> INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /FileService
> INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService [11] from class org.apache.openmeetings.webservice.RecordingWebService
> INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /RecordService
> INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService [12] from class org.apache.openmeetings.webservice.RoomWebService
> INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /RoomService
> INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService [13] from class org.apache.openmeetings.webservice.UserWebService
> INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /UserService
> INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket core library initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket extensions initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer (theme-default)
>
> No hint for the mysql connection (maybe I'm blind ;-))
>
> If you mention the time zone in the connection string, you tlak about the persistense.xml and the values of the connectionstring, right?
>
> Greetz Stefan
>
> Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
> Hello,
>
> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the time of writing): https://mvnrepository.com/artifact/mysql/mysql-connector-java
> Also please check openmeetings.log and ensure what the exact error is being reported while connecting
> (you might need to add server time zone to connection string ....)
>
> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Good Morning @all,
>
> I'm sorry and don't wanna create a messenger out of this list, but the problem is still present.
> To make a clear summary:
>
> The host is a VPS with 4 core and 12GB RAM, running under an "up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2 Webserver.
> The former installation of OM was an 4.0.4., running well (but with flash). My steps to upgrade to OM5 were the following:
>
> 1. Delete folder with existing installtion of OM (backup not nessecary, no files, just a few users)
>
> 2. Drop Database
>
> 3. Create new Database (tried same name first, later on tried different names)
>
> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>
> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>
> 6. Running Web-Installer
>
> Facing Problem that the mysql settings not work. Error:
>
> Could not create connection to database server. Attempted reconnect 3 times. Giving up. (second page web-installer)
>
> Credentials are correct and worked fine via cli!
>
> Additional steps I've tried:
>
> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8 is installed),
> tried both java connectors (version 5.x and 8.x),
> reinstall mariadb-server,
> drop databases und recreate,
> copy mysql-persistence.xml with valid database and credentials,
> ...
>
> Something strange: When stopped and leave the web-installer in step 2 (Database settings) I receive a "redirection error" if I try to restart the web-installer?!
>
> Ok, so far....any ideas?
>
> Maybe a problem of Apache2? (no idea why, but the last thing I didn't change)
>
> Greetz
>
> Stefan
> --
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
Links:
------
[1] http://127.0.0.1:8888/kurento
[2] http://crypt.class.name
[3] http://application.name
[4] http://default.lang.id
[5] http://default.group.id
[6]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.CalendarWebService
[7]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.ErrorWebService
[8]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.GroupWebService
[9]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.InfoWebService
[10]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.FileWebService
[11]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.RecordingWebService
[12]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.RoomWebService
[13]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.UserWebService
Re: Update 404 Apache to 5.0
Posted by Maxim Solodovnik <so...@gmail.com>.
This should be enough
Can you confirm you have stop OM
Perform change and start it again?
On Mon, 15 Apr 2019 at 14:54, Stefan Kühl <st...@quatrekuehl.eu> wrote:
> OK, Maxim,
>
> thanks a lot for the hint.
> No i found the error:
>
> Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException:
> The server time zone value 'CEST' is unrecognized or represents more than
> one time zone. You must configure either the server or JDBC driver (via the
> serverTimezone configuration property) to use a more specifc time zone
> value if you want to utilize time zone support.
>
> After that I've added the server timezone in the mysql-persistence.xml:
>
>
> Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&serverTimezone=Europe/Berlin&....
>
>
> Restart tomcat3 script and mysql.
>
> Error stays. Is there any other place I need to add the serverTimezone?
>
> Greetz
>
> Stefan
>
> Am 15.04.2019 07:58, schrieb Maxim Solodovnik:
>
> Additional NOTE: please check log file is writable
> i.e. sometimes OM is being run as root for the first time, then user is
> changed, but log dir/file is not writable ...
>
> On Mon, 15 Apr 2019 at 12:50, Maxim Solodovnik <so...@gmail.com>
> wrote:
>
>> You MUST have huge stack-trace in the log in this case .....
>>
>> On Mon, 15 Apr 2019 at 12:47, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>>
>>> Hey ;-)
>>>
>>> could it be so easy?
>>>
>>> Unfortunately not:
>>>
>>>
>>>
>>>
>>> Am 15.04.2019 07:15, schrieb Maxim Solodovnik:
>>>
>>> "No hint for MySql connection" === no errors, everything works as
>>> expected :)))
>>> Old driver will not work (unless you will change class name)
>>>
>>> On Mon, 15 Apr 2019 at 12:14, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>>>
>>>> Hey Maxim,
>>>>
>>>> as I wrote, I've tried the newest java-connector (and to be sure also
>>>> the old one ;-))
>>>>
>>>> Here my openmeetingslog from the last try:
>>>>
>>>> INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root
>>>> WebApplicationContext: initialization started
>>>> INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415
>>>> [main] - Initialized JPA EntityManagerFactory for persistence unit
>>>> 'openmeetings'
>>>> INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] -
>>>> Initializing ExecutorService 'taskExecutor'
>>>> INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191
>>>> [rbeatExec-e1-t0] - [KurentoClient] Connecting native client
>>>> INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220
>>>> [rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
>>>> INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234
>>>> [ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will
>>>> create new handler too!
>>>> WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>>> [rbeatExec-e1-t0] - [KurentoClient] Trying to close a
>>>> JsonRpcClientNettyWebSocket with channel == null
>>>> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] -
>>>> [KurentoClient] Error sending heartbeat to server. Exception:
>>>> [KurentoClient] Exception connecting to WebSocket server ws://
>>>> 127.0.0.1:8888/kurento
>>>> INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main]
>>>> - [KurentoClient] Connecting native client
>>>> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] -
>>>> [KurentoClient] Stopping heartbeat and closing client: failure during
>>>> heartbeat mechanism
>>>> INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main]
>>>> - [KurentoClient] Creating new NioEventLoopGroup
>>>> INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234
>>>> [ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will
>>>> create new handler too!
>>>> WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main]
>>>> - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with
>>>> channel == null
>>>> WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to
>>>> create Kurento client, will re-try in 10000 ms
>>>> INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using
>>>> default implementation for ThreadExecutor
>>>> INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] -
>>>> Initialized Scheduler Signaller of type: class
>>>> org.quartz.core.SchedulerSignalerImpl
>>>> INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz
>>>> Scheduler v.2.2.0 created.
>>>> INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore
>>>> initialized.
>>>> INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler
>>>> meta-data: Quartz Scheduler (v2.2.0)
>>>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10
>>>> threads.
>>>> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
>>>> support persistence. and is not clustered.
>>>>
>>>> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz
>>>> scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0'
>>>> initialized from an externally provided properties instance.
>>>> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz
>>>> scheduler version: 2.2.0
>>>> INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory
>>>> set to: org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
>>>> INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] -
>>>> Starting Quartz Scheduler now
>>>> INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler
>>>> org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED
>>>> started.
>>>> INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root
>>>> WebApplicationContext initialized in 7740 ms
>>>> INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url
>>>> mapping found for filter with name OpenmeetingsApplication: [/*]
>>>> INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init: Wicket jQuery UI initializer
>>>> INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init: Wicket core library initializer
>>>> INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init:
>>>> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
>>>> INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init: Wicket extensions initializer
>>>> INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init: Wicket Kendo UI initializer
>>>> INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init: DevUtils DebugBar Initializer
>>>> INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
>>>> INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] -
>>>> [OpenmeetingsApplication] init: Wicket Kendo UI initializer (theme-default)
>>>> DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] -
>>>> Application::init
>>>> DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath
>>>> : /opt/open500/webapps/openmeetings
>>>> WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: max.upload.size
>>>> WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: crypt.class.name
>>>> WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: application.name
>>>> WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: default.lang.id
>>>> WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: application.base.url
>>>> WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: sip.enable
>>>> WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: google.analytics.code
>>>> WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mp4.audio.rate
>>>> WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mp4.audio.bitrate
>>>> WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mp4.video.preset
>>>> WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: default.timezone
>>>> WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: rest.allow.origin
>>>> WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: video.arrange.keycode
>>>> WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mute.others.keycode
>>>> DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] -
>>>> getInstanceOfCrypt:: configKeyCryptClassName: null
>>>> WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mute.keycode
>>>> WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: cam.fps
>>>> WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mic.rate
>>>> WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mic.echo.cancellation
>>>> WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: mic.noise.suppression
>>>> WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: user.login.minimum.length
>>>> WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: user.login.minimum.length
>>>> WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: default.group.id
>>>> WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: sip.exten.context
>>>> WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: user.fname.minimum.length
>>>> WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: user.lname.minimum.length
>>>> WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: chat.send.on.enter
>>>> WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: allow.frontend.register
>>>> WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: allow.soap.register
>>>> WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: allow.oauth.register
>>>> WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: send.email.with.verfication
>>>> WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: send.email.at.register
>>>> WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: header.csp.frame.options
>>>> WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: header.content.security.policy
>>>> WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: chrome.sharing.ext.url
>>>> WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: display.name.editable
>>>> WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] -
>>>> Could not find key in configurations: external.process.ttl
>>>> DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
>>>>
>>>> ################################################################################
>>>> # Openmeetings is
>>>> up #
>>>> # 5.0.0-M1 c88fce9
>>>> 2019-03-29T14:46:44Z #
>>>> # and ready to
>>>> use #
>>>>
>>>> ################################################################################
>>>>
>>>> INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] -
>>>> [OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT mode
>>>> INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /
>>>> INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService
>>>> from class org.apache.openmeetings.webservice.CalendarWebService
>>>> INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /CalendarService
>>>> INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService
>>>> from class org.apache.openmeetings.webservice.ErrorWebService
>>>> INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /ErrorService
>>>> INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService
>>>> from class org.apache.openmeetings.webservice.GroupWebService
>>>> INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /GroupService
>>>> INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService
>>>> from class org.apache.openmeetings.webservice.InfoWebService
>>>> INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /InfoService
>>>> INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService
>>>> from class org.apache.openmeetings.webservice.FileWebService
>>>> INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191
>>>> [pool-1-thread-1] - [KurentoClient] Connecting native client
>>>> INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220
>>>> [pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
>>>> INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234
>>>> [ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will
>>>> create new handler too!
>>>> WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>>> [pool-1-thread-1] - [KurentoClient] Trying to close a
>>>> JsonRpcClientNettyWebSocket with channel == null
>>>> WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1]
>>>> - Fail to create Kurento client, will re-try in 10000 ms
>>>> WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] -
>>>> [KurentoClient] Error sending heartbeat to server. Exception:
>>>> InterruptedException while trying to acquire lock
>>>> WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] -
>>>> [KurentoClient] Stopping heartbeat and closing client: failure during
>>>> heartbeat mechanism
>>>> INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /FileService
>>>> INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService
>>>> from class org.apache.openmeetings.webservice.RecordingWebService
>>>> INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /RecordService
>>>> INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService
>>>> from class org.apache.openmeetings.webservice.RoomWebService
>>>> INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /RoomService
>>>> INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>>> [main] - Creating Service {
>>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService
>>>> from class org.apache.openmeetings.webservice.UserWebService
>>>> INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the
>>>> server's publish address to be /UserService
>>>> INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
>>>> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy: Wicket core library initializer
>>>> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy:
>>>> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
>>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy: Wicket extensions initializer
>>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
>>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
>>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
>>>> INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] -
>>>> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
>>>> (theme-default)
>>>>
>>>>
>>>> No hint for the mysql connection (maybe I'm blind ;-))
>>>>
>>>> If you mention the time zone in the connection string, you tlak about
>>>> the persistense.xml and the values of the connectionstring, right?
>>>>
>>>> Greetz Stefan
>>>>
>>>> Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
>>>>
>>>> Hello,
>>>>
>>>> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the
>>>> time of writing):
>>>> https://mvnrepository.com/artifact/mysql/mysql-connector-java
>>>> Also please check openmeetings.log and ensure what the exact error is
>>>> being reported while connecting
>>>> (you might need to add server time zone to connection string ....)
>>>>
>>>> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu>
>>>> wrote:
>>>>
>>>>> Good Morning @all,
>>>>>
>>>>> I'm sorry and don't wanna create a messenger out of this list, but the
>>>>> problem is still present.
>>>>> To make a clear summary:
>>>>>
>>>>> The host is a VPS with 4 core and 12GB RAM, running under an
>>>>> "up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2
>>>>> Webserver.
>>>>> The former installation of OM was an 4.0.4., running well (but with
>>>>> flash). My steps to upgrade to OM5 were the following:
>>>>>
>>>>> 1. Delete folder with existing installtion of OM (backup not
>>>>> nessecary, no files, just a few users)
>>>>>
>>>>> 2. Drop Database
>>>>>
>>>>> 3. Create new Database (tried same name first, later on tried
>>>>> different names)
>>>>>
>>>>> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>>>>>
>>>>> 5. Start OM using the tomcat3 script (folder-names updatet if
>>>>> nessecary)
>>>>>
>>>>> 6. Running Web-Installer
>>>>>
>>>>> Facing Problem that the mysql settings not work. Error:
>>>>>
>>>>> Could not create connection to database server. Attempted reconnect 3
>>>>> times. Giving up. (second page web-installer)
>>>>>
>>>>> Credentials are correct and worked fine via cli!
>>>>>
>>>>> Additional steps I've tried:
>>>>>
>>>>> reinstall of OM with Tutorial (sparing out the steps Java - version
>>>>> 1.8 is installed),
>>>>> tried both java connectors (version 5.x and 8.x),
>>>>> reinstall mariadb-server,
>>>>> drop databases und recreate,
>>>>> copy mysql-persistence.xml with valid database and credentials,
>>>>> ...
>>>>>
>>>>> Something strange: When stopped and leave the web-installer in step 2
>>>>> (Database settings) I receive a "redirection error" if I try to restart the
>>>>> web-installer?!
>>>>>
>>>>> Ok, so far....any ideas?
>>>>>
>>>>> Maybe a problem of Apache2? (no idea why, but the last thing I didn't
>>>>> change)
>>>>>
>>>>> Greetz
>>>>>
>>>>> Stefan
>>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>
--
WBR
Maxim aka solomax
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
OK, Maxim,
thanks a lot for the hint.
No i found the error:
Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException:
The server time zone value 'CEST' is unrecognized or represents more
than one time zone. You must configure either the server or JDBC driver
(via the serverTimezone configuration property) to use a more specifc
time zone value if you want to utilize time zone support.
After that I've added the server timezone in the mysql-persistence.xml:
Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&serverTimezone=Europe/Berlin&....
Restart tomcat3 script and mysql.
Error stays. Is there any other place I need to add the serverTimezone?
Greetz
Stefan
Am 15.04.2019 07:58, schrieb Maxim Solodovnik:
> Additional NOTE: please check log file is writable
> i.e. sometimes OM is being run as root for the first time, then user is changed, but log dir/file is not writable ...
>
> On Mon, 15 Apr 2019 at 12:50, Maxim Solodovnik <so...@gmail.com> wrote:
> You MUST have huge stack-trace in the log in this case .....
>
> On Mon, 15 Apr 2019 at 12:47, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Hey ;-)
>
> could it be so easy?
>
> Unfortunately not:
>
> Am 15.04.2019 07:15, schrieb Maxim Solodovnik:
> "No hint for MySql connection" === no errors, everything works as expected :)))
> Old driver will not work (unless you will change class name)
>
> On Mon, 15 Apr 2019 at 12:14, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Hey Maxim,
>
> as I wrote, I've tried the newest java-connector (and to be sure also the old one ;-))
>
> Here my openmeetingslog from the last try:
>
> INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root WebApplicationContext: initialization started
> INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415 [main] - Initialized JPA EntityManagerFactory for persistence unit 'openmeetings'
> INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] - Initializing ExecutorService 'taskExecutor'
> INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191 [rbeatExec-e1-t0] - [KurentoClient] Connecting native client
> INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220 [rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308 [rbeatExec-e1-t0] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] - [KurentoClient] Error sending heartbeat to server. Exception: [KurentoClient] Exception connecting to WebSocket server ws://127.0.0.1:8888/kurento [1]
> INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main] - [KurentoClient] Connecting native client
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] - [KurentoClient] Stopping heartbeat and closing client: failure during heartbeat mechanism
> INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to create Kurento client, will re-try in 10000 ms
> INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using default implementation for ThreadExecutor
> INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
> INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz Scheduler v.2.2.0 created.
> INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore initialized.
> INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler meta-data: Quartz Scheduler (v2.2.0) 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10 threads.
> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
>
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' initialized from an externally provided properties instance.
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz scheduler version: 2.2.0
> INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory set to: org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
> INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] - Starting Quartz Scheduler now
> INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED started.
> INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root WebApplicationContext initialized in 7740 ms
> INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url mapping found for filter with name OpenmeetingsApplication: [/*]
> INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket jQuery UI initializer
> INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket core library initializer
> INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket extensions initializer
> INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket Kendo UI initializer
> INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: DevUtils DebugBar Initializer
> INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket Kendo UI initializer (theme-default)
> DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] - Application::init
> DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath : /opt/open500/webapps/openmeetings
> WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: max.upload.size
> WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: crypt.class.name [2]
> WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: application.name [3]
> WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.lang.id [4]
> WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: application.base.url
> WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: sip.enable
> WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: google.analytics.code
> WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.audio.rate
> WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.audio.bitrate
> WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.video.preset
> WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.timezone
> WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: rest.allow.origin
> WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: video.arrange.keycode
> WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mute.others.keycode
> DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] - getInstanceOfCrypt:: configKeyCryptClassName: null
> WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mute.keycode
> WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: cam.fps
> WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.rate
> WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.echo.cancellation
> WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.noise.suppression
> WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.group.id [5]
> WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: sip.exten.context
> WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.fname.minimum.length
> WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.lname.minimum.length
> WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: chat.send.on.enter
> WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.frontend.register
> WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.soap.register
> WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.oauth.register
> WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: send.email.with.verfication
> WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: send.email.at.register
> WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: header.csp.frame.options
> WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: header.content.security.policy
> WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: chrome.sharing.ext.url
> WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: display.name.editable
> WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: external.process.ttl
> DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
> ################################################################################
> # Openmeetings is up #
> # 5.0.0-M1 c88fce9 2019-03-29T14:46:44Z #
> # and ready to use #
> ################################################################################
>
> INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] - [OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT mode
> INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /
> INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService [6] from class org.apache.openmeetings.webservice.CalendarWebService
> INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /CalendarService
> INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService [7] from class org.apache.openmeetings.webservice.ErrorWebService
> INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /ErrorService
> INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService [8] from class org.apache.openmeetings.webservice.GroupWebService
> INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /GroupService
> INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService [9] from class org.apache.openmeetings.webservice.InfoWebService
> INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /InfoService
> INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService [10] from class org.apache.openmeetings.webservice.FileWebService
> INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191 [pool-1-thread-1] - [KurentoClient] Connecting native client
> INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220 [pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308 [pool-1-thread-1] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create Kurento client, will re-try in 10000 ms
> WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] - [KurentoClient] Error sending heartbeat to server. Exception: InterruptedException while trying to acquire lock
> WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] - [KurentoClient] Stopping heartbeat and closing client: failure during heartbeat mechanism
> INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /FileService
> INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService [11] from class org.apache.openmeetings.webservice.RecordingWebService
> INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /RecordService
> INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService [12] from class org.apache.openmeetings.webservice.RoomWebService
> INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /RoomService
> INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService [13] from class org.apache.openmeetings.webservice.UserWebService
> INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /UserService
> INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket core library initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket extensions initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer (theme-default)
>
> No hint for the mysql connection (maybe I'm blind ;-))
>
> If you mention the time zone in the connection string, you tlak about the persistense.xml and the values of the connectionstring, right?
>
> Greetz Stefan
>
> Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
> Hello,
>
> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the time of writing): https://mvnrepository.com/artifact/mysql/mysql-connector-java
> Also please check openmeetings.log and ensure what the exact error is being reported while connecting
> (you might need to add server time zone to connection string ....)
>
> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Good Morning @all,
>
> I'm sorry and don't wanna create a messenger out of this list, but the problem is still present.
> To make a clear summary:
>
> The host is a VPS with 4 core and 12GB RAM, running under an "up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2 Webserver.
> The former installation of OM was an 4.0.4., running well (but with flash). My steps to upgrade to OM5 were the following:
>
> 1. Delete folder with existing installtion of OM (backup not nessecary, no files, just a few users)
>
> 2. Drop Database
>
> 3. Create new Database (tried same name first, later on tried different names)
>
> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>
> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>
> 6. Running Web-Installer
>
> Facing Problem that the mysql settings not work. Error:
>
> Could not create connection to database server. Attempted reconnect 3 times. Giving up. (second page web-installer)
>
> Credentials are correct and worked fine via cli!
>
> Additional steps I've tried:
>
> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8 is installed),
> tried both java connectors (version 5.x and 8.x),
> reinstall mariadb-server,
> drop databases und recreate,
> copy mysql-persistence.xml with valid database and credentials,
> ...
>
> Something strange: When stopped and leave the web-installer in step 2 (Database settings) I receive a "redirection error" if I try to restart the web-installer?!
>
> Ok, so far....any ideas?
>
> Maybe a problem of Apache2? (no idea why, but the last thing I didn't change)
>
> Greetz
>
> Stefan
> --
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
Links:
------
[1] http://127.0.0.1:8888/kurento
[2] http://crypt.class.name
[3] http://application.name
[4] http://default.lang.id
[5] http://default.group.id
[6]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.CalendarWebService
[7]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.ErrorWebService
[8]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.GroupWebService
[9]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.InfoWebService
[10]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.FileWebService
[11]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.RecordingWebService
[12]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.RoomWebService
[13]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.UserWebService
Re: Update 404 Apache to 5.0
Posted by Maxim Solodovnik <so...@gmail.com>.
Additional NOTE: please check log file is writable
i.e. sometimes OM is being run as root for the first time, then user is
changed, but log dir/file is not writable ...
On Mon, 15 Apr 2019 at 12:50, Maxim Solodovnik <so...@gmail.com> wrote:
> You MUST have huge stack-trace in the log in this case .....
>
> On Mon, 15 Apr 2019 at 12:47, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
>> Hey ;-)
>>
>> could it be so easy?
>>
>> Unfortunately not:
>>
>>
>>
>>
>> Am 15.04.2019 07:15, schrieb Maxim Solodovnik:
>>
>> "No hint for MySql connection" === no errors, everything works as
>> expected :)))
>> Old driver will not work (unless you will change class name)
>>
>> On Mon, 15 Apr 2019 at 12:14, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>>
>>> Hey Maxim,
>>>
>>> as I wrote, I've tried the newest java-connector (and to be sure also
>>> the old one ;-))
>>>
>>> Here my openmeetingslog from the last try:
>>>
>>> INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root
>>> WebApplicationContext: initialization started
>>> INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415
>>> [main] - Initialized JPA EntityManagerFactory for persistence unit
>>> 'openmeetings'
>>> INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] -
>>> Initializing ExecutorService 'taskExecutor'
>>> INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191
>>> [rbeatExec-e1-t0] - [KurentoClient] Connecting native client
>>> INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220
>>> [rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
>>> INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234
>>> [ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will
>>> create new handler too!
>>> WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>> [rbeatExec-e1-t0] - [KurentoClient] Trying to close a
>>> JsonRpcClientNettyWebSocket with channel == null
>>> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] -
>>> [KurentoClient] Error sending heartbeat to server. Exception:
>>> [KurentoClient] Exception connecting to WebSocket server ws://
>>> 127.0.0.1:8888/kurento
>>> INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main]
>>> - [KurentoClient] Connecting native client
>>> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] -
>>> [KurentoClient] Stopping heartbeat and closing client: failure during
>>> heartbeat mechanism
>>> INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main]
>>> - [KurentoClient] Creating new NioEventLoopGroup
>>> INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234
>>> [ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will
>>> create new handler too!
>>> WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main]
>>> - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with
>>> channel == null
>>> WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to
>>> create Kurento client, will re-try in 10000 ms
>>> INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using
>>> default implementation for ThreadExecutor
>>> INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] -
>>> Initialized Scheduler Signaller of type: class
>>> org.quartz.core.SchedulerSignalerImpl
>>> INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz
>>> Scheduler v.2.2.0 created.
>>> INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore
>>> initialized.
>>> INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler
>>> meta-data: Quartz Scheduler (v2.2.0)
>>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10
>>> threads.
>>> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
>>> support persistence. and is not clustered.
>>>
>>> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz
>>> scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0'
>>> initialized from an externally provided properties instance.
>>> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz
>>> scheduler version: 2.2.0
>>> INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory
>>> set to: org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
>>> INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] -
>>> Starting Quartz Scheduler now
>>> INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler
>>> org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED
>>> started.
>>> INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root
>>> WebApplicationContext initialized in 7740 ms
>>> INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url
>>> mapping found for filter with name OpenmeetingsApplication: [/*]
>>> INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init: Wicket jQuery UI initializer
>>> INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init: Wicket core library initializer
>>> INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init:
>>> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
>>> INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init: Wicket extensions initializer
>>> INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init: Wicket Kendo UI initializer
>>> INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init: DevUtils DebugBar Initializer
>>> INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
>>> INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] -
>>> [OpenmeetingsApplication] init: Wicket Kendo UI initializer (theme-default)
>>> DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] -
>>> Application::init
>>> DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath :
>>> /opt/open500/webapps/openmeetings
>>> WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: max.upload.size
>>> WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: crypt.class.name
>>> WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: application.name
>>> WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: default.lang.id
>>> WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: application.base.url
>>> WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: sip.enable
>>> WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: google.analytics.code
>>> WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mp4.audio.rate
>>> WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mp4.audio.bitrate
>>> WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mp4.video.preset
>>> WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: default.timezone
>>> WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: rest.allow.origin
>>> WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: video.arrange.keycode
>>> WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mute.others.keycode
>>> DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] -
>>> getInstanceOfCrypt:: configKeyCryptClassName: null
>>> WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mute.keycode
>>> WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: cam.fps
>>> WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mic.rate
>>> WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mic.echo.cancellation
>>> WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: mic.noise.suppression
>>> WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: user.login.minimum.length
>>> WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: user.login.minimum.length
>>> WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: default.group.id
>>> WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: sip.exten.context
>>> WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: user.fname.minimum.length
>>> WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: user.lname.minimum.length
>>> WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: chat.send.on.enter
>>> WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: allow.frontend.register
>>> WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: allow.soap.register
>>> WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: allow.oauth.register
>>> WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: send.email.with.verfication
>>> WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: send.email.at.register
>>> WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: header.csp.frame.options
>>> WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: header.content.security.policy
>>> WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: chrome.sharing.ext.url
>>> WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: display.name.editable
>>> WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>>> not find key in configurations: external.process.ttl
>>> DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
>>>
>>> ################################################################################
>>> # Openmeetings is
>>> up #
>>> # 5.0.0-M1 c88fce9
>>> 2019-03-29T14:46:44Z #
>>> # and ready to
>>> use #
>>>
>>> ################################################################################
>>>
>>> INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] -
>>> [OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT mode
>>> INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /
>>> INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService
>>> from class org.apache.openmeetings.webservice.CalendarWebService
>>> INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /CalendarService
>>> INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService
>>> from class org.apache.openmeetings.webservice.ErrorWebService
>>> INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /ErrorService
>>> INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService
>>> from class org.apache.openmeetings.webservice.GroupWebService
>>> INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /GroupService
>>> INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService
>>> from class org.apache.openmeetings.webservice.InfoWebService
>>> INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /InfoService
>>> INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService
>>> from class org.apache.openmeetings.webservice.FileWebService
>>> INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191
>>> [pool-1-thread-1] - [KurentoClient] Connecting native client
>>> INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220
>>> [pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
>>> INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234
>>> [ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will
>>> create new handler too!
>>> WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>> [pool-1-thread-1] - [KurentoClient] Trying to close a
>>> JsonRpcClientNettyWebSocket with channel == null
>>> WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1]
>>> - Fail to create Kurento client, will re-try in 10000 ms
>>> WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] -
>>> [KurentoClient] Error sending heartbeat to server. Exception:
>>> InterruptedException while trying to acquire lock
>>> WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] -
>>> [KurentoClient] Stopping heartbeat and closing client: failure during
>>> heartbeat mechanism
>>> INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /FileService
>>> INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService
>>> from class org.apache.openmeetings.webservice.RecordingWebService
>>> INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /RecordService
>>> INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService
>>> from class org.apache.openmeetings.webservice.RoomWebService
>>> INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /RoomService
>>> INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>>> [main] - Creating Service {
>>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService
>>> from class org.apache.openmeetings.webservice.UserWebService
>>> INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the
>>> server's publish address to be /UserService
>>> INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
>>> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy: Wicket core library initializer
>>> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy:
>>> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy: Wicket extensions initializer
>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
>>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
>>> INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] -
>>> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
>>> (theme-default)
>>>
>>>
>>> No hint for the mysql connection (maybe I'm blind ;-))
>>>
>>> If you mention the time zone in the connection string, you tlak about
>>> the persistense.xml and the values of the connectionstring, right?
>>>
>>> Greetz Stefan
>>>
>>> Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
>>>
>>> Hello,
>>>
>>> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the
>>> time of writing):
>>> https://mvnrepository.com/artifact/mysql/mysql-connector-java
>>> Also please check openmeetings.log and ensure what the exact error is
>>> being reported while connecting
>>> (you might need to add server time zone to connection string ....)
>>>
>>> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>>>
>>>> Good Morning @all,
>>>>
>>>> I'm sorry and don't wanna create a messenger out of this list, but the
>>>> problem is still present.
>>>> To make a clear summary:
>>>>
>>>> The host is a VPS with 4 core and 12GB RAM, running under an
>>>> "up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2
>>>> Webserver.
>>>> The former installation of OM was an 4.0.4., running well (but with
>>>> flash). My steps to upgrade to OM5 were the following:
>>>>
>>>> 1. Delete folder with existing installtion of OM (backup not nessecary,
>>>> no files, just a few users)
>>>>
>>>> 2. Drop Database
>>>>
>>>> 3. Create new Database (tried same name first, later on tried different
>>>> names)
>>>>
>>>> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>>>>
>>>> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>>>>
>>>> 6. Running Web-Installer
>>>>
>>>> Facing Problem that the mysql settings not work. Error:
>>>>
>>>> Could not create connection to database server. Attempted reconnect 3
>>>> times. Giving up. (second page web-installer)
>>>>
>>>> Credentials are correct and worked fine via cli!
>>>>
>>>> Additional steps I've tried:
>>>>
>>>> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8
>>>> is installed),
>>>> tried both java connectors (version 5.x and 8.x),
>>>> reinstall mariadb-server,
>>>> drop databases und recreate,
>>>> copy mysql-persistence.xml with valid database and credentials,
>>>> ...
>>>>
>>>> Something strange: When stopped and leave the web-installer in step 2
>>>> (Database settings) I receive a "redirection error" if I try to restart the
>>>> web-installer?!
>>>>
>>>> Ok, so far....any ideas?
>>>>
>>>> Maybe a problem of Apache2? (no idea why, but the last thing I didn't
>>>> change)
>>>>
>>>> Greetz
>>>>
>>>> Stefan
>>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: Update 404 Apache to 5.0
Posted by Maxim Solodovnik <so...@gmail.com>.
You MUST have huge stack-trace in the log in this case .....
On Mon, 15 Apr 2019 at 12:47, Stefan Kühl <st...@quatrekuehl.eu> wrote:
> Hey ;-)
>
> could it be so easy?
>
> Unfortunately not:
>
>
>
>
> Am 15.04.2019 07:15, schrieb Maxim Solodovnik:
>
> "No hint for MySql connection" === no errors, everything works as expected
> :)))
> Old driver will not work (unless you will change class name)
>
> On Mon, 15 Apr 2019 at 12:14, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
>> Hey Maxim,
>>
>> as I wrote, I've tried the newest java-connector (and to be sure also the
>> old one ;-))
>>
>> Here my openmeetingslog from the last try:
>>
>> INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root
>> WebApplicationContext: initialization started
>> INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415 [main]
>> - Initialized JPA EntityManagerFactory for persistence unit 'openmeetings'
>> INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] -
>> Initializing ExecutorService 'taskExecutor'
>> INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191
>> [rbeatExec-e1-t0] - [KurentoClient] Connecting native client
>> INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220
>> [rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
>> INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234
>> [ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will
>> create new handler too!
>> WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308
>> [rbeatExec-e1-t0] - [KurentoClient] Trying to close a
>> JsonRpcClientNettyWebSocket with channel == null
>> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] -
>> [KurentoClient] Error sending heartbeat to server. Exception:
>> [KurentoClient] Exception connecting to WebSocket server ws://
>> 127.0.0.1:8888/kurento
>> INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main] -
>> [KurentoClient] Connecting native client
>> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] -
>> [KurentoClient] Stopping heartbeat and closing client: failure during
>> heartbeat mechanism
>> INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main] -
>> [KurentoClient] Creating new NioEventLoopGroup
>> INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234
>> [ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will
>> create new handler too!
>> WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main] -
>> [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel
>> == null
>> WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to
>> create Kurento client, will re-try in 10000 ms
>> INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using
>> default implementation for ThreadExecutor
>> INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] -
>> Initialized Scheduler Signaller of type: class
>> org.quartz.core.SchedulerSignalerImpl
>> INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz
>> Scheduler v.2.2.0 created.
>> INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore
>> initialized.
>> INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler
>> meta-data: Quartz Scheduler (v2.2.0)
>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10 threads.
>> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support
>> persistence. and is not clustered.
>>
>> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz
>> scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0'
>> initialized from an externally provided properties instance.
>> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz
>> scheduler version: 2.2.0
>> INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory
>> set to: org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
>> INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] -
>> Starting Quartz Scheduler now
>> INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler
>> org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED
>> started.
>> INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root
>> WebApplicationContext initialized in 7740 ms
>> INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url
>> mapping found for filter with name OpenmeetingsApplication: [/*]
>> INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init: Wicket jQuery UI initializer
>> INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init: Wicket core library initializer
>> INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init:
>> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
>> INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init: Wicket extensions initializer
>> INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init: Wicket Kendo UI initializer
>> INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init: DevUtils DebugBar Initializer
>> INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
>> INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] -
>> [OpenmeetingsApplication] init: Wicket Kendo UI initializer (theme-default)
>> DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] -
>> Application::init
>> DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath :
>> /opt/open500/webapps/openmeetings
>> WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: max.upload.size
>> WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: crypt.class.name
>> WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: application.name
>> WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: default.lang.id
>> WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: application.base.url
>> WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: sip.enable
>> WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: google.analytics.code
>> WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mp4.audio.rate
>> WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mp4.audio.bitrate
>> WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mp4.video.preset
>> WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: default.timezone
>> WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: rest.allow.origin
>> WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: video.arrange.keycode
>> WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mute.others.keycode
>> DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] -
>> getInstanceOfCrypt:: configKeyCryptClassName: null
>> WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mute.keycode
>> WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: cam.fps
>> WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mic.rate
>> WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mic.echo.cancellation
>> WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: mic.noise.suppression
>> WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: user.login.minimum.length
>> WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: user.login.minimum.length
>> WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: default.group.id
>> WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: sip.exten.context
>> WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: user.fname.minimum.length
>> WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: user.lname.minimum.length
>> WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: chat.send.on.enter
>> WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: allow.frontend.register
>> WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: allow.soap.register
>> WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: allow.oauth.register
>> WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: send.email.with.verfication
>> WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: send.email.at.register
>> WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: header.csp.frame.options
>> WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: header.content.security.policy
>> WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: chrome.sharing.ext.url
>> WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: display.name.editable
>> WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
>> not find key in configurations: external.process.ttl
>> DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
>>
>> ################################################################################
>> # Openmeetings is
>> up #
>> # 5.0.0-M1 c88fce9
>> 2019-03-29T14:46:44Z #
>> # and ready to
>> use #
>>
>> ################################################################################
>>
>> INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] -
>> [OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT mode
>> INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /
>> INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService
>> from class org.apache.openmeetings.webservice.CalendarWebService
>> INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /CalendarService
>> INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService
>> from class org.apache.openmeetings.webservice.ErrorWebService
>> INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /ErrorService
>> INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService
>> from class org.apache.openmeetings.webservice.GroupWebService
>> INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /GroupService
>> INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService
>> from class org.apache.openmeetings.webservice.InfoWebService
>> INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /InfoService
>> INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService
>> from class org.apache.openmeetings.webservice.FileWebService
>> INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191
>> [pool-1-thread-1] - [KurentoClient] Connecting native client
>> INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220
>> [pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
>> INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234
>> [ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will
>> create new handler too!
>> WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308
>> [pool-1-thread-1] - [KurentoClient] Trying to close a
>> JsonRpcClientNettyWebSocket with channel == null
>> WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] -
>> Fail to create Kurento client, will re-try in 10000 ms
>> WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] -
>> [KurentoClient] Error sending heartbeat to server. Exception:
>> InterruptedException while trying to acquire lock
>> WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] -
>> [KurentoClient] Stopping heartbeat and closing client: failure during
>> heartbeat mechanism
>> INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /FileService
>> INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService
>> from class org.apache.openmeetings.webservice.RecordingWebService
>> INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /RecordService
>> INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService
>> from class org.apache.openmeetings.webservice.RoomWebService
>> INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /RoomService
>> INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
>> [main] - Creating Service {
>> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService
>> from class org.apache.openmeetings.webservice.UserWebService
>> INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the
>> server's publish address to be /UserService
>> INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
>> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy: Wicket core library initializer
>> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy:
>> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy: Wicket extensions initializer
>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
>> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
>> INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] -
>> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
>> (theme-default)
>>
>>
>> No hint for the mysql connection (maybe I'm blind ;-))
>>
>> If you mention the time zone in the connection string, you tlak about the
>> persistense.xml and the values of the connectionstring, right?
>>
>> Greetz Stefan
>>
>> Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
>>
>> Hello,
>>
>> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the time
>> of writing):
>> https://mvnrepository.com/artifact/mysql/mysql-connector-java
>> Also please check openmeetings.log and ensure what the exact error is
>> being reported while connecting
>> (you might need to add server time zone to connection string ....)
>>
>> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>>
>>> Good Morning @all,
>>>
>>> I'm sorry and don't wanna create a messenger out of this list, but the
>>> problem is still present.
>>> To make a clear summary:
>>>
>>> The host is a VPS with 4 core and 12GB RAM, running under an
>>> "up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2
>>> Webserver.
>>> The former installation of OM was an 4.0.4., running well (but with
>>> flash). My steps to upgrade to OM5 were the following:
>>>
>>> 1. Delete folder with existing installtion of OM (backup not nessecary,
>>> no files, just a few users)
>>>
>>> 2. Drop Database
>>>
>>> 3. Create new Database (tried same name first, later on tried different
>>> names)
>>>
>>> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>>>
>>> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>>>
>>> 6. Running Web-Installer
>>>
>>> Facing Problem that the mysql settings not work. Error:
>>>
>>> Could not create connection to database server. Attempted reconnect 3
>>> times. Giving up. (second page web-installer)
>>>
>>> Credentials are correct and worked fine via cli!
>>>
>>> Additional steps I've tried:
>>>
>>> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8
>>> is installed),
>>> tried both java connectors (version 5.x and 8.x),
>>> reinstall mariadb-server,
>>> drop databases und recreate,
>>> copy mysql-persistence.xml with valid database and credentials,
>>> ...
>>>
>>> Something strange: When stopped and leave the web-installer in step 2
>>> (Database settings) I receive a "redirection error" if I try to restart the
>>> web-installer?!
>>>
>>> Ok, so far....any ideas?
>>>
>>> Maybe a problem of Apache2? (no idea why, but the last thing I didn't
>>> change)
>>>
>>> Greetz
>>>
>>> Stefan
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
>
--
WBR
Maxim aka solomax
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Hey ;-)
could it be so easy?
Unfortunately not:
Am 15.04.2019 07:15, schrieb Maxim Solodovnik:
> "No hint for MySql connection" === no errors, everything works as expected :)))
> Old driver will not work (unless you will change class name)
>
> On Mon, 15 Apr 2019 at 12:14, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Hey Maxim,
>
> as I wrote, I've tried the newest java-connector (and to be sure also the old one ;-))
>
> Here my openmeetingslog from the last try:
>
> INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root WebApplicationContext: initialization started
> INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415 [main] - Initialized JPA EntityManagerFactory for persistence unit 'openmeetings'
> INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] - Initializing ExecutorService 'taskExecutor'
> INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191 [rbeatExec-e1-t0] - [KurentoClient] Connecting native client
> INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220 [rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308 [rbeatExec-e1-t0] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] - [KurentoClient] Error sending heartbeat to server. Exception: [KurentoClient] Exception connecting to WebSocket server ws://127.0.0.1:8888/kurento [1]
> INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main] - [KurentoClient] Connecting native client
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] - [KurentoClient] Stopping heartbeat and closing client: failure during heartbeat mechanism
> INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to create Kurento client, will re-try in 10000 ms
> INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using default implementation for ThreadExecutor
> INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
> INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz Scheduler v.2.2.0 created.
> INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore initialized.
> INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler meta-data: Quartz Scheduler (v2.2.0) 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10 threads.
> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
>
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' initialized from an externally provided properties instance.
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz scheduler version: 2.2.0
> INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory set to: org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
> INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] - Starting Quartz Scheduler now
> INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED started.
> INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root WebApplicationContext initialized in 7740 ms
> INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url mapping found for filter with name OpenmeetingsApplication: [/*]
> INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket jQuery UI initializer
> INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket core library initializer
> INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket extensions initializer
> INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket Kendo UI initializer
> INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: DevUtils DebugBar Initializer
> INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] - [OpenmeetingsApplication] init: Wicket Kendo UI initializer (theme-default)
> DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] - Application::init
> DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath : /opt/open500/webapps/openmeetings
> WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: max.upload.size
> WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: crypt.class.name [2]
> WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: application.name [3]
> WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.lang.id [4]
> WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: application.base.url
> WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: sip.enable
> WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: google.analytics.code
> WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.audio.rate
> WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.audio.bitrate
> WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mp4.video.preset
> WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.timezone
> WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: rest.allow.origin
> WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: video.arrange.keycode
> WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mute.others.keycode
> DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] - getInstanceOfCrypt:: configKeyCryptClassName: null
> WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mute.keycode
> WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: cam.fps
> WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.rate
> WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.echo.cancellation
> WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: mic.noise.suppression
> WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: default.group.id [5]
> WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: sip.exten.context
> WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.fname.minimum.length
> WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: user.lname.minimum.length
> WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: chat.send.on.enter
> WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.frontend.register
> WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.soap.register
> WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: allow.oauth.register
> WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: send.email.with.verfication
> WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: send.email.at.register
> WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: header.csp.frame.options
> WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: header.content.security.policy
> WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: chrome.sharing.ext.url
> WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: display.name.editable
> WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could not find key in configurations: external.process.ttl
> DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
> ################################################################################
> # Openmeetings is up #
> # 5.0.0-M1 c88fce9 2019-03-29T14:46:44Z #
> # and ready to use #
> ################################################################################
>
> INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] - [OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT mode
> INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /
> INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService [6] from class org.apache.openmeetings.webservice.CalendarWebService
> INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /CalendarService
> INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService [7] from class org.apache.openmeetings.webservice.ErrorWebService
> INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /ErrorService
> INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService [8] from class org.apache.openmeetings.webservice.GroupWebService
> INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /GroupService
> INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService [9] from class org.apache.openmeetings.webservice.InfoWebService
> INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /InfoService
> INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService [10] from class org.apache.openmeetings.webservice.FileWebService
> INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191 [pool-1-thread-1] - [KurentoClient] Connecting native client
> INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220 [pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234 [ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will create new handler too!
> WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308 [pool-1-thread-1] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create Kurento client, will re-try in 10000 ms
> WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] - [KurentoClient] Error sending heartbeat to server. Exception: InterruptedException while trying to acquire lock
> WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] - [KurentoClient] Stopping heartbeat and closing client: failure during heartbeat mechanism
> INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /FileService
> INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService [11] from class org.apache.openmeetings.webservice.RecordingWebService
> INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /RecordService
> INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService [12] from class org.apache.openmeetings.webservice.RoomWebService
> INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /RoomService
> INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437 [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService [13] from class org.apache.openmeetings.webservice.UserWebService
> INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the server's publish address to be /UserService
> INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket core library initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket extensions initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] - [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer (theme-default)
>
> No hint for the mysql connection (maybe I'm blind ;-))
>
> If you mention the time zone in the connection string, you tlak about the persistense.xml and the values of the connectionstring, right?
>
> Greetz Stefan
>
> Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
> Hello,
>
> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the time of writing): https://mvnrepository.com/artifact/mysql/mysql-connector-java
> Also please check openmeetings.log and ensure what the exact error is being reported while connecting
> (you might need to add server time zone to connection string ....)
>
> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
> Good Morning @all,
>
> I'm sorry and don't wanna create a messenger out of this list, but the problem is still present.
> To make a clear summary:
>
> The host is a VPS with 4 core and 12GB RAM, running under an "up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2 Webserver.
> The former installation of OM was an 4.0.4., running well (but with flash). My steps to upgrade to OM5 were the following:
>
> 1. Delete folder with existing installtion of OM (backup not nessecary, no files, just a few users)
>
> 2. Drop Database
>
> 3. Create new Database (tried same name first, later on tried different names)
>
> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>
> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>
> 6. Running Web-Installer
>
> Facing Problem that the mysql settings not work. Error:
>
> Could not create connection to database server. Attempted reconnect 3 times. Giving up. (second page web-installer)
>
> Credentials are correct and worked fine via cli!
>
> Additional steps I've tried:
>
> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8 is installed),
> tried both java connectors (version 5.x and 8.x),
> reinstall mariadb-server,
> drop databases und recreate,
> copy mysql-persistence.xml with valid database and credentials,
> ...
>
> Something strange: When stopped and leave the web-installer in step 2 (Database settings) I receive a "redirection error" if I try to restart the web-installer?!
>
> Ok, so far....any ideas?
>
> Maybe a problem of Apache2? (no idea why, but the last thing I didn't change)
>
> Greetz
>
> Stefan
> --
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
Links:
------
[1] http://127.0.0.1:8888/kurento
[2] http://crypt.class.name
[3] http://application.name
[4] http://default.lang.id
[5] http://default.group.id
[6]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.CalendarWebService
[7]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.ErrorWebService
[8]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.GroupWebService
[9]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.InfoWebService
[10]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.FileWebService
[11]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.RecordingWebService
[12]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.RoomWebService
[13]
http://webservice.openmeetings.apache.org/%7Dorg.apache.openmeetings.webservice.UserWebService
Re: Update 404 Apache to 5.0
Posted by Maxim Solodovnik <so...@gmail.com>.
"No hint for MySql connection" === no errors, everything works as expected
:)))
Old driver will not work (unless you will change class name)
On Mon, 15 Apr 2019 at 12:14, Stefan Kühl <st...@quatrekuehl.eu> wrote:
> Hey Maxim,
>
> as I wrote, I've tried the newest java-connector (and to be sure also the
> old one ;-))
>
> Here my openmeetingslog from the last try:
>
> INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root
> WebApplicationContext: initialization started
> INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415 [main]
> - Initialized JPA EntityManagerFactory for persistence unit 'openmeetings'
> INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] -
> Initializing ExecutorService 'taskExecutor'
> INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191
> [rbeatExec-e1-t0] - [KurentoClient] Connecting native client
> INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220
> [rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234
> [ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will
> create new handler too!
> WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308
> [rbeatExec-e1-t0] - [KurentoClient] Trying to close a
> JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] -
> [KurentoClient] Error sending heartbeat to server. Exception:
> [KurentoClient] Exception connecting to WebSocket server ws://
> 127.0.0.1:8888/kurento
> INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main] -
> [KurentoClient] Connecting native client
> WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] -
> [KurentoClient] Stopping heartbeat and closing client: failure during
> heartbeat mechanism
> INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main] -
> [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234
> [ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will
> create new handler too!
> WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main] -
> [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel
> == null
> WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to
> create Kurento client, will re-try in 10000 ms
> INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using
> default implementation for ThreadExecutor
> INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] -
> Initialized Scheduler Signaller of type: class
> org.quartz.core.SchedulerSignalerImpl
> INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz
> Scheduler v.2.2.0 created.
> INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore
> initialized.
> INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler
> meta-data: Quartz Scheduler (v2.2.0)
> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10 threads.
> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support
> persistence. and is not clustered.
>
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz
> scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0'
> initialized from an externally provided properties instance.
> INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz
> scheduler version: 2.2.0
> INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory
> set to: org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
> INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] -
> Starting Quartz Scheduler now
> INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler
> org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED
> started.
> INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root
> WebApplicationContext initialized in 7740 ms
> INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url
> mapping found for filter with name OpenmeetingsApplication: [/*]
> INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init: Wicket jQuery UI initializer
> INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init: Wicket core library initializer
> INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init:
> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init: Wicket extensions initializer
> INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init: Wicket Kendo UI initializer
> INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init: DevUtils DebugBar Initializer
> INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] -
> [OpenmeetingsApplication] init: Wicket Kendo UI initializer (theme-default)
> DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] -
> Application::init
> DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath :
> /opt/open500/webapps/openmeetings
> WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: max.upload.size
> WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: crypt.class.name
> WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: application.name
> WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: default.lang.id
> WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: application.base.url
> WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: sip.enable
> WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: google.analytics.code
> WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mp4.audio.rate
> WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mp4.audio.bitrate
> WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mp4.video.preset
> WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: default.timezone
> WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: rest.allow.origin
> WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: video.arrange.keycode
> WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mute.others.keycode
> DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] -
> getInstanceOfCrypt:: configKeyCryptClassName: null
> WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mute.keycode
> WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: cam.fps
> WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mic.rate
> WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mic.echo.cancellation
> WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: mic.noise.suppression
> WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: user.login.minimum.length
> WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: default.group.id
> WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: sip.exten.context
> WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: user.fname.minimum.length
> WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: user.lname.minimum.length
> WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: chat.send.on.enter
> WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: allow.frontend.register
> WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: allow.soap.register
> WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: allow.oauth.register
> WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: send.email.with.verfication
> WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: send.email.at.register
> WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: header.csp.frame.options
> WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: header.content.security.policy
> WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: chrome.sharing.ext.url
> WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: display.name.editable
> WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
> not find key in configurations: external.process.ttl
> DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
>
> ################################################################################
> # Openmeetings is
> up #
> # 5.0.0-M1 c88fce9
> 2019-03-29T14:46:44Z #
> # and ready to
> use #
>
> ################################################################################
>
> INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] -
> [OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT mode
> INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /
> INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService
> from class org.apache.openmeetings.webservice.CalendarWebService
> INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /CalendarService
> INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService
> from class org.apache.openmeetings.webservice.ErrorWebService
> INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /ErrorService
> INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService
> from class org.apache.openmeetings.webservice.GroupWebService
> INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /GroupService
> INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService
> from class org.apache.openmeetings.webservice.InfoWebService
> INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /InfoService
> INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService
> from class org.apache.openmeetings.webservice.FileWebService
> INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191
> [pool-1-thread-1] - [KurentoClient] Connecting native client
> INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220
> [pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
> INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234
> [ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will
> create new handler too!
> WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308
> [pool-1-thread-1] - [KurentoClient] Trying to close a
> JsonRpcClientNettyWebSocket with channel == null
> WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] -
> Fail to create Kurento client, will re-try in 10000 ms
> WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] -
> [KurentoClient] Error sending heartbeat to server. Exception:
> InterruptedException while trying to acquire lock
> WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] -
> [KurentoClient] Stopping heartbeat and closing client: failure during
> heartbeat mechanism
> INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /FileService
> INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService
> from class org.apache.openmeetings.webservice.RecordingWebService
> INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /RecordService
> INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService
> from class org.apache.openmeetings.webservice.RoomWebService
> INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /RoomService
> INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
> [main] - Creating Service {
> http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService
> from class org.apache.openmeetings.webservice.UserWebService
> INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /UserService
> INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy: Wicket core library initializer
> INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy:
> org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy: Wicket extensions initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
> INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy: Wicket jQuery UI initializer (plugins)
> INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] -
> [OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
> (theme-default)
>
>
> No hint for the mysql connection (maybe I'm blind ;-))
>
> If you mention the time zone in the connection string, you tlak about the
> persistense.xml and the values of the connectionstring, right?
>
> Greetz Stefan
>
> Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
>
> Hello,
>
> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the time
> of writing): https://mvnrepository.com/artifact/mysql/mysql-connector-java
> Also please check openmeetings.log and ensure what the exact error is
> being reported while connecting
> (you might need to add server time zone to connection string ....)
>
> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
>> Good Morning @all,
>>
>> I'm sorry and don't wanna create a messenger out of this list, but the
>> problem is still present.
>> To make a clear summary:
>>
>> The host is a VPS with 4 core and 12GB RAM, running under an "up-to-date"
>> Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2 Webserver.
>> The former installation of OM was an 4.0.4., running well (but with
>> flash). My steps to upgrade to OM5 were the following:
>>
>> 1. Delete folder with existing installtion of OM (backup not nessecary,
>> no files, just a few users)
>>
>> 2. Drop Database
>>
>> 3. Create new Database (tried same name first, later on tried different
>> names)
>>
>> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>>
>> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>>
>> 6. Running Web-Installer
>>
>> Facing Problem that the mysql settings not work. Error:
>>
>> Could not create connection to database server. Attempted reconnect 3
>> times. Giving up. (second page web-installer)
>>
>> Credentials are correct and worked fine via cli!
>>
>> Additional steps I've tried:
>>
>> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8
>> is installed),
>> tried both java connectors (version 5.x and 8.x),
>> reinstall mariadb-server,
>> drop databases und recreate,
>> copy mysql-persistence.xml with valid database and credentials,
>> ...
>>
>> Something strange: When stopped and leave the web-installer in step 2
>> (Database settings) I receive a "redirection error" if I try to restart the
>> web-installer?!
>>
>> Ok, so far....any ideas?
>>
>> Maybe a problem of Apache2? (no idea why, but the last thing I didn't
>> change)
>>
>> Greetz
>>
>> Stefan
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>
--
WBR
Maxim aka solomax
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Hey Maxim,
as I wrote, I've tried the newest java-connector (and to be sure also
the old one ;-))
Here my openmeetingslog from the last try:
INFO 04-14 19:19:44.180 o.s.w.c.ContextLoader:270 [main] - Root
WebApplicationContext: initialization started
INFO 04-14 19:19:46.138 o.s.o.j.LocalEntityManagerFactoryBean:415
[main] - Initialized JPA EntityManagerFactory for persistence unit
'openmeetings'
INFO 04-14 19:19:46.809 o.s.s.c.ThreadPoolTaskExecutor:171 [main] -
Initializing ExecutorService 'taskExecutor'
INFO 04-14 19:19:50.427 o.k.j.c.JsonRpcClientNettyWebSocket:191
[rbeatExec-e1-t0] - [KurentoClient] Connecting native client
INFO 04-14 19:19:50.443 o.k.j.c.JsonRpcClientNettyWebSocket:220
[rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
INFO 04-14 19:19:51.126 o.k.j.c.JsonRpcClientNettyWebSocket:234
[ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel. Will
create new handler too!
WARN 04-14 19:19:51.298 o.k.j.c.JsonRpcClientNettyWebSocket:308
[rbeatExec-e1-t0] - [KurentoClient] Trying to close a
JsonRpcClientNettyWebSocket with channel == null
WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:270 [rbeatExec-e1-t0] -
[KurentoClient] Error sending heartbeat to server. Exception:
[KurentoClient] Exception connecting to WebSocket server
ws://127.0.0.1:8888/kurento
INFO 04-14 19:19:51.306 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main]
- [KurentoClient] Connecting native client
WARN 04-14 19:19:51.306 o.k.j.c.JsonRpcClient:287 [rbeatExec-e1-t0] -
[KurentoClient] Stopping heartbeat and closing client: failure during
heartbeat mechanism
INFO 04-14 19:19:51.307 o.k.j.c.JsonRpcClientNettyWebSocket:220 [main]
- [KurentoClient] Creating new NioEventLoopGroup
INFO 04-14 19:19:51.310 o.k.j.c.JsonRpcClientNettyWebSocket:234
[ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel. Will
create new handler too!
WARN 04-14 19:19:51.313 o.k.j.c.JsonRpcClientNettyWebSocket:308 [main]
- [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with
channel == null
WARN 04-14 19:19:51.325 o.a.o.c.r.KurentoHandler:124 [main] - Fail to
create Kurento client, will re-try in 10000 ms
INFO 04-14 19:19:51.834 o.q.i.StdSchedulerFactory:1184 [main] - Using
default implementation for ThreadExecutor
INFO 04-14 19:19:51.869 o.q.c.SchedulerSignalerImpl:61 [main] -
Initialized Scheduler Signaller of type: class
org.quartz.core.SchedulerSignalerImpl
INFO 04-14 19:19:51.872 o.q.c.QuartzScheduler:249 [main] - Quartz
Scheduler v.2.2.0 created.
INFO 04-14 19:19:51.874 o.q.s.RAMJobStore:155 [main] - RAMJobStore
initialized.
INFO 04-14 19:19:51.875 o.q.c.QuartzScheduler:318 [main] - Scheduler
meta-data: Quartz Scheduler (v2.2.0)
'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' 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 10
threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
support persistence. and is not clustered.
INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1339 [main] - Quartz
scheduler 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0'
initialized from an externally provided properties instance.
INFO 04-14 19:19:51.876 o.q.i.StdSchedulerFactory:1343 [main] - Quartz
scheduler version: 2.2.0
INFO 04-14 19:19:51.878 o.q.c.QuartzScheduler:2346 [main] - JobFactory
set to:
org.springframework.scheduling.quartz.AdaptableJobFactory@5e83677e
INFO 04-14 19:19:51.909 o.s.s.q.SchedulerFactoryBean:726 [main] -
Starting Quartz Scheduler now
INFO 04-14 19:19:51.913 o.q.c.QuartzScheduler:588 [main] - Scheduler
org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED
started.
INFO 04-14 19:19:51.926 o.s.w.c.ContextLoader:306 [main] - Root
WebApplicationContext initialized in 7740 ms
INFO 04-14 19:19:51.947 o.a.w.u.f.WebXmlFile:235 [main] - web.xml: url
mapping found for filter with name OpenmeetingsApplication: [/*]
INFO 04-14 19:19:52.081 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init: Wicket jQuery UI initializer
INFO 04-14 19:19:52.083 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init: Wicket core library initializer
INFO 04-14 19:19:52.087 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init:
org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
INFO 04-14 19:19:52.447 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init: Wicket extensions initializer
INFO 04-14 19:19:52.473 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init: Wicket Kendo UI initializer
INFO 04-14 19:19:52.475 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init: DevUtils DebugBar Initializer
INFO 04-14 19:19:52.477 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init: Wicket jQuery UI initializer (plugins)
INFO 04-14 19:19:52.478 o.a.w.Application:569 [main] -
[OpenmeetingsApplication] init: Wicket Kendo UI initializer
(theme-default)
DEBUG 04-14 19:19:52.775 o.a.o.w.a.Application:291 [main] -
Application::init
DEBUG 04-14 19:19:52.832 o.a.o.w.a.Application:298 [main] - webAppPath :
/opt/open500/webapps/openmeetings
WARN 04-14 19:19:57.944 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: max.upload.size
WARN 04-14 19:19:57.948 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: crypt.class.name
WARN 04-14 19:19:57.950 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: application.name
WARN 04-14 19:19:57.951 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: default.lang.id
WARN 04-14 19:19:57.967 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: application.base.url
WARN 04-14 19:19:57.968 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: sip.enable
WARN 04-14 19:19:57.969 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: google.analytics.code
WARN 04-14 19:19:57.971 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mp4.audio.rate
WARN 04-14 19:19:57.973 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mp4.audio.bitrate
WARN 04-14 19:19:57.974 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mp4.video.preset
WARN 04-14 19:19:57.976 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: default.timezone
WARN 04-14 19:19:57.978 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: rest.allow.origin
WARN 04-14 19:19:57.980 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: video.arrange.keycode
WARN 04-14 19:19:57.982 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mute.others.keycode
DEBUG 04-14 19:19:57.983 o.a.o.u.c.CryptProvider:38 [Bean#0_Worker-8] -
getInstanceOfCrypt:: configKeyCryptClassName: null
WARN 04-14 19:19:57.985 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mute.keycode
WARN 04-14 19:19:57.987 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: cam.fps
WARN 04-14 19:19:57.989 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mic.rate
WARN 04-14 19:19:57.990 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mic.echo.cancellation
WARN 04-14 19:19:57.992 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: mic.noise.suppression
WARN 04-14 19:19:57.999 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: user.login.minimum.length
WARN 04-14 19:19:58.001 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: user.login.minimum.length
WARN 04-14 19:19:58.002 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: default.group.id
WARN 04-14 19:19:58.004 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: sip.exten.context
WARN 04-14 19:19:58.006 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: user.fname.minimum.length
WARN 04-14 19:19:58.007 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: user.lname.minimum.length
WARN 04-14 19:19:58.009 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: chat.send.on.enter
WARN 04-14 19:19:58.011 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: allow.frontend.register
WARN 04-14 19:19:58.013 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: allow.soap.register
WARN 04-14 19:19:58.014 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: allow.oauth.register
WARN 04-14 19:19:58.018 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: send.email.with.verfication
WARN 04-14 19:19:58.020 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: send.email.at.register
WARN 04-14 19:19:58.022 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: header.csp.frame.options
WARN 04-14 19:19:58.023 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: header.content.security.policy
WARN 04-14 19:19:58.025 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: chrome.sharing.ext.url
WARN 04-14 19:19:58.026 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: display.name.editable
WARN 04-14 19:19:58.033 o.a.o.d.d.b.ConfigurationDao:199 [main] - Could
not find key in configurations: external.process.ttl
DEBUG 04-14 19:19:58.035 o.a.o.u.Version:82 [main] -
################################################################################
# Openmeetings is up
#
# 5.0.0-M1 c88fce9 2019-03-29T14:46:44Z
#
# and ready to use
#
################################################################################
INFO 04-14 19:19:58.165 o.a.w.p.h.WebApplication:935 [main] -
[OpenmeetingsApplication] Started Wicket version 8.3.0 in DEPLOYMENT
mode
INFO 04-14 19:19:59.134 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /
INFO 04-14 19:19:59.349 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService
from class org.apache.openmeetings.webservice.CalendarWebService
INFO 04-14 19:20:00.765 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /CalendarService
INFO 04-14 19:20:00.780 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService
from class org.apache.openmeetings.webservice.ErrorWebService
INFO 04-14 19:20:00.815 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /ErrorService
INFO 04-14 19:20:00.818 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService
from class org.apache.openmeetings.webservice.GroupWebService
INFO 04-14 19:20:00.973 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /GroupService
INFO 04-14 19:20:00.976 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService
from class org.apache.openmeetings.webservice.InfoWebService
INFO 04-14 19:20:01.090 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /InfoService
INFO 04-14 19:20:01.100 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService
from class org.apache.openmeetings.webservice.FileWebService
INFO 04-14 19:20:01.337 o.k.j.c.JsonRpcClientNettyWebSocket:191
[pool-1-thread-1] - [KurentoClient] Connecting native client
INFO 04-14 19:20:01.338 o.k.j.c.JsonRpcClientNettyWebSocket:220
[pool-1-thread-1] - [KurentoClient] Creating new NioEventLoopGroup
INFO 04-14 19:20:01.400 o.k.j.c.JsonRpcClientNettyWebSocket:234
[ntLoopGroup-4-1] - [KurentoClient] Initiating new Netty channel. Will
create new handler too!
WARN 04-14 19:20:01.419 o.k.j.c.JsonRpcClientNettyWebSocket:308
[pool-1-thread-1] - [KurentoClient] Trying to close a
JsonRpcClientNettyWebSocket with channel == null
WARN 04-14 19:20:01.469 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1]
- Fail to create Kurento client, will re-try in 10000 ms
WARN 04-14 19:20:01.480 o.k.j.c.JsonRpcClient:270 [rbeatExec-e5-t0] -
[KurentoClient] Error sending heartbeat to server. Exception:
InterruptedException while trying to acquire lock
WARN 04-14 19:20:01.481 o.k.j.c.JsonRpcClient:287 [rbeatExec-e5-t0] -
[KurentoClient] Stopping heartbeat and closing client: failure during
heartbeat mechanism
INFO 04-14 19:20:01.493 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /FileService
INFO 04-14 19:20:01.502 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService
from class org.apache.openmeetings.webservice.RecordingWebService
INFO 04-14 19:20:01.704 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /RecordService
INFO 04-14 19:20:01.707 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService
from class org.apache.openmeetings.webservice.RoomWebService
INFO 04-14 19:20:02.272 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /RoomService
INFO 04-14 19:20:02.275 o.a.c.w.s.f.ReflectionServiceFactoryBean:437
[main] - Creating Service
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService
from class org.apache.openmeetings.webservice.UserWebService
INFO 04-14 19:20:02.395 o.a.c.e.ServerImpl:94 [main] - Setting the
server's publish address to be /UserService
INFO 04-14 19:20:03.404 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy: Wicket core library initializer
INFO 04-14 19:20:03.405 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy:
org.wicketstuff.dashboard.DashboardContextInitializer@75c880f1
INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy: Wicket extensions initializer
INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy: DevUtils DebugBar Initializer
INFO 04-14 19:20:03.406 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy: Wicket jQuery UI initializer
(plugins)
INFO 04-14 19:20:03.407 o.a.w.Application:550 [main] -
[OpenmeetingsApplication] destroy: Wicket Kendo UI initializer
(theme-default)
No hint for the mysql connection (maybe I'm blind ;-))
If you mention the time zone in the connection string, you tlak about
the persistense.xml and the values of the connectionstring, right?
Greetz Stefan
Am 15.04.2019 06:49, schrieb Maxim Solodovnik:
> Hello,
>
> for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the time of writing): https://mvnrepository.com/artifact/mysql/mysql-connector-java
> Also please check openmeetings.log and ensure what the exact error is being reported while connecting
> (you might need to add server time zone to connection string ....)
>
> On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
>
>> Good Morning @all,
>>
>> I'm sorry and don't wanna create a messenger out of this list, but the problem is still present.
>> To make a clear summary:
>>
>> The host is a VPS with 4 core and 12GB RAM, running under an "up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2 Webserver.
>> The former installation of OM was an 4.0.4., running well (but with flash). My steps to upgrade to OM5 were the following:
>>
>> 1. Delete folder with existing installtion of OM (backup not nessecary, no files, just a few users)
>>
>> 2. Drop Database
>>
>> 3. Create new Database (tried same name first, later on tried different names)
>>
>> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>>
>> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>>
>> 6. Running Web-Installer
>>
>> Facing Problem that the mysql settings not work. Error:
>>
>> Could not create connection to database server. Attempted reconnect 3 times. Giving up. (second page web-installer)
>>
>> Credentials are correct and worked fine via cli!
>>
>> Additional steps I've tried:
>>
>> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8 is installed),
>> tried both java connectors (version 5.x and 8.x),
>> reinstall mariadb-server,
>> drop databases und recreate,
>> copy mysql-persistence.xml with valid database and credentials,
>> ...
>>
>> Something strange: When stopped and leave the web-installer in step 2 (Database settings) I receive a "redirection error" if I try to restart the web-installer?!
>>
>> Ok, so far....any ideas?
>>
>> Maybe a problem of Apache2? (no idea why, but the last thing I didn't change)
>>
>> Greetz
>>
>> Stefan
>
> --
> WBR
> Maxim aka solomax
Re: Update 404 Apache to 5.0
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello,
for 5.0.0-M1 you need to use latest MySql java driver (8.0.15 at the time
of writing): https://mvnrepository.com/artifact/mysql/mysql-connector-java
Also please check openmeetings.log and ensure what the exact error is being
reported while connecting
(you might need to add server time zone to connection string ....)
On Mon, 15 Apr 2019 at 11:34, Stefan Kühl <st...@quatrekuehl.eu> wrote:
> Good Morning @all,
>
> I'm sorry and don't wanna create a messenger out of this list, but the
> problem is still present.
> To make a clear summary:
>
> The host is a VPS with 4 core and 12GB RAM, running under an "up-to-date"
> Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2 Webserver.
> The former installation of OM was an 4.0.4., running well (but with
> flash). My steps to upgrade to OM5 were the following:
>
> 1. Delete folder with existing installtion of OM (backup not nessecary, no
> files, just a few users)
>
> 2. Drop Database
>
> 3. Create new Database (tried same name first, later on tried different
> names)
>
> 4. Unzip OM 5 in the folder (same procedure: same name first...)
>
> 5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
>
> 6. Running Web-Installer
>
> Facing Problem that the mysql settings not work. Error:
>
> Could not create connection to database server. Attempted reconnect 3
> times. Giving up. (second page web-installer)
>
> Credentials are correct and worked fine via cli!
>
> Additional steps I've tried:
>
> reinstall of OM with Tutorial (sparing out the steps Java - version 1.8 is
> installed),
> tried both java connectors (version 5.x and 8.x),
> reinstall mariadb-server,
> drop databases und recreate,
> copy mysql-persistence.xml with valid database and credentials,
> ...
>
> Something strange: When stopped and leave the web-installer in step 2
> (Database settings) I receive a "redirection error" if I try to restart the
> web-installer?!
>
> Ok, so far....any ideas?
>
> Maybe a problem of Apache2? (no idea why, but the last thing I didn't
> change)
>
> Greetz
>
> Stefan
>
--
WBR
Maxim aka solomax
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Good Morning @all,
I'm sorry and don't wanna create a messenger out of this list, but the
problem is still present.
To make a clear summary:
The host is a VPS with 4 core and 12GB RAM, running under an
"up-to-date" Ubuntu 18.04. OS. I am hsting to vHosts using an Apache2
Webserver.
The former installation of OM was an 4.0.4., running well (but with
flash). My steps to upgrade to OM5 were the following:
1. Delete folder with existing installtion of OM (backup not nessecary,
no files, just a few users)
2. Drop Database
3. Create new Database (tried same name first, later on tried different
names)
4. Unzip OM 5 in the folder (same procedure: same name first...)
5. Start OM using the tomcat3 script (folder-names updatet if nessecary)
6. Running Web-Installer
Facing Problem that the mysql settings not work. Error:
Could not create connection to database server. Attempted reconnect 3
times. Giving up. (second page web-installer)
Credentials are correct and worked fine via cli!
Additional steps I've tried:
reinstall of OM with Tutorial (sparing out the steps Java - version 1.8
is installed),
tried both java connectors (version 5.x and 8.x),
reinstall mariadb-server,
drop databases und recreate,
copy mysql-persistence.xml with valid database and credentials,
...
Something strange: When stopped and leave the web-installer in step 2
(Database settings) I receive a "redirection error" if I try to restart
the web-installer?!
Ok, so far....any ideas?
Maybe a problem of Apache2? (no idea why, but the last thing I didn't
change)
Greetz
Stefan
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Did it, no change.
Now i am tryiung something crazy ;-)
copy the local installation of OM5 including mysqldymp of all tables and
put it onto my server.
we will see....
Am 14.04.2019 17:27, schrieb Aaron Hepp:
> Can you drop down to su before running the tomcat3 script?
>
> On 4/14/19 11:04 AM, Stefan Kühl wrote:
>
> I use the newer one, but checked both of them.
>
> I have no idea, it seems like a connection problem concerning rights or something like that.
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 16:43, schrieb Aaron Hepp: Last thing I can think of...which mysql connector are you using? My Ubuntu 16.04 OM5 install is still using the old 5.1.45. I never replaced it with the 5.1.47. If you followed the instructions for the 18.04 OM5 install it is using the 8.0.15. That is if you are using Ubuntu.
>
> The version we have used:
> 4.x
> mysql-connector-java-
> 5.1.47.jar 5.1.45.jar (what I am currently running)
> mysql-connector-java-
> 5.1.47.jar 5.1.47.jar
> 5.x
> mysql-connector-java-
> 5.1.47.jar 8.0.15.jar
>
> On 4/14/19 10:29 AM, Stefan Kühl wrote:
>
> Hello Aaron,
>
> checked the mysql_persistence.xml twice and added the name of the database. Still same problem. mysql is up and running, connection via cli works with given credentials.
> Rebooted, still same error message.
>
> Purged mariadb-server, reinstall it, new database created, nothing.....same error message.
>
> Checked mysql port 3306 -> listening for 127.0.0.1
>
> I'am through.....
>
> Greetz Stefan
>
> Am 14.04.2019 15:16, schrieb Aaron Hepp: I had the same problem but mine was a database that filed to build correctly. So I dropped the database and recreated it.
>
> But 1st I would check your mysql_persistence.xml file (/opt/your_om_install_location/webapps/openmeetings/WEB-INF/classes/META-INF/)
>
> Make sure your database name is defined in the file.
>
> <property name="openjpa.ConnectionProperties" value="DriverClassName=com.mysql.jdbc.Driver , Url=jdbc:mysql://localhost:3306/<DATABASE_NAME>?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true , MaxActive=100 , MaxWait=10000 , TestOnBorrow=true , poolPreparedStatements=true , Username= , Password="/>
>
> On 4/14/19 7:58 AM, Stefan Kühl wrote:
>
> Strange!!
>
> Running the web installer, in the part mysql it says:
>
> Could not create connection to database server. Attempted reconnect 3 times. Giving up.
>
> mariadb-server works fine, all privileges are set. Try different tables. Don't work.
>
> With the old installation it works without problems.
>
> Any ideas?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 13:04, schrieb Stefan Kühl:
>
> yes, got it.
> I use a script to renew my letsencrypt certificates which use also .jks. copy the keystore.jks to keystore and it works. ;-)
>
> Thanks
>
> Am 14.04.2019 12:38, schrieb Aaron Hepp: also note that in OM4 it used keystore.jks where in OM5 it is just keystore. It may not be necessary but I create a new keystore file each time I renew my cert via letsencrypt.
>
> Below is the commands I use to generate the cert and keystore
>
> letsencrypt certonly
> ****with OM not running select 1
> ****enter your domain name example: testom5.net
>
> ****I store my cert and files in a folder called ssl to make it simpler when typing the commands to generate the keystore
> cd /opt/files/ssl
> ****copy the generated cert, key, and root to the ssl folder and rename
> cp /etc/letsencrypt/live/testom5.net/cert.pem /opt/files/ssl/red5.crt
> cp /etc/letsencrypt/live/testom5.net/privkey.pem /opt/files/ssl/red5.key
> cp /etc/letsencrypt/live/testom5.net/fullchain.pem /opt/files/ssl/root.crt
>
> **** delete the existing keystore file (in my example my OM install is in a folder called om5)
> **** also deletes the generated files when creating the keystore (.p12)
> rm /opt/files/ssl/red5.p12
> rm /opt/om5/conf/keystore
>
> ****create new keystore source file (will ask you to create a password which will be used in the creation)
> openssl pkcs12 -export -in red5.crt -inkey red5.key -out red5.p12 -name red5 -certfile root.crt
>
> **** create new keystore (password is the password you used in the above step example: password. This is all one line)
> keytool -importkeystore -srcstorepass password -srckeystore red5.p12 -srcstoretype PKCS12 -deststorepass password -destkeystore /opt/om5/conf/keystore -alias red5
>
> **** add the root certificate (will ask for the password you used in the 1st step)
> keytool -import -alias root -keystore /opt/om5/conf/keystore -trustcacerts -file root.crt
>
> ****your new keystore has now been created. Now the password you used in step one, make sure you change the password in the /opt/om5/conf/server.xml file to match what you used
>
> ****section where password goes
> <Connector port="5443" protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="150" SSLEnabled="true"
> keystoreFile="conf/keystore" keystorePass="password" <-------------
> clientAuth="false" sslProtocol="TLS"/>
>
> There are other ways to accomplish the goal but I found this to be the easiest when trying to explain it via typing.
>
> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>
> Morning,
>
> try to update my 4.0.4 running on apache2 to version 5.0
>
> but I cannot connect to web-installer, because of insecure connection (using HSTS). I copied all the neccessary certifiacte files into the new OM folder. Is there any other differenz I need to take care of in using Apache2 instead of tomcat?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>
> Morning@ everybody,
>
> tested it three times. Installation of kms directly on a 18.04. LTS Ubuntu works very well.
>
> Maybe for Alvaro and his great Tutorials (!) it would be worth to add a paragraph for native installation with the commands:
>
> sudo apt update
> sudo apt install --no-install-recommends --yes gnupg #to be sure that gnupg is installed#
> DISTRO="bionic" #verify the name of the distribution#
> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
> #in the following we are building the kms sources.list#
> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
> # server answers with > #
> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
> EOF
> # server returns to normal prompt #
> sudo apt update && sudo apt install --yes kurento-media-server
>
> ## thats all ##
>
> Greetz
>
> Stefan
>
> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
> Hello All,
>
> recently new Kurento server with native 18.04 support is out [1 [1]]
> So overall installation should be more stable :)
>
> [1] https://www.kurento.org/blog/kurento-610-bionic-support
Links:
------
[1] https://www.kurento.org/blog/kurento-610-bionic-support
Re: Update 404 Apache to 5.0
Posted by Aaron Hepp <aa...@gmail.com>.
Can you drop down to su before running the tomcat3 script?
On 4/14/19 11:04 AM, Stefan Kühl wrote:
>
> I use the newer one, but checked both of them.
>
> I have no idea, it seems like a connection problem concerning rights
> or something like that.
>
> Greetz
>
> Stefan
>
>
> Am 14.04.2019 16:43, schrieb Aaron Hepp:
>
>> Last thing I can think of...which mysql connector are you using? My
>> Ubuntu 16.04 OM5 install is still using the old 5.1.45. I never
>> replaced it with the 5.1.47. If you followed the instructions for
>> the 18.04 OM5 install it is using the 8.0.15. That is if you are
>> using Ubuntu.
>>
>> The version we have used:
>> 4.x
>> mysql-connector-java-
>> 5.1.47.jar
>> 5.1.45.jar (what I am currently running)
>> mysql-connector-java-
>> 5.1.47.jar
>> 5.1.47.jar
>> 5.x
>> mysql-connector-java-
>> 5.1.47.jar
>> 8.0.15.jar
>>
>> On 4/14/19 10:29 AM, Stefan Kühl wrote:
>>>
>>> Hello Aaron,
>>>
>>> checked the mysql_persistence.xml twice and added the name of the
>>> database. Still same problem. mysql is up and running, connection
>>> via cli works with given credentials.
>>> Rebooted, still same error message.
>>>
>>> Purged mariadb-server, reinstall it, new database created,
>>> nothing.....same error message.
>>>
>>> Checked mysql port 3306 -> listening for 127.0.0.1
>>>
>>> I'am through.....
>>>
>>> Greetz Stefan
>>>
>>>
>>> Am 14.04.2019 15:16, schrieb Aaron Hepp:
>>>
>>> I had the same problem but mine was a database that filed to
>>> build correctly. So I dropped the database and recreated it.
>>>
>>> But 1st I would check your mysql_persistence.xml file
>>> (/opt/your_om_install_location/webapps/openmeetings/WEB-INF/classes/META-INF/)
>>>
>>> Make sure your database name is defined in the file.
>>>
>>> <property name="openjpa.ConnectionProperties"
>>> value="DriverClassName=com.mysql.jdbc.Driver ,
>>> Url=jdbc:mysql://localhost:3306/*<database_name>*?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true
>>> , MaxActive=100 , MaxWait=10000 ,
>>> TestOnBorrow=true , poolPreparedStatements=true ,
>>> Username= , Password="/>
>>>
>>>
>>> On 4/14/19 7:58 AM, Stefan Kühl wrote:
>>>
>>> Strange!!
>>>
>>> Running the web installer, in the part mysql it says:
>>>
>>> Could not create connection to database server. Attempted
>>> reconnect 3 times. Giving up.
>>>
>>> mariadb-server works fine, all privileges are set. Try
>>> different tables. Don't work.
>>>
>>> With the old installation it works without problems.
>>>
>>> Any ideas?
>>>
>>> Greetz
>>>
>>> Stefan
>>>
>>>
>>> Am 14.04.2019 13:04, schrieb Stefan Kühl:
>>>
>>> yes, got it.
>>> I use a script to renew my letsencrypt certificates
>>> which use also .jks. copy the keystore.jks to keystore
>>> and it works. ;-)
>>>
>>> Thanks
>>>
>>>
>>>
>>> Am 14.04.2019 12:38, schrieb Aaron Hepp:
>>>
>>> also note that in OM4 it used keystore.jks where in
>>> OM5 it is just keystore. It may not be necessary
>>> but I create a new keystore file each time I renew
>>> my cert via letsencrypt.
>>>
>>> Below is the commands I use to generate the cert and
>>> keystore
>>>
>>> letsencrypt certonly
>>> ****with OM not running select 1
>>> ****enter your domain name example: testom5.net
>>>
>>> ****I store my cert and files in a folder called ssl
>>> to make it simpler when typing the commands to
>>> generate the keystore
>>> cd /opt/files/ssl
>>> ****copy the generated cert, key, and root to the
>>> ssl folder and rename
>>> cp /etc/letsencrypt/live/testom5.net/cert.pem
>>> /opt/files/ssl/red5.crt
>>> cp /etc/letsencrypt/live/testom5.net/privkey.pem
>>> /opt/files/ssl/red5.key
>>> cp /etc/letsencrypt/live/testom5.net/fullchain.pem
>>> /opt/files/ssl/root.crt
>>>
>>> **** delete the existing keystore file (in my
>>> example my OM install is in a folder called om5)
>>> **** also deletes the generated files when creating
>>> the keystore (.p12)
>>> rm /opt/files/ssl/red5.p12
>>> rm /opt/om5/conf/keystore
>>>
>>> ****create new keystore source file (will ask you to
>>> create a password which will be used in the creation)
>>> openssl pkcs12 -export -in red5.crt -inkey red5.key
>>> -out red5.p12 -name red5 -certfile root.crt
>>>
>>> **** create new keystore (password is the password
>>> you used in the above step example: password. This
>>> is all one line)
>>> keytool -importkeystore -srcstorepass _password
>>> _-srckeystore red5.p12 -srcstoretype PKCS12
>>> -deststorepass_password_ -destkeystore
>>> /opt/om5/conf/keystore -alias red5
>>>
>>> **** add the root certificate (will ask for the
>>> password you used in the 1st step)
>>> keytool -import -alias root -keystore
>>> /opt/om5/conf/keystore -trustcacerts -file root.crt
>>>
>>> ****your new keystore has now been created. Now the
>>> password you used in step one, make sure you change
>>> the password in the /opt/om5/conf/server.xml file to
>>> match what you used
>>>
>>> ****section where password goes
>>> <Connector port="5443"
>>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>>> maxThreads="150" SSLEnabled="true"
>>> keystoreFile="conf/keystore"
>>> keystorePass="_password_" <-------------
>>> clientAuth="false" sslProtocol="TLS"/>
>>>
>>> There are other ways to accomplish the goal but I
>>> found this to be the easiest when trying to explain
>>> it via typing.
>>>
>>> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>>>
>>> Morning,
>>>
>>> try to update my 4.0.4 running on apache2 to
>>> version 5.0
>>>
>>> but I cannot connect to web-installer, because
>>> of insecure connection (using HSTS). I copied
>>> all the neccessary certifiacte files into the
>>> new OM folder. Is there any other differenz I
>>> need to take care of in using Apache2 instead of
>>> tomcat?
>>>
>>> Greetz
>>>
>>> Stefan
>>>
>>>
>>> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>>>
>>> Morning@ everybody,
>>>
>>> tested it three times. Installation of kms
>>> directly on a 18.04. LTS Ubuntu works very well.
>>>
>>> Maybe for Alvaro and his great Tutorials (!)
>>> it would be worth to add a paragraph for
>>> native installation with the commands:
>>>
>>> sudo apt update
>>> sudo apt install --no-install-recommends
>>> --yes gnupg #to be sure that gnupg is installed#
>>> DISTRO="bionic" #verify the name of the
>>> distribution#
>>> sudo apt-key adv --keyserver
>>> keyserver.ubuntu.com --recv-keys 5AFA7A83
>>> #in the following we are building the kms
>>> sources.list#
>>> sudo tee
>>> "/etc/apt/sources.list.d/kurento.list"
>>> >/dev/null <<EOF
>>> # server answers with > #
>>> deb [arch=amd64]
>>> http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
>>> EOF
>>> # server returns to normal prompt #
>>> sudo apt update && sudo apt install --yes
>>> kurento-media-server
>>>
>>> ## thats all ##
>>>
>>> Greetz
>>>
>>> Stefan
>>>
>>>
>>> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
>>>
>>> Hello All,
>>>
>>> recently new Kurento server with native
>>> 18.04 support is out [1
>>> <https://www.kurento.org/blog/kurento-610-bionic-support>]
>>> So overall installation should be more
>>> stable :)
>>>
>>> [1]
>>> https://www.kurento.org/blog/kurento-610-bionic-support
>>>
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
I use the newer one, but checked both of them.
I have no idea, it seems like a connection problem concerning rights or
something like that.
Greetz
Stefan
Am 14.04.2019 16:43, schrieb Aaron Hepp:
> Last thing I can think of...which mysql connector are you using? My Ubuntu 16.04 OM5 install is still using the old 5.1.45. I never replaced it with the 5.1.47. If you followed the instructions for the 18.04 OM5 install it is using the 8.0.15. That is if you are using Ubuntu.
>
> The version we have used:
> 4.x
> mysql-connector-java-
> 5.1.47.jar 5.1.45.jar (what I am currently running)
> mysql-connector-java-
> 5.1.47.jar 5.1.47.jar
> 5.x
> mysql-connector-java-
> 5.1.47.jar 8.0.15.jar
>
> On 4/14/19 10:29 AM, Stefan Kühl wrote:
>
> Hello Aaron,
>
> checked the mysql_persistence.xml twice and added the name of the database. Still same problem. mysql is up and running, connection via cli works with given credentials.
> Rebooted, still same error message.
>
> Purged mariadb-server, reinstall it, new database created, nothing.....same error message.
>
> Checked mysql port 3306 -> listening for 127.0.0.1
>
> I'am through.....
>
> Greetz Stefan
>
> Am 14.04.2019 15:16, schrieb Aaron Hepp: I had the same problem but mine was a database that filed to build correctly. So I dropped the database and recreated it.
>
> But 1st I would check your mysql_persistence.xml file (/opt/your_om_install_location/webapps/openmeetings/WEB-INF/classes/META-INF/)
>
> Make sure your database name is defined in the file.
>
> <property name="openjpa.ConnectionProperties" value="DriverClassName=com.mysql.jdbc.Driver , Url=jdbc:mysql://localhost:3306/<DATABASE_NAME>?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true , MaxActive=100 , MaxWait=10000 , TestOnBorrow=true , poolPreparedStatements=true , Username= , Password="/>
>
> On 4/14/19 7:58 AM, Stefan Kühl wrote:
>
> Strange!!
>
> Running the web installer, in the part mysql it says:
>
> Could not create connection to database server. Attempted reconnect 3 times. Giving up.
>
> mariadb-server works fine, all privileges are set. Try different tables. Don't work.
>
> With the old installation it works without problems.
>
> Any ideas?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 13:04, schrieb Stefan Kühl:
>
> yes, got it.
> I use a script to renew my letsencrypt certificates which use also .jks. copy the keystore.jks to keystore and it works. ;-)
>
> Thanks
>
> Am 14.04.2019 12:38, schrieb Aaron Hepp: also note that in OM4 it used keystore.jks where in OM5 it is just keystore. It may not be necessary but I create a new keystore file each time I renew my cert via letsencrypt.
>
> Below is the commands I use to generate the cert and keystore
>
> letsencrypt certonly
> ****with OM not running select 1
> ****enter your domain name example: testom5.net
>
> ****I store my cert and files in a folder called ssl to make it simpler when typing the commands to generate the keystore
> cd /opt/files/ssl
> ****copy the generated cert, key, and root to the ssl folder and rename
> cp /etc/letsencrypt/live/testom5.net/cert.pem /opt/files/ssl/red5.crt
> cp /etc/letsencrypt/live/testom5.net/privkey.pem /opt/files/ssl/red5.key
> cp /etc/letsencrypt/live/testom5.net/fullchain.pem /opt/files/ssl/root.crt
>
> **** delete the existing keystore file (in my example my OM install is in a folder called om5)
> **** also deletes the generated files when creating the keystore (.p12)
> rm /opt/files/ssl/red5.p12
> rm /opt/om5/conf/keystore
>
> ****create new keystore source file (will ask you to create a password which will be used in the creation)
> openssl pkcs12 -export -in red5.crt -inkey red5.key -out red5.p12 -name red5 -certfile root.crt
>
> **** create new keystore (password is the password you used in the above step example: password. This is all one line)
> keytool -importkeystore -srcstorepass password -srckeystore red5.p12 -srcstoretype PKCS12 -deststorepass password -destkeystore /opt/om5/conf/keystore -alias red5
>
> **** add the root certificate (will ask for the password you used in the 1st step)
> keytool -import -alias root -keystore /opt/om5/conf/keystore -trustcacerts -file root.crt
>
> ****your new keystore has now been created. Now the password you used in step one, make sure you change the password in the /opt/om5/conf/server.xml file to match what you used
>
> ****section where password goes
> <Connector port="5443" protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="150" SSLEnabled="true"
> keystoreFile="conf/keystore" keystorePass="password" <-------------
> clientAuth="false" sslProtocol="TLS"/>
>
> There are other ways to accomplish the goal but I found this to be the easiest when trying to explain it via typing.
>
> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>
> Morning,
>
> try to update my 4.0.4 running on apache2 to version 5.0
>
> but I cannot connect to web-installer, because of insecure connection (using HSTS). I copied all the neccessary certifiacte files into the new OM folder. Is there any other differenz I need to take care of in using Apache2 instead of tomcat?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>
> Morning@ everybody,
>
> tested it three times. Installation of kms directly on a 18.04. LTS Ubuntu works very well.
>
> Maybe for Alvaro and his great Tutorials (!) it would be worth to add a paragraph for native installation with the commands:
>
> sudo apt update
> sudo apt install --no-install-recommends --yes gnupg #to be sure that gnupg is installed#
> DISTRO="bionic" #verify the name of the distribution#
> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
> #in the following we are building the kms sources.list#
> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
> # server answers with > #
> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
> EOF
> # server returns to normal prompt #
> sudo apt update && sudo apt install --yes kurento-media-server
>
> ## thats all ##
>
> Greetz
>
> Stefan
>
> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
> Hello All,
>
> recently new Kurento server with native 18.04 support is out [1 [1]]
> So overall installation should be more stable :)
>
> [1] https://www.kurento.org/blog/kurento-610-bionic-support
Links:
------
[1] https://www.kurento.org/blog/kurento-610-bionic-support
Re: Update 404 Apache to 5.0
Posted by Aaron Hepp <aa...@gmail.com>.
Last thing I can think of...which mysql connector are you using? My
Ubuntu 16.04 OM5 install is still using the old 5.1.45. I never
replaced it with the 5.1.47. If you followed the instructions for the
18.04 OM5 install it is using the 8.0.15. That is if you are using Ubuntu.
The version we have used:
4.x
mysql-connector-java-
5.1.47.jar
5.1.45.jar (what I am currently running)
mysql-connector-java-
5.1.47.jar
5.1.47.jar
5.x
mysql-connector-java-
5.1.47.jar
8.0.15.jar
On 4/14/19 10:29 AM, Stefan Kühl wrote:
>
> Hello Aaron,
>
> checked the mysql_persistence.xml twice and added the name of the
> database. Still same problem. mysql is up and running, connection via
> cli works with given credentials.
> Rebooted, still same error message.
>
> Purged mariadb-server, reinstall it, new database created,
> nothing.....same error message.
>
> Checked mysql port 3306 -> listening for 127.0.0.1
>
> I'am through.....
>
> Greetz Stefan
>
>
> Am 14.04.2019 15:16, schrieb Aaron Hepp:
>
>> I had the same problem but mine was a database that filed to build
>> correctly. So I dropped the database and recreated it.
>>
>> But 1st I would check your mysql_persistence.xml file
>> (/opt/your_om_install_location/webapps/openmeetings/WEB-INF/classes/META-INF/)
>>
>> Make sure your database name is defined in the file.
>>
>> <property name="openjpa.ConnectionProperties"
>> value="DriverClassName=com.mysql.jdbc.Driver ,
>> Url=jdbc:mysql://localhost:3306/*<database_name>*?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true
>> , MaxActive=100 , MaxWait=10000 , TestOnBorrow=true ,
>> poolPreparedStatements=true , Username= , Password="/>
>>
>>
>> On 4/14/19 7:58 AM, Stefan Kühl wrote:
>>>
>>> Strange!!
>>>
>>> Running the web installer, in the part mysql it says:
>>>
>>> Could not create connection to database server. Attempted reconnect
>>> 3 times. Giving up.
>>>
>>> mariadb-server works fine, all privileges are set. Try different
>>> tables. Don't work.
>>>
>>> With the old installation it works without problems.
>>>
>>> Any ideas?
>>>
>>> Greetz
>>>
>>> Stefan
>>>
>>>
>>> Am 14.04.2019 13:04, schrieb Stefan Kühl:
>>>
>>> yes, got it.
>>> I use a script to renew my letsencrypt certificates which use
>>> also .jks. copy the keystore.jks to keystore and it works. ;-)
>>>
>>> Thanks
>>>
>>>
>>>
>>> Am 14.04.2019 12:38, schrieb Aaron Hepp:
>>>
>>> also note that in OM4 it used keystore.jks where in OM5 it
>>> is just keystore. It may not be necessary but I create a
>>> new keystore file each time I renew my cert via letsencrypt.
>>>
>>> Below is the commands I use to generate the cert and keystore
>>>
>>> letsencrypt certonly
>>> ****with OM not running select 1
>>> ****enter your domain name example: testom5.net
>>>
>>> ****I store my cert and files in a folder called ssl to make
>>> it simpler when typing the commands to generate the keystore
>>> cd /opt/files/ssl
>>> ****copy the generated cert, key, and root to the ssl folder
>>> and rename
>>> cp /etc/letsencrypt/live/testom5.net/cert.pem
>>> /opt/files/ssl/red5.crt
>>> cp /etc/letsencrypt/live/testom5.net/privkey.pem
>>> /opt/files/ssl/red5.key
>>> cp /etc/letsencrypt/live/testom5.net/fullchain.pem
>>> /opt/files/ssl/root.crt
>>>
>>> **** delete the existing keystore file (in my example my OM
>>> install is in a folder called om5)
>>> **** also deletes the generated files when creating the
>>> keystore (.p12)
>>> rm /opt/files/ssl/red5.p12
>>> rm /opt/om5/conf/keystore
>>>
>>> ****create new keystore source file (will ask you to create
>>> a password which will be used in the creation)
>>> openssl pkcs12 -export -in red5.crt -inkey red5.key -out
>>> red5.p12 -name red5 -certfile root.crt
>>>
>>> **** create new keystore (password is the password you used
>>> in the above step example: password. This is all one line)
>>> keytool -importkeystore -srcstorepass _password
>>> _-srckeystore red5.p12 -srcstoretype PKCS12
>>> -deststorepass_password_ -destkeystore
>>> /opt/om5/conf/keystore -alias red5
>>>
>>> **** add the root certificate (will ask for the password you
>>> used in the 1st step)
>>> keytool -import -alias root -keystore /opt/om5/conf/keystore
>>> -trustcacerts -file root.crt
>>>
>>> ****your new keystore has now been created. Now the
>>> password you used in step one, make sure you change the
>>> password in the /opt/om5/conf/server.xml file to match what
>>> you used
>>>
>>> ****section where password goes
>>> <Connector port="5443"
>>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>>> maxThreads="150" SSLEnabled="true"
>>> keystoreFile="conf/keystore"
>>> keystorePass="_password_" <-------------
>>> clientAuth="false" sslProtocol="TLS"/>
>>>
>>> There are other ways to accomplish the goal but I found this
>>> to be the easiest when trying to explain it via typing.
>>>
>>> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>>>
>>> Morning,
>>>
>>> try to update my 4.0.4 running on apache2 to version 5.0
>>>
>>> but I cannot connect to web-installer, because of
>>> insecure connection (using HSTS). I copied all the
>>> neccessary certifiacte files into the new OM folder. Is
>>> there any other differenz I need to take care of in
>>> using Apache2 instead of tomcat?
>>>
>>> Greetz
>>>
>>> Stefan
>>>
>>>
>>> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>>>
>>> Morning@ everybody,
>>>
>>> tested it three times. Installation of kms directly
>>> on a 18.04. LTS Ubuntu works very well.
>>>
>>> Maybe for Alvaro and his great Tutorials (!) it
>>> would be worth to add a paragraph for native
>>> installation with the commands:
>>>
>>> sudo apt update
>>> sudo apt install --no-install-recommends --yes gnupg
>>> #to be sure that gnupg is installed#
>>> DISTRO="bionic" #verify the name of the distribution#
>>> sudo apt-key adv --keyserver keyserver.ubuntu.com
>>> --recv-keys 5AFA7A83
>>> #in the following we are building the kms sources.list#
>>> sudo tee "/etc/apt/sources.list.d/kurento.list"
>>> >/dev/null <<EOF
>>> # server answers with > #
>>> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0
>>> $DISTRO kms6
>>> EOF
>>> # server returns to normal prompt #
>>> sudo apt update && sudo apt install --yes
>>> kurento-media-server
>>>
>>> ## thats all ##
>>>
>>> Greetz
>>>
>>> Stefan
>>>
>>>
>>> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
>>>
>>> Hello All,
>>>
>>> recently new Kurento server with native 18.04
>>> support is out [1
>>> <https://www.kurento.org/blog/kurento-610-bionic-support>]
>>> So overall installation should be more stable :)
>>>
>>> [1]
>>> https://www.kurento.org/blog/kurento-610-bionic-support
>>>
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Hello Aaron,
checked the mysql_persistence.xml twice and added the name of the
database. Still same problem. mysql is up and running, connection via
cli works with given credentials.
Rebooted, still same error message.
Purged mariadb-server, reinstall it, new database created,
nothing.....same error message.
Checked mysql port 3306 -> listening for 127.0.0.1
I'am through.....
Greetz Stefan
Am 14.04.2019 15:16, schrieb Aaron Hepp:
> I had the same problem but mine was a database that filed to build correctly. So I dropped the database and recreated it.
>
> But 1st I would check your mysql_persistence.xml file (/opt/your_om_install_location/webapps/openmeetings/WEB-INF/classes/META-INF/)
>
> Make sure your database name is defined in the file.
>
> <property name="openjpa.ConnectionProperties" value="DriverClassName=com.mysql.jdbc.Driver , Url=jdbc:mysql://localhost:3306/<DATABASE_NAME>?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true , MaxActive=100 , MaxWait=10000 , TestOnBorrow=true , poolPreparedStatements=true , Username= , Password="/>
>
> On 4/14/19 7:58 AM, Stefan Kühl wrote:
>
> Strange!!
>
> Running the web installer, in the part mysql it says:
>
> Could not create connection to database server. Attempted reconnect 3 times. Giving up.
>
> mariadb-server works fine, all privileges are set. Try different tables. Don't work.
>
> With the old installation it works without problems.
>
> Any ideas?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 13:04, schrieb Stefan Kühl:
>
> yes, got it.
> I use a script to renew my letsencrypt certificates which use also .jks. copy the keystore.jks to keystore and it works. ;-)
>
> Thanks
>
> Am 14.04.2019 12:38, schrieb Aaron Hepp: also note that in OM4 it used keystore.jks where in OM5 it is just keystore. It may not be necessary but I create a new keystore file each time I renew my cert via letsencrypt.
>
> Below is the commands I use to generate the cert and keystore
>
> letsencrypt certonly
> ****with OM not running select 1
> ****enter your domain name example: testom5.net
>
> ****I store my cert and files in a folder called ssl to make it simpler when typing the commands to generate the keystore
> cd /opt/files/ssl
> ****copy the generated cert, key, and root to the ssl folder and rename
> cp /etc/letsencrypt/live/testom5.net/cert.pem /opt/files/ssl/red5.crt
> cp /etc/letsencrypt/live/testom5.net/privkey.pem /opt/files/ssl/red5.key
> cp /etc/letsencrypt/live/testom5.net/fullchain.pem /opt/files/ssl/root.crt
>
> **** delete the existing keystore file (in my example my OM install is in a folder called om5)
> **** also deletes the generated files when creating the keystore (.p12)
> rm /opt/files/ssl/red5.p12
> rm /opt/om5/conf/keystore
>
> ****create new keystore source file (will ask you to create a password which will be used in the creation)
> openssl pkcs12 -export -in red5.crt -inkey red5.key -out red5.p12 -name red5 -certfile root.crt
>
> **** create new keystore (password is the password you used in the above step example: password. This is all one line)
> keytool -importkeystore -srcstorepass password -srckeystore red5.p12 -srcstoretype PKCS12 -deststorepass password -destkeystore /opt/om5/conf/keystore -alias red5
>
> **** add the root certificate (will ask for the password you used in the 1st step)
> keytool -import -alias root -keystore /opt/om5/conf/keystore -trustcacerts -file root.crt
>
> ****your new keystore has now been created. Now the password you used in step one, make sure you change the password in the /opt/om5/conf/server.xml file to match what you used
>
> ****section where password goes
> <Connector port="5443" protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="150" SSLEnabled="true"
> keystoreFile="conf/keystore" keystorePass="password" <-------------
> clientAuth="false" sslProtocol="TLS"/>
>
> There are other ways to accomplish the goal but I found this to be the easiest when trying to explain it via typing.
>
> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>
> Morning,
>
> try to update my 4.0.4 running on apache2 to version 5.0
>
> but I cannot connect to web-installer, because of insecure connection (using HSTS). I copied all the neccessary certifiacte files into the new OM folder. Is there any other differenz I need to take care of in using Apache2 instead of tomcat?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>
> Morning@ everybody,
>
> tested it three times. Installation of kms directly on a 18.04. LTS Ubuntu works very well.
>
> Maybe for Alvaro and his great Tutorials (!) it would be worth to add a paragraph for native installation with the commands:
>
> sudo apt update
> sudo apt install --no-install-recommends --yes gnupg #to be sure that gnupg is installed#
> DISTRO="bionic" #verify the name of the distribution#
> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
> #in the following we are building the kms sources.list#
> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
> # server answers with > #
> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
> EOF
> # server returns to normal prompt #
> sudo apt update && sudo apt install --yes kurento-media-server
>
> ## thats all ##
>
> Greetz
>
> Stefan
>
> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
> Hello All,
>
> recently new Kurento server with native 18.04 support is out [1 [1]]
> So overall installation should be more stable :)
>
> [1] https://www.kurento.org/blog/kurento-610-bionic-support
Links:
------
[1] https://www.kurento.org/blog/kurento-610-bionic-support
Re: Update 404 Apache to 5.0
Posted by Aaron Hepp <aa...@gmail.com>.
I had the same problem but mine was a database that filed to build
correctly. So I dropped the database and recreated it.
But 1st I would check your mysql_persistence.xml file
(/opt/your_om_install_location/webapps/openmeetings/WEB-INF/classes/META-INF/)
Make sure your database name is defined in the file.
<property name="openjpa.ConnectionProperties"
value="DriverClassName=com.mysql.jdbc.Driver ,
Url=jdbc:mysql://localhost:3306/*<database_name>*?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true
, MaxActive=100 , MaxWait=10000 , TestOnBorrow=true ,
poolPreparedStatements=true , Username= , Password="/>
On 4/14/19 7:58 AM, Stefan Kühl wrote:
>
> Strange!!
>
> Running the web installer, in the part mysql it says:
>
> Could not create connection to database server. Attempted reconnect 3
> times. Giving up.
>
> mariadb-server works fine, all privileges are set. Try different
> tables. Don't work.
>
> With the old installation it works without problems.
>
> Any ideas?
>
> Greetz
>
> Stefan
>
>
> Am 14.04.2019 13:04, schrieb Stefan Kühl:
>
>> yes, got it.
>> I use a script to renew my letsencrypt certificates which use also
>> .jks. copy the keystore.jks to keystore and it works. ;-)
>>
>> Thanks
>>
>>
>>
>> Am 14.04.2019 12:38, schrieb Aaron Hepp:
>>
>> also note that in OM4 it used keystore.jks where in OM5 it is
>> just keystore. It may not be necessary but I create a new
>> keystore file each time I renew my cert via letsencrypt.
>>
>> Below is the commands I use to generate the cert and keystore
>>
>> letsencrypt certonly
>> ****with OM not running select 1
>> ****enter your domain name example: testom5.net
>>
>> ****I store my cert and files in a folder called ssl to make it
>> simpler when typing the commands to generate the keystore
>> cd /opt/files/ssl
>> ****copy the generated cert, key, and root to the ssl folder and
>> rename
>> cp /etc/letsencrypt/live/testom5.net/cert.pem /opt/files/ssl/red5.crt
>> cp /etc/letsencrypt/live/testom5.net/privkey.pem
>> /opt/files/ssl/red5.key
>> cp /etc/letsencrypt/live/testom5.net/fullchain.pem
>> /opt/files/ssl/root.crt
>>
>> **** delete the existing keystore file (in my example my OM
>> install is in a folder called om5)
>> **** also deletes the generated files when creating the keystore
>> (.p12)
>> rm /opt/files/ssl/red5.p12
>> rm /opt/om5/conf/keystore
>>
>> ****create new keystore source file (will ask you to create a
>> password which will be used in the creation)
>> openssl pkcs12 -export -in red5.crt -inkey red5.key -out red5.p12
>> -name red5 -certfile root.crt
>>
>> **** create new keystore (password is the password you used in
>> the above step example: password. This is all one line)
>> keytool -importkeystore -srcstorepass _password _-srckeystore
>> red5.p12 -srcstoretype PKCS12 -deststorepass_password_
>> -destkeystore /opt/om5/conf/keystore -alias red5
>>
>> **** add the root certificate (will ask for the password you used
>> in the 1st step)
>> keytool -import -alias root -keystore /opt/om5/conf/keystore
>> -trustcacerts -file root.crt
>>
>> ****your new keystore has now been created. Now the password you
>> used in step one, make sure you change the password in the
>> /opt/om5/conf/server.xml file to match what you used
>>
>> ****section where password goes
>> <Connector port="5443"
>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>> maxThreads="150" SSLEnabled="true"
>> keystoreFile="conf/keystore"
>> keystorePass="_password_" <-------------
>> clientAuth="false" sslProtocol="TLS"/>
>>
>> There are other ways to accomplish the goal but I found this to
>> be the easiest when trying to explain it via typing.
>>
>> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>>
>> Morning,
>>
>> try to update my 4.0.4 running on apache2 to version 5.0
>>
>> but I cannot connect to web-installer, because of insecure
>> connection (using HSTS). I copied all the neccessary
>> certifiacte files into the new OM folder. Is there any other
>> differenz I need to take care of in using Apache2 instead of
>> tomcat?
>>
>> Greetz
>>
>> Stefan
>>
>>
>> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>>
>> Morning@ everybody,
>>
>> tested it three times. Installation of kms directly on a
>> 18.04. LTS Ubuntu works very well.
>>
>> Maybe for Alvaro and his great Tutorials (!) it would be
>> worth to add a paragraph for native installation with the
>> commands:
>>
>> sudo apt update
>> sudo apt install --no-install-recommends --yes gnupg #to
>> be sure that gnupg is installed#
>> DISTRO="bionic" #verify the name of the distribution#
>> sudo apt-key adv --keyserver keyserver.ubuntu.com
>> --recv-keys 5AFA7A83
>> #in the following we are building the kms sources.list#
>> sudo tee "/etc/apt/sources.list.d/kurento.list"
>> >/dev/null <<EOF
>> # server answers with > #
>> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO
>> kms6
>> EOF
>> # server returns to normal prompt #
>> sudo apt update && sudo apt install --yes
>> kurento-media-server
>>
>> ## thats all ##
>>
>> Greetz
>>
>> Stefan
>>
>>
>> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
>>
>> Hello All,
>>
>> recently new Kurento server with native 18.04 support
>> is out [1
>> <https://www.kurento.org/blog/kurento-610-bionic-support>]
>> So overall installation should be more stable :)
>>
>> [1]
>> https://www.kurento.org/blog/kurento-610-bionic-support
>>
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
Strange!!
Running the web installer, in the part mysql it says:
Could not create connection to database server. Attempted reconnect 3
times. Giving up.
mariadb-server works fine, all privileges are set. Try different tables.
Don't work.
With the old installation it works without problems.
Any ideas?
Greetz
Stefan
Am 14.04.2019 13:04, schrieb Stefan Kühl:
> yes, got it.
> I use a script to renew my letsencrypt certificates which use also .jks. copy the keystore.jks to keystore and it works. ;-)
>
> Thanks
>
> Am 14.04.2019 12:38, schrieb Aaron Hepp: also note that in OM4 it used keystore.jks where in OM5 it is just keystore. It may not be necessary but I create a new keystore file each time I renew my cert via letsencrypt.
>
> Below is the commands I use to generate the cert and keystore
>
> letsencrypt certonly
> ****with OM not running select 1
> ****enter your domain name example: testom5.net
>
> ****I store my cert and files in a folder called ssl to make it simpler when typing the commands to generate the keystore
> cd /opt/files/ssl
> ****copy the generated cert, key, and root to the ssl folder and rename
> cp /etc/letsencrypt/live/testom5.net/cert.pem /opt/files/ssl/red5.crt
> cp /etc/letsencrypt/live/testom5.net/privkey.pem /opt/files/ssl/red5.key
> cp /etc/letsencrypt/live/testom5.net/fullchain.pem /opt/files/ssl/root.crt
>
> **** delete the existing keystore file (in my example my OM install is in a folder called om5)
> **** also deletes the generated files when creating the keystore (.p12)
> rm /opt/files/ssl/red5.p12
> rm /opt/om5/conf/keystore
>
> ****create new keystore source file (will ask you to create a password which will be used in the creation)
> openssl pkcs12 -export -in red5.crt -inkey red5.key -out red5.p12 -name red5 -certfile root.crt
>
> **** create new keystore (password is the password you used in the above step example: password. This is all one line)
> keytool -importkeystore -srcstorepass password -srckeystore red5.p12 -srcstoretype PKCS12 -deststorepass password -destkeystore /opt/om5/conf/keystore -alias red5
>
> **** add the root certificate (will ask for the password you used in the 1st step)
> keytool -import -alias root -keystore /opt/om5/conf/keystore -trustcacerts -file root.crt
>
> ****your new keystore has now been created. Now the password you used in step one, make sure you change the password in the /opt/om5/conf/server.xml file to match what you used
>
> ****section where password goes
> <Connector port="5443" protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="150" SSLEnabled="true"
> keystoreFile="conf/keystore" keystorePass="password" <-------------
> clientAuth="false" sslProtocol="TLS"/>
>
> There are other ways to accomplish the goal but I found this to be the easiest when trying to explain it via typing.
>
> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>
> Morning,
>
> try to update my 4.0.4 running on apache2 to version 5.0
>
> but I cannot connect to web-installer, because of insecure connection (using HSTS). I copied all the neccessary certifiacte files into the new OM folder. Is there any other differenz I need to take care of in using Apache2 instead of tomcat?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>
> Morning@ everybody,
>
> tested it three times. Installation of kms directly on a 18.04. LTS Ubuntu works very well.
>
> Maybe for Alvaro and his great Tutorials (!) it would be worth to add a paragraph for native installation with the commands:
>
> sudo apt update
> sudo apt install --no-install-recommends --yes gnupg #to be sure that gnupg is installed#
> DISTRO="bionic" #verify the name of the distribution#
> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
> #in the following we are building the kms sources.list#
> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
> # server answers with > #
> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
> EOF
> # server returns to normal prompt #
> sudo apt update && sudo apt install --yes kurento-media-server
>
> ## thats all ##
>
> Greetz
>
> Stefan
>
> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
> Hello All,
>
> recently new Kurento server with native 18.04 support is out [1 [1]]
> So overall installation should be more stable :)
>
> [1] https://www.kurento.org/blog/kurento-610-bionic-support
Links:
------
[1] https://www.kurento.org/blog/kurento-610-bionic-support
Re: Update 404 Apache to 5.0
Posted by Stefan Kühl <st...@quatrekuehl.eu>.
yes, got it.
I use a script to renew my letsencrypt certificates which use also .jks.
copy the keystore.jks to keystore and it works. ;-)
Thanks
Am 14.04.2019 12:38, schrieb Aaron Hepp:
> also note that in OM4 it used keystore.jks where in OM5 it is just keystore. It may not be necessary but I create a new keystore file each time I renew my cert via letsencrypt.
>
> Below is the commands I use to generate the cert and keystore
>
> letsencrypt certonly
> ****with OM not running select 1
> ****enter your domain name example: testom5.net
>
> ****I store my cert and files in a folder called ssl to make it simpler when typing the commands to generate the keystore
> cd /opt/files/ssl
> ****copy the generated cert, key, and root to the ssl folder and rename
> cp /etc/letsencrypt/live/testom5.net/cert.pem /opt/files/ssl/red5.crt
> cp /etc/letsencrypt/live/testom5.net/privkey.pem /opt/files/ssl/red5.key
> cp /etc/letsencrypt/live/testom5.net/fullchain.pem /opt/files/ssl/root.crt
>
> **** delete the existing keystore file (in my example my OM install is in a folder called om5)
> **** also deletes the generated files when creating the keystore (.p12)
> rm /opt/files/ssl/red5.p12
> rm /opt/om5/conf/keystore
>
> ****create new keystore source file (will ask you to create a password which will be used in the creation)
> openssl pkcs12 -export -in red5.crt -inkey red5.key -out red5.p12 -name red5 -certfile root.crt
>
> **** create new keystore (password is the password you used in the above step example: password. This is all one line)
> keytool -importkeystore -srcstorepass password -srckeystore red5.p12 -srcstoretype PKCS12 -deststorepass password -destkeystore /opt/om5/conf/keystore -alias red5
>
> **** add the root certificate (will ask for the password you used in the 1st step)
> keytool -import -alias root -keystore /opt/om5/conf/keystore -trustcacerts -file root.crt
>
> ****your new keystore has now been created. Now the password you used in step one, make sure you change the password in the /opt/om5/conf/server.xml file to match what you used
>
> ****section where password goes
> <Connector port="5443" protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="150" SSLEnabled="true"
> keystoreFile="conf/keystore" keystorePass="password" <-------------
> clientAuth="false" sslProtocol="TLS"/>
>
> There are other ways to accomplish the goal but I found this to be the easiest when trying to explain it via typing.
>
> On 4/14/19 5:36 AM, Stefan Kühl wrote:
>
> Morning,
>
> try to update my 4.0.4 running on apache2 to version 5.0
>
> but I cannot connect to web-installer, because of insecure connection (using HSTS). I copied all the neccessary certifiacte files into the new OM folder. Is there any other differenz I need to take care of in using Apache2 instead of tomcat?
>
> Greetz
>
> Stefan
>
> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>
> Morning@ everybody,
>
> tested it three times. Installation of kms directly on a 18.04. LTS Ubuntu works very well.
>
> Maybe for Alvaro and his great Tutorials (!) it would be worth to add a paragraph for native installation with the commands:
>
> sudo apt update
> sudo apt install --no-install-recommends --yes gnupg #to be sure that gnupg is installed#
> DISTRO="bionic" #verify the name of the distribution#
> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
> #in the following we are building the kms sources.list#
> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
> # server answers with > #
> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
> EOF
> # server returns to normal prompt #
> sudo apt update && sudo apt install --yes kurento-media-server
>
> ## thats all ##
>
> Greetz
>
> Stefan
>
> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
> Hello All,
>
> recently new Kurento server with native 18.04 support is out [1 [1]]
> So overall installation should be more stable :)
>
> [1] https://www.kurento.org/blog/kurento-610-bionic-support
Links:
------
[1] https://www.kurento.org/blog/kurento-610-bionic-support
Re: Update 404 Apache to 5.0
Posted by Aaron Hepp <aa...@gmail.com>.
also note that in OM4 it used keystore.jks where in OM5 it is just
keystore. It may not be necessary but I create a new keystore file each
time I renew my cert via letsencrypt.
Below is the commands I use to generate the cert and keystore
letsencrypt certonly
****with OM not running select 1
****enter your domain name example: testom5.net
****I store my cert and files in a folder called ssl to make it simpler
when typing the commands to generate the keystore
cd /opt/files/ssl
****copy the generated cert, key, and root to the ssl folder and rename
cp /etc/letsencrypt/live/testom5.net/cert.pem /opt/files/ssl/red5.crt
cp /etc/letsencrypt/live/testom5.net/privkey.pem /opt/files/ssl/red5.key
cp /etc/letsencrypt/live/testom5.net/fullchain.pem /opt/files/ssl/root.crt
**** delete the existing keystore file (in my example my OM install is
in a folder called om5)
**** also deletes the generated files when creating the keystore (.p12)
rm /opt/files/ssl/red5.p12
rm /opt/om5/conf/keystore
****create new keystore source file (will ask you to create a password
which will be used in the creation)
openssl pkcs12 -export -in red5.crt -inkey red5.key -out red5.p12 -name
red5 -certfile root.crt
**** create new keystore (password is the password you used in the above
step example: password. This is all one line)
keytool -importkeystore -srcstorepass _password _-srckeystore red5.p12
-srcstoretype PKCS12 -deststorepass_password_ -destkeystore
/opt/om5/conf/keystore -alias red5
**** add the root certificate (will ask for the password you used in the
1st step)
keytool -import -alias root -keystore /opt/om5/conf/keystore
-trustcacerts -file root.crt
****your new keystore has now been created. Now the password you used
in step one, make sure you change the password in the
/opt/om5/conf/server.xml file to match what you used
****section where password goes
<Connector port="5443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" SSLEnabled="true"
keystoreFile="conf/keystore" keystorePass="_password_"
<-------------
clientAuth="false" sslProtocol="TLS"/>
There are other ways to accomplish the goal but I found this to be the
easiest when trying to explain it via typing.
On 4/14/19 5:36 AM, Stefan Kühl wrote:
>
> Morning,
>
> try to update my 4.0.4 running on apache2 to version 5.0
>
> but I cannot connect to web-installer, because of insecure connection
> (using HSTS). I copied all the neccessary certifiacte files into the
> new OM folder. Is there any other differenz I need to take care of in
> using Apache2 instead of tomcat?
>
> Greetz
>
> Stefan
>
>
> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>
>> Morning@ everybody,
>>
>> tested it three times. Installation of kms directly on a 18.04. LTS
>> Ubuntu works very well.
>>
>> Maybe for Alvaro and his great Tutorials (!) it would be worth to add
>> a paragraph for native installation with the commands:
>>
>> sudo apt update
>> sudo apt install --no-install-recommends --yes gnupg #to be sure that
>> gnupg is installed#
>> DISTRO="bionic" #verify the name of the distribution#
>> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
>> #in the following we are building the kms sources.list#
>> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
>> # server answers with > #
>> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
>> EOF
>> # server returns to normal prompt #
>> sudo apt update && sudo apt install --yes kurento-media-server
>>
>> ## thats all ##
>>
>> Greetz
>>
>> Stefan
>>
>>
>> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
>>
>> Hello All,
>>
>> recently new Kurento server with native 18.04 support is out [1
>> <https://www.kurento.org/blog/kurento-610-bionic-support>]
>> So overall installation should be more stable :)
>>
>> [1] https://www.kurento.org/blog/kurento-610-bionic-support
>>
Re: Update 404 Apache to 5.0
Posted by Aaron Hepp <aa...@gmail.com>.
look at your sever.xml file to make sure you have the right keystore
password set..
<Connector port="443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" SSLEnabled="true"
keystoreFile="conf/keystore"
keystorePass="#################"
clientAuth="false" sslProtocol="TLS"/>
On 4/14/19 5:36 AM, Stefan Kühl wrote:
>
> Morning,
>
> try to update my 4.0.4 running on apache2 to version 5.0
>
> but I cannot connect to web-installer, because of insecure connection
> (using HSTS). I copied all the neccessary certifiacte files into the
> new OM folder. Is there any other differenz I need to take care of in
> using Apache2 instead of tomcat?
>
> Greetz
>
> Stefan
>
>
> Am 14.04.2019 10:36, schrieb Stefan Kühl:
>
>> Morning@ everybody,
>>
>> tested it three times. Installation of kms directly on a 18.04. LTS
>> Ubuntu works very well.
>>
>> Maybe for Alvaro and his great Tutorials (!) it would be worth to add
>> a paragraph for native installation with the commands:
>>
>> sudo apt update
>> sudo apt install --no-install-recommends --yes gnupg #to be sure that
>> gnupg is installed#
>> DISTRO="bionic" #verify the name of the distribution#
>> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5AFA7A83
>> #in the following we are building the kms sources.list#
>> sudo tee "/etc/apt/sources.list.d/kurento.list" >/dev/null <<EOF
>> # server answers with > #
>> deb [arch=amd64] http://ubuntu.openvidu.io/6.10.0 $DISTRO kms6
>> EOF
>> # server returns to normal prompt #
>> sudo apt update && sudo apt install --yes kurento-media-server
>>
>> ## thats all ##
>>
>> Greetz
>>
>> Stefan
>>
>>
>> Am 09.04.2019 11:36, schrieb Maxim Solodovnik:
>>
>> Hello All,
>>
>> recently new Kurento server with native 18.04 support is out [1
>> <https://www.kurento.org/blog/kurento-610-bionic-support>]
>> So overall installation should be more stable :)
>>
>> [1] https://www.kurento.org/blog/kurento-610-bionic-support
>>