[MXS-268] Segmentation fault when using schemarouter through socket Created: 2015-07-14 Updated: 2015-09-01 Resolved: 2015-07-14 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbclient, schemarouter |
| Affects Version/s: | 1.2.0 |
| Fix Version/s: | 1.2.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Alex V. Yeskin | Assignee: | markus makela |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian 8.1 |
||
| Attachments: |
|
| Description |
|
Configured MaxScale as follows: [Shard service] [Shard listener] [srv_localhost] When starting service, MaxScale logging error in /var/log/maxscale/error1.log: When trying to connect using mysql console:
MaxScale fails with SIGSEGV: ==> error1.log <== (gdb) bt |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-07-14 ] |
|
Asgard MaxScale is not officially supported and test on Debian 8 as of 1.2.0. Can you reproduce it on Debian 7 ? |
| Comment by markus makela [ 2015-07-14 ] |
|
I could not reproduce with identical settings on Debian 7. |
| Comment by Alex V. Yeskin [ 2015-07-16 ] |
|
Debian 7 is not interested for some reasons. I tried to reproduce the bug on CentOS 7, but everything is ok there. Well, we should wait for Debian 8 support. |
| Comment by Aleksey Chernykh [ 2015-09-01 ] |
|
Could you provide some information about Debian 8 support plans? |
| Comment by Dipti Joshi (Inactive) [ 2015-09-01 ] |
|
Debain 8 support will be added in 1.3 |