[MDEV-7423] Weird behaviour with failing plugin library. Created: 2015-01-08 Updated: 2015-01-08 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Plugins |
| Affects Version/s: | 5.5.41 |
| Fix Version/s: | 5.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Alexey Botchkov | Assignee: | Alexey Botchkov |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
though:
|
| Comments |
| Comment by Elena Stepanova [ 2015-01-08 ] | |||||||||||||||||||||||||||
|
Doesn't fail like that for me:
Do you actually have something in mysql.plugin? Did you have anything there before the failed attempt? | |||||||||||||||||||||||||||
| Comment by Sergei Golubchik [ 2015-01-08 ] | |||||||||||||||||||||||||||
|
What is this bug report about? The "version `GLIBC_2.14' not found" error? Or how INSTALL/UNINSTALL behave when plugin installation fails? Or both? | |||||||||||||||||||||||||||
| Comment by Elena Stepanova [ 2015-01-08 ] | |||||||||||||||||||||||||||
|
To my understanding it's about the inconsistent state that the plugin ends up after the failed installation attempt (something is written to mysql.plugin, although the plugin was not installed and hence cannot be uninstalled). But I couldn't reproduce it so far. |