Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
23.02.1
-
None
-
None
-
MXS-SPRINT-182
Description
While doing the data migration activity from PostgreSQL to MariaDB then maxscale is killing itself.
OS: Centos7
RAM: 16GB
Even though we have created one test schema with simple table but still we are getting the below issue. While fetching objects from source then we are getting the below issue.
NOTE: I did not find any details from the Maxscale logs.
Please find the error details from the system logs.
Apr 25 03:50:49 test201 maxscale: The 'log_debug' option has no effect in release mode.
Apr 25 03:50:49 test201 maxscale: The logging of debug messages has been enabled.
Apr 25 03:50:49 test201 maxscale: The logging of info messages has been enabled.
Apr 25 03:50:49 test201 maxscale: The logging of notice messages has been enabled.
Apr 25 03:50:49 test201 maxscale: The logging of warning messages has been enabled.
Apr 25 03:50:49 test201 maxscale: Using up to 2.32GiB of memory for query classifier cache
Apr 25 03:50:49 test201 systemd: Started MariaDB MaxScale Database Proxy.
Apr 25 04:00:11 test201 systemd: maxscale.service: main process exited, code=killed, status=11/SEGV
Apr 25 04:00:11 test201 systemd: Unit maxscale.service entered failed state.
Apr 25 04:00:11 test201 systemd: maxscale.service failed.
Apr 25 04:00:11 test201 systemd: maxscale.service holdoff time over, scheduling restart.
Apr 25 04:00:11 test201 systemd: Stopped MariaDB MaxScale Database Proxy.
Apr 25 04:00:11 test201 systemd: Starting MariaDB MaxScale Database Proxy...
Apr 25 04:00:11 test201 maxscale: /etc/maxscale.cnf.d does not exist, not reading.
Apr 25 04:00:11 test201 maxscale: The 'log_debug' option has no effect in release mode.
Apr 25 04:00:11 test201 maxscale: The logging of debug messages has been enabled.
Apr 25 04:00:11 test201 maxscale: The logging of info messages has been enabled.
Apr 25 04:00:11 test201 maxscale: The logging of notice messages has been enabled.
Apr 25 04:00:11 test201 maxscale: The logging of warning messages has been enabled.
Apr 25 04:00:11 test201 maxscale: Using up to 2.32GiB of memory for query classifier cache
Apr 25 04:00:11 test201 systemd: Started MariaDB MaxScale Database Proxy.
Apr 25 04:01:01 test201 systemd: Created slice User Slice of root.
Apr 25 04:01:01 test201 systemd: Started Session 6862 of user root.
Apr 25 04:01:01 test201 systemd: Removed slice User Slice of root.
Apr 25 04:04:10 test201 systemd: maxscale.service: main process exited, code=killed, status=11/SEGV
Apr 25 04:04:10 test201 systemd: Unit maxscale.service entered failed state.
Apr 25 04:04:10 test201 systemd: maxscale.service failed.
Apr 25 04:04:10 test201 systemd: maxscale.service holdoff time over, scheduling restart.
Apr 25 04:04:10 test201 systemd: Stopped MariaDB MaxScale Database Proxy.
Apr 25 04:04:10 test201 systemd: Starting MariaDB MaxScale Database Proxy...
Apr 25 04:04:10 test201 maxscale: /etc/maxscale.cnf.d does not exist, not reading.
Apr 25 04:04:10 test201 maxscale: The 'log_debug' option has no effect in release mode.
Apr 25 04:04:10 test201 maxscale: The logging of debug messages has been enabled.
Apr 25 04:04:10 test201 maxscale: The logging of info messages has been enabled.
Apr 25 04:04:10 test201 maxscale: The logging of notice messages has been enabled.
Apr 25 04:04:10 test201 maxscale: The logging of warning messages has been enabled.
Apr 25 04:04:10 test201 maxscale: Using up to 2.32GiB of memory for query classifier cache
Apr 25 04:04:10 test201 systemd: Started MariaDB MaxScale Database Proxy.