Not sure really what the problem was. the persistence file was correct
with the right db name in it. I just dropped the database and rebuilt
it, and it connected fine. First time I had ever had the issue on a
build. But after recreating the database it connected without a
problem. Just going to chalk that one up the strange events.
On 4/13/19 3:19 AM, R. Scholz wrote:
Hello Aaron,
I think it is the same problem I had a few weeks ago. (And I hope I
solved it.)
To your questions with the log: You find relevant logs at "/opt/logs"
e.g. "/opt/%OMDIR%/logs". The actual log is named "catalina.out".
When it is the error I think you have to edit the "mysql-persistence.xml"
You find it in the openmeeting-Directory ->
webapps/openmeetings/WEB-INF/classes/META-INF.
Here the part of my email.
My Solution:
The Parameter "serverTimezone" must in the first line of the
Driver-command (where is separated by "&").
It doesn't matter where you put it.
When I put it into the comma-separated-part it's not functionally.
Here's my line in the mysql-persistence.xml:
value="DriverClassName=com.mysql.cj.jdbc.Driver
,
Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&*serverTimezone=Europe/Berlin&*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
, maxTotal=100
, maxIdle=100
, minIdle=0
, maxWaitMillis=10000
, TestOnBorrow=true
, poolPreparedStatements=true
, Username=
, Password=" />
I hope it helps.
Best regards,
René
Am 13.04.2019 um 01:58 schrieb Aaron Hepp:
Where are the connection logs to the database located at? Just stood
up a new OM5 instance on a Ubuntu 16.04 install. went through all
the steps, but does not look like it is making a connection to the
MySQL database.
Could not create connection to database server. Attempted reconnect 3
times. Giving up.
Database is up and listening on port 3306, made sure database name,
user and password were correct, but keep getting the errors. Was
going to look at the logs but forgot where they are at to determine
what the issue was.
