[MDEV-9961] Garbd segfaults when using a configuration file on RH6 Created: 2016-04-21 Updated: 2017-11-29 Resolved: 2016-11-18 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera Arbitrator garbd |
| Affects Version/s: | 10.0.24-galera |
| Fix Version/s: | 10.1.20, 10.2.3, 5.5.54-galera, 10.0.29-galera |
| Type: | Bug | Priority: | Major |
| Reporter: | Art van Scheppingen | Assignee: | Nirbhay Choubey (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Redhat 6.7 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
On a Redhat 6.7 installation we see Garbd segfaulting when we use a configuration file when starting Garbd, on Redhat 7.1 we don't see this issue happening.
Nothing gets logged to the garbd log file.
The configuration files get generated by ClusterControl for both OS-es and contain the exact same information:
Also the garbd.log file exists and has the right permissions: if we start up Garbd with all the commandline parameters it is fine. Using strace gave us the folowing last few lines:
I have added the full strace to the report. The package we install: |
| Comments |
| Comment by Daniel Black [ 2016-04-21 ] |
|
I'd suggest setting 'ulimit -c unlimited' in the shell before running garb and then using "gdb `which garbd` core" to get a backtrace ("thread apply all bt full"). When you do use strace, use -s99 so that the text strings aren't limited to something too small. |
| Comment by Art van Scheppingen [ 2016-04-21 ] |
|
Thanks for the suggestion. Thread 1 (Thread 0x7fc412b177e0 (LWP 30096)): Do you need the core dump I created as well? |
| Comment by David Kedves [ 2016-06-01 ] |
|
I got exactly the same crash [ http://ftp.vim.org/db/mariadb/yum/10.1/centos6-amd64/rpms/galera-25.3.15-1.rhel6.el6.x86_64.rpm ] So my suggestion is, could you please guys re-build the package (and update the yum repos) on a recent centos6/rhel6 system? |
| Comment by Geoff Montee (Inactive) [ 2016-11-03 ] |
|
I submitted the same bug to Codership a while ago: https://github.com/codership/galera/issues/430 I did not realize that this bug may be specific to MariaDB's galera packages. |
| Comment by Nirbhay Choubey (Inactive) [ 2016-11-18 ] |
|
Fixed in Galera-25.3.19. |