Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.5.17, 6.2.0
-
None
Description
xpandmon hits a debug assertion when servers are unlinked from it.
2022-01-07 06:35:09 notice : [xpandmon] Xpand-Monitor: Monitoring Xpand cluster state using node 10.166.0.38:3306.
|
debug assert at /home/timofey_turenko_mariadb_com/MaxScale/server/modules/monitor/xpandmon/xpandmonitor.cc:676 failed: !SERVER::find_by_unique_name(server_name)
|
alert : MaxScale 6.2.1 received fatal signal 6. Commit ID: 500cd2476ff7fbbabbc39d3f96c18b391ec44c02 System name: Linux Release
|
string: Red Hat Enterprise Linux Server release 7.9 (Maipo)
|
|
|
|
|
/lib64/libpthread.so.0(+0xf630): sigaction.c:?
|
/lib64/libpthread.so.0(raise+0x2b): ??:?
|
/usr/lib64/maxscale/libxpandmon.so(_ZN12XpandMonitor13refresh_nodesEP8st_mysql+0x14dd): server/modules/monitor/xpandmon/xpandmonitor.cc:678
|
/usr/lib64/maxscale/libxpandmon.so(_ZN12XpandMonitor13refresh_nodesEv+0x148): server/modules/monitor/xpandmon/xpandmonitor.cc:593
|
/usr/lib64/maxscale/libxpandmon.so(_ZN12XpandMonitor13check_clusterEN5xpand10SoftfailedE+0xe2): server/modules/monitor/xpandmon/xpandmonitor.cc:884
|
/usr/lib64/maxscale/libxpandmon.so(_ZN12XpandMonitor9configureEPKN8maxscale16ConfigParametersE+0x25c): server/modules/monitor/xpandmon/xpandmonitor.cc:299
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN14MonitorManager19reconfigure_monitorEPN8maxscale7MonitorERKNS0_16ConfigParametersE+0x27b): server/core/monitormanager.cc:336
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_Z31runtime_alter_monitor_from_jsonPN8maxscale7MonitorEP6json_t+0x4e5): server/core/config_runtime.cc:2171
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x6f1c4a): server/core/resource.cc:457
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZNK8Resource4callERK11HttpRequest+0xb1): server/core/resource.cc:152
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x702114): server/core/resource.cc:1552 (discriminator 1)
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x705569): server/core/resource.cc:1750
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7062dd): server/core/resource.cc:1812 (discriminator 1)
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x706efd): /opt/rh/devtoolset-7/root/usr/include/c++/7/bits/std_function.h:318
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZNKSt8functionIFvvEEclEv+0x5c): /opt/rh/devtoolset-7/root/usr/include/c++/7/bits/std_function.h:706
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x9774fc): maxutils/maxbase/src/worker.cc:498
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker14handle_messageERNS_12MessageQueueERKNS_19MessageQueueMessageE+0x192): maxutils/maxbase/src/worker.cc:659
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase12MessageQueue18handle_poll_eventsEPNS_6WorkerEj+0x3ba): maxutils/maxbase/src/messagequeue.cc:307
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase12MessageQueue12poll_handlerEP13MXB_POLL_DATAP10MXB_WORKERj+0x31): maxutils/maxbase/src/messagequeue.cc:343
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0xf72): maxutils/maxbase/src/worker.cc:854
|
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x207): maxutils/maxbase/src/worker.cc:563
|
/usr/bin/maxscale(_ZN7maxbase6Worker3runEv+0x1d): maxutils/maxbase/include/maxbase/worker.hh:448
|
/usr/bin/maxscale(main+0x2db7): server/core/gateway.cc:2234
|
/lib64/libc.so.6(__libc_start_main+0xf5): ??:?
|
/usr/bin/maxscale(): ??:?
|
alert : Writing core dump.
|
This can be reproduced by running the xpand_basics test, starting MaxScale and then executing the following maxctrl command:
maxctrl unlink monitor Xpand-Monitor xpand_server2 xpand_server3 xpand_server4
|