You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by jox joe <jo...@gmail.com> on 2021/11/24 19:59:52 UTC

MariaDB not accessable OM 6.0.0

001: MariaDB is up and running.

● mariadb.service - MariaDB 10.6.5 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
preset: enabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: active (running) since Wed 2021-11-24 19:17:02 GMT; 21min ago
     Docs: man:mariadbd(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 6438 ExecStartPost=/etc/mysql/debian-start (code=exited,
status=0/SUCCESS)
  Process: 6436 ExecStartPost=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 6366 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ]
&& VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]
&& systemctl set-environment _WSREP_START_POSITION=$VA
  Process: 6357 ExecStartPre=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 6348 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d
/var/run/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 6422 (mariadbd)
   Status: "Taking your SQL requests now..."
    Tasks: 9 (limit: 4915)
   CGroup: /system.slice/mariadb.service
           └─6422 /usr/sbin/mariadbd

002: Then I receive the following message (if Tomcat is running):

mariadbd[6422]: 2021-11-24 19:38:00 243 [Warning] Access denied for user
'om_db_admin'@'localhost' (using password: YES)

In openmeetings.log error: mariadb/sql is down

003: OM 6.0.0 runs on local server Ununtu 18

004:
I can't access OM, the message:
https://192.168.1.30:5443/openmeetings/notinited

I've never seen 'om_db_admin' before.

Thank you for your help.

Re: MariaDB not accessable OM 6.0.0

Posted by Maxim Solodovnik <so...@gmail.com>.
You must specify valid user/password in your db config (persistense.xml)

And ensure DB is accessible via TCP

from mobile (sorry for typos ;)


On Thu, Nov 25, 2021, 03:00 jox joe <jo...@gmail.com> wrote:

> 001: MariaDB is up and running.
>
> ● mariadb.service - MariaDB 10.6.5 database server
>    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
> preset: enabled)
>   Drop-In: /etc/systemd/system/mariadb.service.d
>            └─migrated-from-my.cnf-settings.conf
>    Active: active (running) since Wed 2021-11-24 19:17:02 GMT; 21min ago
>      Docs: man:mariadbd(8)
>            https://mariadb.com/kb/en/library/systemd/
>   Process: 6438 ExecStartPost=/etc/mysql/debian-start (code=exited,
> status=0/SUCCESS)
>   Process: 6436 ExecStartPost=/bin/sh -c systemctl unset-environment
> _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
>   Process: 6366 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ]
> && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]
> && systemctl set-environment _WSREP_START_POSITION=$VA
>   Process: 6357 ExecStartPre=/bin/sh -c systemctl unset-environment
> _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
>   Process: 6348 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d
> /var/run/mysqld (code=exited, status=0/SUCCESS)
>  Main PID: 6422 (mariadbd)
>    Status: "Taking your SQL requests now..."
>     Tasks: 9 (limit: 4915)
>    CGroup: /system.slice/mariadb.service
>            └─6422 /usr/sbin/mariadbd
>
> 002: Then I receive the following message (if Tomcat is running):
>
> mariadbd[6422]: 2021-11-24 19:38:00 243 [Warning] Access denied for user
> 'om_db_admin'@'localhost' (using password: YES)
>
> In openmeetings.log error: mariadb/sql is down
>
> 003: OM 6.0.0 runs on local server Ununtu 18
>
> 004:
> I can't access OM, the message:
> https://192.168.1.30:5443/openmeetings/notinited
>
> I've never seen 'om_db_admin' before.
>
> Thank you for your help.
>
>
>
>
>
>

Re: MariaDB not accessable OM 6.0.0

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Thanks for sharing

Sebastian Wagner
Director Arrakeen Solutions, OM-Hosting.com
http://arrakeen-solutions.co.nz/
https://om-hosting.com - Cloud & Server Hosting for HTML5
Video-Conferencing OpenMeetings
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url>
<https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>


On Sun, 9 Jan 2022 at 04:04, jox joe <jo...@gmail.com> wrote:

> Thanks for your replies.
> SOLUTION:
> I used the wrong database connector.
> It worked with this one:
> mysql-connector-java-8.0.26.jar
>
> Tom Meierjürgen <to...@web.de> ezt írta (időpont: 2021. nov. 25., Cs,
> 8:43):
>
>> Obviously you´re running a Galera Cluster which did not finish its
>> synchronsation/replication due to a node beeing down / having been down.
>>
>> First fix your db-cluster ,then check if the user you configured in OM
>> exists in the db and has the proper rights.
>>
>> Before fixing the db-cluster, the db would not be accessible for the
>> om-nodes.
>>
>> Mostly happens when the galera cluster was not able to build up a proper
>> qorum (2 nodes only? it needs at least three to build a working quorum,
>> but galera runs even with two nodes,but not as fault-tolerant as with a
>> quorum) as then it stops completely in case of an error due to switching
>> off one galera-node or one node crashing due to powerfailure or
>> something like that.
>>
>>
>> Greetz from Cologne/Germany,
>>
>>   Tom
>>
>> Am 24.11.2021 um 20:59 schrieb jox joe:
>> > 001: MariaDB is up and running.
>> >
>> > ● mariadb.service - MariaDB 10.6.5 database server
>> >    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled;
>> > vendor preset: enabled)
>> >   Drop-In: /etc/systemd/system/mariadb.service.d
>> >            └─migrated-from-my.cnf-settings.conf
>> >    Active: active (running) since Wed 2021-11-24 19:17:02 GMT; 21min ago
>> >      Docs: man:mariadbd(8)
>> > https://mariadb.com/kb/en/library/systemd/
>> >   Process: 6438 ExecStartPost=/etc/mysql/debian-start (code=exited,
>> > status=0/SUCCESS)
>> >   Process: 6436 ExecStartPost=/bin/sh -c systemctl unset-environment
>> > _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
>> >   Process: 6366 ExecStartPre=/bin/sh -c [ ! -e
>> > /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..;
>> > /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment
>> > _WSREP_START_POSITION=$VA
>> >   Process: 6357 ExecStartPre=/bin/sh -c systemctl unset-environment
>> > _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
>> >   Process: 6348 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root
>> > -d /var/run/mysqld (code=exited, status=0/SUCCESS)
>> >  Main PID: 6422 (mariadbd)
>> >    Status: "Taking your SQL requests now..."
>> >     Tasks: 9 (limit: 4915)
>> >    CGroup: /system.slice/mariadb.service
>> >            └─6422 /usr/sbin/mariadbd
>> >
>> > 002: Then I receive the following message (if Tomcat is running):
>> >
>> > mariadbd[6422]: 2021-11-24 19:38:00 243 [Warning] Access denied for
>> > user 'om_db_admin'@'localhost' (using password: YES)
>> >
>> > In openmeetings.log error: mariadb/sql is down
>> >
>> > 003: OM 6.0.0 runs on local server Ununtu 18
>> >
>> > 004:
>> > I can't access OM, the message:
>> > https://192.168.1.30:5443/openmeetings/notinited
>> >
>> > I've never seen 'om_db_admin' before.
>> >
>> > Thank you for your help.
>> >
>> >
>> >
>> >
>> >
>>
>

Re: MariaDB not accessable OM 6.0.0

Posted by jox joe <jo...@gmail.com>.
Thanks for your replies.
SOLUTION:
I used the wrong database connector.
It worked with this one:
mysql-connector-java-8.0.26.jar

Tom Meierjürgen <to...@web.de> ezt írta (időpont: 2021. nov. 25., Cs,
8:43):

> Obviously you´re running a Galera Cluster which did not finish its
> synchronsation/replication due to a node beeing down / having been down.
>
> First fix your db-cluster ,then check if the user you configured in OM
> exists in the db and has the proper rights.
>
> Before fixing the db-cluster, the db would not be accessible for the
> om-nodes.
>
> Mostly happens when the galera cluster was not able to build up a proper
> qorum (2 nodes only? it needs at least three to build a working quorum,
> but galera runs even with two nodes,but not as fault-tolerant as with a
> quorum) as then it stops completely in case of an error due to switching
> off one galera-node or one node crashing due to powerfailure or
> something like that.
>
>
> Greetz from Cologne/Germany,
>
>   Tom
>
> Am 24.11.2021 um 20:59 schrieb jox joe:
> > 001: MariaDB is up and running.
> >
> > ● mariadb.service - MariaDB 10.6.5 database server
> >    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled;
> > vendor preset: enabled)
> >   Drop-In: /etc/systemd/system/mariadb.service.d
> >            └─migrated-from-my.cnf-settings.conf
> >    Active: active (running) since Wed 2021-11-24 19:17:02 GMT; 21min ago
> >      Docs: man:mariadbd(8)
> > https://mariadb.com/kb/en/library/systemd/
> >   Process: 6438 ExecStartPost=/etc/mysql/debian-start (code=exited,
> > status=0/SUCCESS)
> >   Process: 6436 ExecStartPost=/bin/sh -c systemctl unset-environment
> > _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
> >   Process: 6366 ExecStartPre=/bin/sh -c [ ! -e
> > /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..;
> > /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment
> > _WSREP_START_POSITION=$VA
> >   Process: 6357 ExecStartPre=/bin/sh -c systemctl unset-environment
> > _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
> >   Process: 6348 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root
> > -d /var/run/mysqld (code=exited, status=0/SUCCESS)
> >  Main PID: 6422 (mariadbd)
> >    Status: "Taking your SQL requests now..."
> >     Tasks: 9 (limit: 4915)
> >    CGroup: /system.slice/mariadb.service
> >            └─6422 /usr/sbin/mariadbd
> >
> > 002: Then I receive the following message (if Tomcat is running):
> >
> > mariadbd[6422]: 2021-11-24 19:38:00 243 [Warning] Access denied for
> > user 'om_db_admin'@'localhost' (using password: YES)
> >
> > In openmeetings.log error: mariadb/sql is down
> >
> > 003: OM 6.0.0 runs on local server Ununtu 18
> >
> > 004:
> > I can't access OM, the message:
> > https://192.168.1.30:5443/openmeetings/notinited
> >
> > I've never seen 'om_db_admin' before.
> >
> > Thank you for your help.
> >
> >
> >
> >
> >
>

Re: MariaDB not accessable OM 6.0.0

Posted by Tom Meierjürgen <to...@web.de>.
Obviously you´re running a Galera Cluster which did not finish its
synchronsation/replication due to a node beeing down / having been down.

First fix your db-cluster ,then check if the user you configured in OM
exists in the db and has the proper rights.

Before fixing the db-cluster, the db would not be accessible for the
om-nodes.

Mostly happens when the galera cluster was not able to build up a proper
qorum (2 nodes only? it needs at least three to build a working quorum,
but galera runs even with two nodes,but not as fault-tolerant as with a
quorum) as then it stops completely in case of an error due to switching
off one galera-node or one node crashing due to powerfailure or
something like that.


Greetz from Cologne/Germany,

  Tom

Am 24.11.2021 um 20:59 schrieb jox joe:
> 001: MariaDB is up and running.
>
> ● mariadb.service - MariaDB 10.6.5 database server
>    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled;
> vendor preset: enabled)
>   Drop-In: /etc/systemd/system/mariadb.service.d
>            └─migrated-from-my.cnf-settings.conf
>    Active: active (running) since Wed 2021-11-24 19:17:02 GMT; 21min ago
>      Docs: man:mariadbd(8)
> https://mariadb.com/kb/en/library/systemd/
>   Process: 6438 ExecStartPost=/etc/mysql/debian-start (code=exited,
> status=0/SUCCESS)
>   Process: 6436 ExecStartPost=/bin/sh -c systemctl unset-environment
> _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
>   Process: 6366 ExecStartPre=/bin/sh -c [ ! -e
> /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..;
> /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment
> _WSREP_START_POSITION=$VA
>   Process: 6357 ExecStartPre=/bin/sh -c systemctl unset-environment
> _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
>   Process: 6348 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root
> -d /var/run/mysqld (code=exited, status=0/SUCCESS)
>  Main PID: 6422 (mariadbd)
>    Status: "Taking your SQL requests now..."
>     Tasks: 9 (limit: 4915)
>    CGroup: /system.slice/mariadb.service
>            └─6422 /usr/sbin/mariadbd
>
> 002: Then I receive the following message (if Tomcat is running):
>
> mariadbd[6422]: 2021-11-24 19:38:00 243 [Warning] Access denied for
> user 'om_db_admin'@'localhost' (using password: YES)
>
> In openmeetings.log error: mariadb/sql is down
>
> 003: OM 6.0.0 runs on local server Ununtu 18
>
> 004:
> I can't access OM, the message:
> https://192.168.1.30:5443/openmeetings/notinited
>
> I've never seen 'om_db_admin' before.
>
> Thank you for your help.
>
>
>
>
>