[Bug 270807] mysqld got signal 4 ;Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270807

            Bug ID: 270807
           Summary: mysqld got signal 4 ;Most likely, you have hit a bug,
                    but this error can also be caused by malfunctioning
                    hardware.
           Product: Ports & Packages
           Version: Latest
          Hardware: arm64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: federicogalvezdurand@yahoo.com

mysql80-server stop working at version 8.0.26
1) All versions after 8.0.26 do not start, with the same "got signal 4 ...".
I have tried with RELEASE 13.0, 13.1 and 13.2. All the same.
I managed to run 8.0.26 in all of them, clean and efficient.
But I can not upgrade because all other versions fail.
2) I have already tried removing all previous files in /var/db/mysql and
/usr/local/etc/mysql; that is, a clean start. Nothing changes. All versions
after 8.0.26 fail.
3) I have tried this in two different Raspberrypi boards: rpi3 B+ 1G RAM, rpi4
8G RAM. Both the same.
rpi4 is running ZFS, offering NAS (samba43) and minildna in my local network
(FreeBSD + MacOS), clean and stable, now on 13.2-RELEASE.
rpi3 is running Apache24 + MySQL 80.0.26 + python39, clean and stable, now on
13.2-RELEASE.
No hardware failures detected, ever.
4) admin@rpi4% sudo pkg check -dna
Checking all packages: 100%
mysql80-server is missing a required shared library: libprotobuf.so.3.19.4
BUT, we do have protobuf installed in a most recent version.
admin@rpi4% sudo pkg info | grep protobuf
protobuf-3.20.1,1              Data interchange format library
py39-protobuf-3.20.1,1         Google protobuf Python Client Library
I created a symbolic link to cover for missing 3.19.4, it does not make a
difference. 
I am running 8.0.26 patching older libraries required with symbolic links to
newer ones and surprisingly works:
(/usr/local/lib)
ln -s libicuuc.so.72.1 libicuuc.so.69
ln -s libicuio.so.72.1 libicuio.so.69
ln -s libicudata.so.72.1 libicudata.so.69
ln -s libicui18n.so.72.1 libicui18n.so.69
ln -s libprotobuf-lite.so.32.0.12 libprotobuf-lite.so.28

Last try at uname -a:
FreeBSD rpi4.local 13.2-RELEASE FreeBSD 13.2-RELEASE
releng/13.2-n254617-525ecfdad597 GENERIC arm64.

tail -20 /var/log/mysqld.log:
2023-04-12T21:36:24.388389Z 0 [System] [MY-013169] [Server]
/usr/local/libexec/mysqld (mysqld 8.0.32) initializing of server in progress as
process 5667
2023-04-12T21:36:24.403051Z 0 [System] [MY-013951] [Server] A backtrace was
processed and added to the main error-log in the appropriate format.
mysqld: Error on delete of '/var/db/mysql/auto.cnf' (OS errno 2 - No such file
or directory)
2023-04-12T21:36:24.403410Z 0 [Warning] [MY-010107] [Server] World-writable
config file '/var/db/mysql/auto.cnf' has been removed.
2023-04-12T21:36:24.415309Z 1 [System] [MY-013576] [InnoDB] InnoDB
initialization has started.
2023-04-12T21:36:25Z UTC - mysqld got signal 4 ;
Most likely, you have hit a bug, but this error can also be caused by
malfunctioning hardware.
Thread pointer: 0x95c9f000
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Fatal signal 11 while backtracing

-- 
You are receiving this mail because:
You are the assignee for the bug.