I first reported this as bugzilla bug 280165 on July 6th for mysql80-server-8.0.35_1 and mysql81-server-8.1.0 and subsequently added mysql84-server-8.4.0 on August 4th starting from a brand new image of the OS, and it was assigned to someone, but I've heard nothing from them. The daemon gets a SIGILL during startup, so it's pretty severe. I did some research and got stack traces. There's also a file ownership problem in the pkg. Is noone else experiencing this problem? Is there anything I can do to help move this along? What's the next step? I tried to reach out to Oracle, but all they would say is that they don't support FreeBSD.
I really need to resolve this because something very bizarre has happened on my FreeBSD 13.1 system. Even though the database is still up and running, the pkg and all its file (links) have disappeared. I am assuming the system retains a phantom link count to the inode as long as a program is running, like it does for a regular open, because top/htop shows /usr/local/libexec/mysqld even though "ls" can't see it. My only guess is that when I did a pkg autoremove, it had unintended consequences, but for the moment, I am afraid to reboot the system or mess with it in any way since I won't be able to restart the database. There's a fair chance that I could reboot and reinstall the mysql80-server, but it's not a risk I'm ready to take.
I really need to resolve this because something very bizarre has happened on my FreeBSD 13.1 system. Even though the database is still up and running, the pkg and all its file (links) have disappeared. I am assuming the system retains a phantom link count to the inode as long as a program is running, like it does for a regular open, because top/htop shows /usr/local/libexec/mysqld even though "ls" can't see it. My only guess is that when I did a pkg autoremove, it had unintended consequences, but for the moment, I am afraid to reboot the system or mess with it in any way since I won't be able to restart the database. There's a fair chance that I could reboot and reinstall the mysql80-server, but it's not a risk I'm ready to take.