-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mariadb crashing since 2.5.0 #893
Comments
Ugh. Maybe: go-fuse was updated from v2.3.0 to v2.5.0: https://github.com/rfjakob/gocryptfs/compare/v2.4.0..v2.5.0#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6L7 Let me try to repro this. |
And, what CPU do you have? Maybe f5007b2 |
Yes, it is an AMD EPYC 9634 |
Oh, I missed Edit2. Do you have the whole backtrace for |
You mean this one?
|
I was hoping for line numbers, but better than nothing. I failed to to get mariadb to run on gocryptfs due to SELinux (do you have a hint beside disabling selinux?) I am doing this ( https://optimizedbyotto.com/post/grokking-mariadb-test-run-mtr/ ):
/tmp/mysql-test.b is a gocryptfs mount. Let's see. |
For SELinux: |
Well. mariadb-test failed, but it also failed on plain ext4 (differently). So that's not a very good reproducer. How do you trigger the crash? |
It seems very random. Mostly it occurs when one of my cronjobs runs which is triggering a PHP skript which is doing something with the DB. A lot of calls are OK, but maybe once in a hour it crashes. |
Looking |
After dropping
But I just realized I missed the critical ingredient of running gocryptfs as root with |
That did the trick. I got a crash, and also some |
Here we go. Same "Operation not permitted" issue.
|
Hmm, unfortunately my mariadb did not log such a thing, not in /var/log/mariadb/mariadb.log nor journald. |
@johnassel if you need a workaround I have set up my gocryptfs mounts to use a script that calls For example:
and the fstab entry looks like:
|
Ah ok - my workaround is reverting to 2.4.0 for now. |
Reproducer script: https://gist.github.com/rfjakob/411d5b77bb39322eee3aca769b1d9577 |
Looks like golang/sys@d0df966 broke it. |
I'm running the mariadb data directory (/var/lib/mysql/) inside a gocryptfs mount.
After upgrading to 2.5.0 I'm experiencing frequent crashes of the maridb process:
Process 39501 (mariadbd) crashed in page_cur_tuple_insert(page_cur_t*, dtuple_t const*,...
There might be an underlying problem with permissions or such since I'm getting errors for cronjobs which are calling php scripts inside a gocryptfs directory since 2.5.0, too.
Failed to open stream: Permission denied in ...
But these are way more rare than the crashes of the mariadb daemon.
Going back to 2.4.0 fixes both problems.
The gocryptfs mount is mounted throught the root account using the -allow_other flag.
System is a Fedora 41 with the static binaries on ext4.
I'm not sure how to debug this futher, since gocryptfs does not log anything in normal mode.
It looks somewhat similar to #892 but for me older versions are working.
Edit: Startet the mount with --debug. Waiting now for a crash to happen.
Edit2: It seems (as mentioned in the issue above, too) as if --debug stops the crashes.
The text was updated successfully, but these errors were encountered: