Quantcast
Channel: CentOS Bug Tracker - Issues
Viewing all articles
Browse latest Browse all 19115

0008452: [abrt] corosync: _poll_add_(): corosync killed by SIGABRT

$
0
0
Description of problem:<br /> Corosync crashes at least once per day on either of the two nodes. The<br /> configuration:<br /> <br /> totem {<br /> version: 2<br /> secauth: off<br /> cluster_name: sio-db<br /> transport: udpu<br /> rrp_mode: passive<br /> }<br /> <br /> nodelist {<br /> node {<br /> ring0_addr: sio-c01-db01<br /> ring1_addr: sio-c01-db01a<br /> nodeid: 1<br /> }<br /> node {<br /> ring0_addr: sio-c01-db02<br /> ring1_addr: sio-c01-db02a<br /> nodeid: 2<br /> }<br /> }<br /> <br /> quorum {<br /> provider: corosync_votequorum<br /> two_node: 1<br /> }<br /> <br /> logging {<br /> to_syslog: yes<br /> debug: on<br /> }<br /> <br /> Debug shows nothing intersting. Ring0 is connected through a tinc VPN which <br /> introduces latency, but otherwise is stable. Ring1 is directly connected<br /> via patchcable.<br /> <br /> Version-Release number of selected component:<br /> corosync-2.3.4-4.el7<br /> <br /> Truncated backtrace:<br /> Thread no. 1 (8 frames)<br /> #4 _poll_add_ at loop_poll.c:305<br /> #5 qb_loop_poll_add at loop_poll.c:353<br /> #6 qb_ipcs_shm_connect at ipc_shm.c:321<br /> #7 handle_new_connection at ipc_setup.c:510<br /> #8 process_auth at ipc_setup.c:694<br /> #9 _poll_dispatch_and_take_back_ at loop_poll.c:108<br /> #10 qb_loop_run_level at loop.c:43<br /> #11 qb_loop_run at loop.c:210

Viewing all articles
Browse latest Browse all 19115

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>