Fresh install on centos with MariaDB

I am struggeling to install xwiki on a centos machine. This is a new install, new and empty xwiki database.
My setting:
Tomcat 9.0.37
Java 11.0.7
xwiki-platform-distribution-war-12.7.1.war
mariadb 10.0
mariadb-java-client-2.6.2.jar

08-Sep-2020 17:59:56.870 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.37
08-Sep-2020 17:59:56.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Jun 30 2020 20:09:49 UTC
08-Sep-2020 17:59:56.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.37.0
08-Sep-2020 17:59:56.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
08-Sep-2020 17:59:56.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            3.10.0-1127.13.1.el7.x86_64
08-Sep-2020 17:59:56.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
08-Sep-2020 17:59:56.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jvm/java-11-openjdk-11.0.7.10-4.el7_8.x86_64
08-Sep-2020 17:59:56.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           11.0.7+10-LTS
08-Sep-2020 17:59:56.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
08-Sep-2020 17:59:56.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /opt/tomcat/apache-tomcat-9.0.37
08-Sep-2020 17:59:56.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /opt/tomcat/apache-tomcat-9.0.37

=> tomcat is starting up perfectly.
after accessing xwiki I find the following bug in the catalina.out file:

2020-09-08 18:00:31,967 [XWiki initialization] INFO  .HibernateDataMigrationManager - Checking Hibernate mapping and updating schema if needed for wiki [xwiki]
2020-09-08 18:00:33,623 [XWiki initialization] INFO  .HibernateDataMigrationManager - Storage schema updates and data migrations are enabled
2020-09-08 18:00:33,772 [XWiki initialization] INFO  .HibernateDataMigrationManager - No data migration to apply for wiki [xwiki] currently in version [1138000]
2020-09-08 18:00:33,772 [XWiki initialization] INFO  .HibernateDataMigrationManager - Checking Hibernate mapping and updating schema if needed for wiki [xwiki]
2020-09-08 18:00:34,211 [XWiki initialization] WARN  o.h.e.j.s.SqlExceptionHelper   - SQL Error: 1146, SQLState: 42S02
2020-09-08 18:00:34,211 [XWiki initialization] ERROR o.h.e.j.s.SqlExceptionHelper   - (conn=2441738) Table 'xwiki.xwikiproperties' doesn't exist
2020-09-08 18:00:34,232 [XWiki initialization] ERROR c.x.x.XWiki                    - Failed to initialize mandatory document
com.xpn.xwiki.XWikiException: Error number 3201 in 3: Exception while saving document xwiki:XWiki.GlobalRedirect

and a lot of error messages following.
My mariadb config seems to work, because there are several tables created after accessing the xwiki homepage, but at all there were only 25 tables created. I think there missing some tables, right?

What could be the cause for my bug?

Thank you
Peter

Definitely (you should have 39 tables), one of them being xwikiproperties according to the log but no idea why since I don’t see anything in the log that could explain why this table was not created.

It’s a very strange behavior since it’s usually all or nothing, is it possible that you don’t have enough place left where MariaDB databases are stored ?

I don’t remember any similar issue and XWiki definitely work fine with MariaDB (it’s part of our automated tests and many people use that these days since that’s what you get by default when using the XWiki MySQL Debian packages) so not much other idea. I guess you tried several times already ?

yes I have deleted the db several times, no change.
Ist there any script which only installs the database, which I can run by manually?
really strange…

Dear all, I have the same problem with a fresh install on mariadb. This is the set of tables that were created:

+-------------------------------+
| Tables_in_xwiki               |
+-------------------------------+
| activitystream_events         |
| activitystream_events_targets |
| feeds_aggregatorgroup         |
| feeds_aggregatorurl           |
| feeds_aggregatorurlgroups     |
| feeds_feedentry               |
| feeds_feedentrytags           |
| feeds_keyword                 |
| notification_filter_prefs     |
| xwikiattachment               |
| xwikiattachment_archive       |
| xwikiattachment_content       |
| xwikiattrecyclebin            |
| xwikicomments                 |
| xwikidbversion                |
| xwikidoc                      |
| xwikilock                     |
| xwikiobjects                  |
| xwikipreferences              |
| xwikircs                      |
| xwikirecyclebin               |
| xwikispace                    |
| xwikistatsdoc                 |
| xwikistatsreferer             |
| xwikistatsvisit               |
+-------------------------------+

Tried multiple times, no effect.

Problem seems to be related to mariadb. With mysql it worked.

What driver class and what JDBC driver have you used for MariaDB?

Thanks

BTW the supported version is indicated here: https://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy/DatabaseSupportStrategy

So that’s 10.4 and 10.5 ATM.

Maybe you could try this and also make sure you use the MariaDB driver and not the MySQL one, maybe MariaDB has now diverged and is no longer a drop-in replacement for MySQL. See https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/InstallationWAR/InstallationMariaDB/

I used the debian packages xwiki-tomcat9-mariadb, so it was the jdbc driver that came with this package. Can’t check it now because it’s already deinstalled (before I installed xwiki-tomcat9-mysql)

I finally analyzed this missing tables issue and you can find details on Loading.... In short XWiki simply does not work out of the box with MariaDB versions lower than 10.2 if you use utf8mb4 encoding because of the default maximum size of the key in those versions.