[MXS-3471] After "clock has been changed to REALTIME" in syslog maxscale crashes Created: 2021-03-29  Updated: 2021-07-12  Resolved: 2021-04-01

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.7
Fix Version/s: 2.5.11

Type: Bug Priority: Major
Reporter: Claudio Nanni Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

Crashes have been reported when this event is logged in syslog:

The system clock has been changed to REALTIME microseconds after January 1st, 1970

-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Mar 29 12:37:29 marai maxscale[114412]: (199150) MaxScale 2.5.7 received fatal signal 11. Commit ID: cec605f3894b2098329fea2685edcec38d9764ed System name: Linux Release string: NAME="Oracle Linux Server"
Mar 29 12:37:29 marai systemd[1]: maxscale.service: main process exited, code=killed, status=11/SEGV
 
== syslog =================================================================
 
Mar 29 13:11:38 marai systemd[1]: Time has been changed
-- Subject: Time change
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Mar 29 13:11:39 marai maxscale[52481]: (812) MaxScale 2.5.7 received fatal signal 6. Commit ID: cec605f3894b2098329fea2685edcec38d9764ed System name: Linux Release string: NAME="Oracle Linux Server"
Mar 29 13:11:39 marai maxscale[52481]: (812) Statement currently being classified: none/unknown
Mar 29 13:11:40 marai maxscale[52481]: (812) 
                                         /lib64/libc.so.6(gsignal+0x37): :?
                                         /lib64/libc.so.6(abort+0x148): :?
                                         /lib64/libc.so.6(+0x78de7): :?
                                         /lib64/libc.so.6(+0x82d56): malloc.c:?
                                         /lib64/libc.so.6(__libc_malloc+0x4c): :?
                                         /lib64/libc.so.6(open_memstream+0x1a): :?
                                         /lib64/libc.so.6(__vsyslog_chk+0x7a): :?
                                         /lib64/libc.so.6(syslog+0x8f): :?
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(mxb_log_message+0x73b): maxutils/maxbase/src/log.cc:898
                                         /usr/bin/maxscale(): server/core/gateway.cc:451
                                         /lib64/libpthread.so.0(+0xf5d0): sigaction.c:?
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZNK7Session18adjust_io_activityEl+0x50): /opt/rh/devtoolset-7/root/usr/include/c++/7/bits/stl_algobase.h:696
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7Session16book_io_activityEv+0x1f): server/core/session.cc:1567
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN3DCB14process_eventsEj+0xaf): server/core/dcb.cc:1338
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN3DCB13event_handlerEPS_j+0x21): server/core/dcb.cc:1351
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1be): maxutils/maxbase/src/worker.cc:879
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:574
                                         /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x229bef): thread48.o:?
                                         /lib64/libpthread.so.0(+0x7dd5): pthread_create.c:?
                                         /lib64/libc.so.6(clone+0x6d): ??:?
Mar 29 13:11:40 marai systemd[1]: maxscale.service: main process exited, code=killed, status=6/ABRT
Mar 29 13:11:40 marai systemd[1]: Unit maxscale.service entered failed state.
Mar 29 13:11:40 marai systemd[1]: maxscale.service failed.
Mar 29 13:11:40 marai systemd[1]: maxscale.service holdoff time over, scheduling restart.
Mar 29 13:11:40 marai systemd[1]: Stopped MariaDB MaxScale Database Proxy.

== maxscale log ===========================================
2021-03-29 12:37:30   notice : Read 31 user@host entries from 'server1' for service 'Standalone-Service'.
*** Error in `/usr/bin/maxscale': malloc(): memory corruption: 0x00007f0ed0046200 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x82d56)[0x7f0ee7906d56]
/lib64/libc.so.6(__libc_malloc+0x4c)[0x7f0ee790926c]
/lib64/libc.so.6(open_memstream+0x1a)[0x7f0ee78fb8ea]
/lib64/libc.so.6(__vsyslog_chk+0x7a)[0x7f0ee797baba]
/lib64/libc.so.6(syslog+0x8f)[0x7f0ee797c01f]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(mxb_log_message+0x73b)[0x7f0eea5d6f6b]
/usr/bin/maxscale[0x409e8e]
/lib64/libpthread.so.0(+0xf5d0)[0x7f0ee967b5d0]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZNK7Session18adjust_io_activityEl+0x50)[0x7f0eea5c2950]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7Session16book_io_activityEv+0x1f)[0x7f0eea5c29af]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN3DCB14process_eventsEj+0xaf)[0x7f0eea546a7f]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN3DCB13event_handlerEPS_j+0x21)[0x7f0eea546bc1]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1be)[0x7f0eea5df6de]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53)[0x7f0eea5df8f3]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x229bef)[0x7f0eea681bef]
/lib64/libpthread.so.0(+0x7dd5)[0x7f0ee9673dd5]
/lib64/libc.so.6(clone+0x6d)[0x7f0ee7981f6d]
======= Memory map: ========



 Comments   
Comment by Sergei Wallgren [ 2021-03-30 ]

FYI.
I've seen these same errors also on server with MaxScale 2.5.4.

Did NOT see this problem on

Generated at Thu Feb 08 04:21:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.