[mythtv-users] fedora 42, mariadb 10.11.15-1 crashing repeatedly

[Brendan Kearney]

On 1/15/26 9:41 AM, Eyal Lebedinsky via mythtv-users wrote:
> On 15/1/26 11:21, Eyal Lebedinsky via mythtv-users wrote:
>> Just did an update/reboot and mariadb is crashing repeatedly.
>>      Version    3:10.11.15-1
>>      Downgraded, to 3:10.11.11-1 and it works.
>> See log below.
>>
>> Any chance that some cleanup is required due to incompatibility?
>> Maybe in /var/lib/mysql (see below)?
>> Elsewhere? Any log file I can provide?
>>
>> TIA
>
> Short story: almost sorted.
>
> I decided to again install 10.11.15 and surely it was reliably crashing.
>
> After looking carefully at mariadb.log I saw this as it was aborting:
>
> 2026-01-15  9:43:38 0 [ERROR] mariadbd: Can't create/write to file 
> '/run/mariadb/mariadb.pid' (Errcode: 2 "No such file or directory")
> 2026-01-15  9:43:38 0 [ERROR] Can't start server: can't create PID 
> file: No such file or directory
> terminate called without an active exception
> 260115  9:43:38 [ERROR] /usr/libexec/mariadbd got signal 6 ;
>
> After pondering the situation, I thought that maybe an old pid file 
> was left behind. Not so, there is none.
> I then found that the actual directory is missing, so I created it and 
> made it mysql:mysql. maria db started OK.
>
> This is strange. I was just running 10.11.11 happily, how come the 
> directory went awol when upgrading 10.11.11 -> 10.11.15?
> An installer issue?
>
> The good news is that now mariadb starts fine. However, will the 
> directory stay?
>
> ... reboot... it may b
>
> nope, the directory is missing again!
>     $ sudo mkdir /run/mariadb/
>     $ sudo chown mysql:mysql /run/mariadb/
> and no more crashing.
>
> Something funny is going on here.
> - Something to do with the /run vs. /var/run?
> - Is this directory supposed to be created by mariadb when it starts?
> - Am I missing an obscure mariadb package that takes care of this?
>
> dnf says:
>     Installed packages
>     mariadb-backup.x86_64                  3:10.11.15-1.fc42 updates
>     mariadb-client-utils.noarch            3:10.11.15-1.fc42 updates
>     mariadb-common.noarch                  3:10.11.15-1.fc42 updates
>     mariadb-cracklib-password-check.x86_64 3:10.11.15-1.fc42 updates
>     mariadb-devel.x86_64                   3:10.11.15-1.fc42 updates
>     mariadb-embedded.x86_64                3:10.11.15-1.fc42 updates
>     mariadb-errmsg.noarch                  3:10.11.15-1.fc42 updates
>     mariadb-gssapi-server.x86_64           3:10.11.15-1.fc42 updates
>     mariadb-rocksdb-engine.x86_64          3:10.11.15-1.fc42 updates
>     mariadb-server.x86_64                  3:10.11.15-1.fc42 updates
>     mariadb-server-utils.noarch            3:10.11.15-1.fc42 updates
>
> So we are close but no cigar yet. Hoping someone has a clue.
>
it may be the tmpfiles config is missing the correct entries to create 
that directory...

[root at server1 ~]# rpm -ql mariadb-server |grep tmp
/usr/lib/tmpfiles.d/mariadb.conf

[root at server1 ~]# cat /usr/lib/tmpfiles.d/mariadb.conf
# Do not edit this file.
# To override this, put /etc/tmpfiles.d/mariadb.conf instead.
d /run/mariadb 0755 mysql mysql -
d /run/mariadb 0755 mysql mysql -

maybe you need to correct what is in the tmpfiles.d config, or add the 
drop-in file to correct things?