In the attached log there are two problems found:
1. Two cases where maxscale received a signal 11 and generated a stack trace and was restarted
2. This log was saved when maxscale was apparently hung. There were a number of maxadmin list server commands hung (which we do to verify sanity of maxscale). Running a maxadmin list server just hangs.

Once we killed all the hung maxadmin list server processes and restarted maxscale, everything was back to normal.

So two questions:
(a) why is maxscale taking a signal 11 and restarting
(b) why is maxscale hanging (unfortunately this is container environment so there is no backtrace capability).