[MXS-371] Fatal: MaxScale received fatal signal 11. Created: 2015-09-16 Updated: 2015-09-22 Resolved: 2015-09-22 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbbackend |
| Affects Version/s: | 1.2.0 |
| Fix Version/s: | 1.2.1 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Jakob Ackermann | Assignee: | Johan Wikman |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
OpenVZ Centos 7 running on Proxmox(Debian) |
||
| Description |
|
2015-09-16 09:14:07 Fatal: MaxScale received fatal signal 11. Attempting backtrace. Maxscale configuration: [maxscale] #we have to move the pid file for pcs [Galera Monitor] monitor_interval=10000 disable_master_failback=1 [RWSplitRouter] type=service router=readwritesplit servers=server1,server2 user=maxscale passwd={hash} max_slave_connections=100% [RWSplitListener1] [RWSplitListener2] [server1] [server2] Two different applications connection to both listening IP and maxscale stops suddenly. I could not find anything relevant in the trace or debug log. |
| Comments |
| Comment by markus makela [ 2015-09-21 ] |
|
Does the query traffic going through MaxScale contain prepared statements? If it does, this seems like a duplicate of |
| Comment by Jakob Ackermann [ 2015-09-21 ] |
|
Yes, I use prepare statements. Is the new package available in the Enterprise Repository? |
| Comment by Jakob Ackermann [ 2015-09-21 ] |
|
I apologize for not taking the step and review the state of version 1.2.1. Once it will make to repository I will check and report back. Thanks. |
| Comment by markus makela [ 2015-09-22 ] |
|
If you can build MaxScale from source, you can try out the release-1.2.1 branch. Here's a guide on how to build MaxScale from source. |