[MXS-3718] MaxScale killed by watchdog timeout Created: 2021-08-10  Updated: 2021-11-01  Resolved: 2021-09-02

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.12
Fix Version/s: 2.5.16

Type: Bug Priority: Major
Reporter: Pon Suresh Pandian (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Ubuntu - 20.04.2 LTS (Focal Fossa)


 Description   

If the OS time is adjusted backwards by several hours, MaxScale will be killed by the systemd watchdog.

Reproduced with:

timedatectl set-ntp false
 
timedatectl set-local-rtc false
 
timedatectl set-time 04:51:14

Original description:
Hi Team,

In MaxScale log the time was updating backwards during the maxscale crash.

Here I have attached the maxscale log as-well as system logs too.. Please check it.

From Maxscale Log :
--------------------

2021-08-10 21:39:56   notice : Server changed state: basel2-alm-ftp-db1[10.1.11.51:3306]: new_master. [Slave, Running] -> [Master, Running]
 
2021-08-10 21:39:56   notice : Server changed state: basel2-alm-ftp-db2[10.1.11.52:3306]: new_slave. [Master, Running] -> [Slave, Running]
 
2021-08-10 14:45:06   alert  : MaxScale 2.5.12 received fatal signal 6. Commit ID: 7cff3faf7b1237d037ee1b6526add9a56cbc580e System name: Linux Release string: Ubuntu 20.04.2 LTS
 
2021-08-10 14:45:06   alert  : Statement currently being classified: none/unknown
 
nm: /lib/x86_64-linux-gnu/libc.so.6: no symbols
 
nm: /lib/x86_64-linux-gnu/libc.so.6: no symbols
 
2021-08-10 14:45:06   alert  : 
  /lib/x86_64-linux-gnu/libc.so.6(epoll_wait+0x5e): ??:0
 
  /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x125): maxutils/maxbase/src/worker.cc:815
 
  /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x57): maxutils/maxbase/src/worker.cc:574
 
  /usr/bin/maxscale(main+0x1b3b): maxutils/maxbase/include/maxbase/log.h:168
 
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3): ??:0
 
  /usr/bin/maxscale(_start+0x2e): ??:?



 Comments   
Comment by Pon Suresh Pandian (Inactive) [ 2021-08-11 ]

Hi Markus,

Sure I will remove those files. And it was already attached in support case.

Comment by markus makela [ 2021-08-24 ]

This could potentially be caused by a hang on shutdown but the stacktrace does suggest otherwise.

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