Open Lejooohn opened 3 years ago
I am seeing similar issues w/ 5.7.33 and the latest rev of the plugin
The offsets are automatically detected, and 5.7.33 is officially supported so I do not believe it to be strictly offset related. Though capturing the offsets manually did provide one additional value vs what was already detected, which was a "0"
root/offset-extract.sh ./sql/mysqld //offsets for: ./sql/mysqld (5.7.33) {"5.7.33","dfe9f47ea91dcddd7683092402db1315", 7824, 7872, 3632, 4792, 456, 360, 0, 32, 64, 160, 536, 7988, 4360, 3648, 3656, 3660, 6072, 2072, 8, 7056, 7096, 7080, 13472, 148, 672, 0},
Host environment is RHEL 8.4, which does change the game a bit w/r/t core system libraries, compiler used to compile mysqld and boost as well as the plugin.
@Lejooohn We were able to work around this by rebuilding the mysql-community packages. It is highly likely your mysqld was compiled w/ -fcf-protection enabled which hardens the code and also makes it impossible to hotpatch the necessary memory locations
On RHEL, we circumvented by modifying the flags included in the rpmrc file, not sure where these flags are set in Debian but I assume apt has similar wrappers for compiling packages. I would start your investigation there.
Hi everyone,
I'm facing an issue when i try to install the latest version of the plugin v1.1.8 normally compatible with MySQL 5.7.33. It run on Debian 10 up2date.
When i try to recover the offset :
Content of my.cnf :
the error log show :
I tried to register it manually :
mysql> INSTALL PLUGIN AUDIT SONAME 'libaudit_plugin.so'; ERROR 1123 (HY000): Can't initialize function 'AUDIT'; Plugin initialization function failed.
Did i something wrong? Maybe someone already have the correct offset for this version? :)
Regards,