INSTALL SONAME fails because TidesDB can't find my.cnf

[mdcallag]

I don't know if this is a bug.

I built MariaDB + TidesDB with: "-DDEFAULT_SYSCONFDIR=/home/mdcallag/d/ma120202_tides/etc"

And then this happens. Is it hardwired to look in $mysql_data_dir/etc/my.cnf? The datadir I use is /data/m/my/data but I don't put etc there.

MariaDB [(none)]> INSTALL SONAME 'ha_tidesdb';
ERROR 1524 (HY000): Plugin '(null)' is not loaded
MariaDB [(none)]> quit

From the error log I see:

Could not open required defaults file: /data/m/my/data/etc/my.cnf
Fatal error in defaults handling. Program aborted

[guycipher]

Oh that's odd. I haven't seen that one.

The '(null)' name seems to be MariaDB failing to read the plugin descriptor from ha_tidesdb.so. It looks to be like MariaDB either can't find the plugin fully or libtidesdb.so.

Uh we don't really hardwire anything like that specifically. TidesDB lives where MariaDB lives, data, configuration etc.

Above would be mysql_home, TidesDB lives in mysql_home/tidesdb_data

Where plugin lives.

It really looks like a sequence of events caused the server to start in a way where it can't read the plugin fully or the plugin wasn't built against a proper TidesDB library, though ABI and all though be compatible.

I could be completely wrong, if you have steps in which I can reproduce that would be mighty helpful.

Thank you Mark.

[mdcallag]

I followed the steps for a manual build using MariaDB 12.2.2 and TidesDB 9.0.9

With this as cmk.relwithdbg
The cmake command line was: bash ../cmk.relwithdbg ~/d/ma120202_tides

I initialize the server via this script.
And note (see here) that I copy my.cnf to the place where TidesDB checks. That is my workaround.

To run the init script, put the my.cnf in a file named etc/my.cnf.cfoobar
Then: bash ini.sh foobar
Yes, foobar, not cfoobar, odd naming convention I have been using forever.

The my.cnf is here.

[guycipher]

Ah very good, thank you Mark. I've spent some time and from my investigation this is not a plugin issue but a relative-path resolution quirk in the MariaDB server itself.

mariadbd chdirs to datadir at startup, and INSTALL SONAME re-reads the original --defaults-file= string unchanged, so your relative etc/my.cnf now resolves to /data/m/my/data/etc/my.cnf and fails, which is why you see Plugin '(null)' is not loaded. The plugin itself doesn't touch defaults files.