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
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 wrote:
> OK, Maxim,
>
> thanks a lot for the hint.
> No i found the error:
>
> Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException:
> The server
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 serverTimezo
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 wrote:
> You MUST have huge stack-trace in the log in this case .
>
> On Mon
You MUST have huge stack-trace in the log in this case .
On Mon, 15 Apr 2019 at 12:47, Stefan Kühl 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 e
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
"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 wrote:
> Hey Maxim,
>
> as I wrote, I've tried the newest java-connector (and to be sure also the
> old one ;-))
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.LocalEnti
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
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 i
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 A
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
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 insta
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
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
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 defin
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.
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
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
look at your sever.xml file to make sure you have the right keystore
password set..
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 run
20 matches
Mail list logo
