-- Logs begin at Fri 2021-08-27 21:16:23 AEST, end at Wed 2021-09-01 22:07:44 AEST. -- Sep 01 21:57:30 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-um3Rbm.pdf Sep 01 21:57:30 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 21:57:30 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 21:57:30 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 21:57:31 ded101527.smartservers.com.au node[32625]: 2021-09-01T11:57:31.300Z INFO: >> Generating EXOZ-voucher-f9OWuj.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964119/216592671/44f3a51c66c5c16ce1b942d144abfb4b2a119289 on port 6928 Sep 01 21:57:31 ded101527.smartservers.com.au node[32625]: 2021-09-01T11:57:31.300Z INFO: << EXOZ-voucher-f9OWuj.pdf generated for https://transactional.ticketmates.net.au/voucher/4964119/216592671/44f3a51c66c5c16ce1b942d144abfb4b2a119289 on /tmp/EXOZ-voucher-f9OWuj.pdf Sep 01 21:57:31 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 21:57:31 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 21:57:31 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 21:57:31 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 21:57:31 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964119/216592671/44f3a51c66c5c16ce1b942d144abfb4b2a119289 Sep 01 21:57:32 ded101527.smartservers.com.au node[32625]: Wait for load took 69ms Sep 01 21:57:32 ded101527.smartservers.com.au node[32625]: Wait for js execution took 4ms Sep 01 21:57:32 ded101527.smartservers.com.au node[32625]: Wait for animations took 100ms Sep 01 21:57:32 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-f9OWuj.pdf Sep 01 21:57:32 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 21:57:32 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 21:57:32 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: 2021-09-01T11:57:58.034Z INFO: >> Generating EXOZ-voucher-D8Gbuk.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964125/216592676/b99ba11fab7338f3c3c8c377a9d8e090b0828a3a on port 6929 Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: 2021-09-01T11:57:58.035Z INFO: << EXOZ-voucher-D8Gbuk.pdf generated for https://transactional.ticketmates.net.au/voucher/4964125/216592676/b99ba11fab7338f3c3c8c377a9d8e090b0828a3a on /tmp/EXOZ-voucher-D8Gbuk.pdf Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964125/216592676/b99ba11fab7338f3c3c8c377a9d8e090b0828a3a Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Wait for load took 51ms Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Wait for js execution took 2ms Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Wait for animations took 100ms Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-D8Gbuk.pdf Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 21:57:58 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 21:58:23 ded101527.smartservers.com.au systemd[1244636]: Starting Mark boot as successful... -- Subject: Unit UNIT has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit UNIT has begun starting up. Sep 01 21:58:23 ded101527.smartservers.com.au systemd[1244636]: grub-boot-success.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit UNIT has successfully entered the 'dead' state. Sep 01 21:58:23 ded101527.smartservers.com.au systemd[1244636]: Started Mark boot as successful. -- Subject: Unit UNIT has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit UNIT has finished starting up. -- -- The start-up result is done. Sep 01 21:59:21 ded101527.smartservers.com.au sshd[1245836]: Connection closed by 127.0.0.1 port 32790 [preauth] Sep 01 21:59:47 ded101527.smartservers.com.au node[32625]: 2021-09-01T11:59:47.735Z INFO: Chrome shutdown on port 6921 Sep 01 22:00:41 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:00:41.872Z INFO: >> Generating EXOZ-voucher-QguWUJ.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964124/216592674/7becafb2854e66809d412b03c5788cb7f70ef9cd on port 6930 Sep 01 22:00:41 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:00:41.872Z INFO: << EXOZ-voucher-QguWUJ.pdf generated for https://transactional.ticketmates.net.au/voucher/4964124/216592674/7becafb2854e66809d412b03c5788cb7f70ef9cd on /tmp/EXOZ-voucher-QguWUJ.pdf Sep 01 22:00:41 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 22:00:41 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 22:00:41 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964124/216592674/7becafb2854e66809d412b03c5788cb7f70ef9cd Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: Wait for load took 121ms Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: Wait for js execution took 9ms Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: Wait for animations took 100ms Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-QguWUJ.pdf Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 22:00:42 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:00:49.203Z INFO: >> Generating EXOZ-voucher-oy7N7P.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964126/216592677/0e59747a297e8b3a723246b0f2e2ab2b5a9e387d on port 6931 Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:00:49.204Z INFO: << EXOZ-voucher-oy7N7P.pdf generated for https://transactional.ticketmates.net.au/voucher/4964126/216592677/0e59747a297e8b3a723246b0f2e2ab2b5a9e387d on /tmp/EXOZ-voucher-oy7N7P.pdf Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964126/216592677/0e59747a297e8b3a723246b0f2e2ab2b5a9e387d Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: Wait for load took 70ms Sep 01 22:00:49 ded101527.smartservers.com.au node[32625]: Wait for js execution took 0ms Sep 01 22:00:50 ded101527.smartservers.com.au node[32625]: Wait for animations took 99ms Sep 01 22:00:50 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-oy7N7P.pdf Sep 01 22:00:50 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 22:00:50 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 22:00:50 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 22:01:01 ded101527.smartservers.com.au CROND[1246088]: (root) CMD (run-parts /etc/cron.hourly) Sep 01 22:01:01 ded101527.smartservers.com.au run-parts[1246091]: (/etc/cron.hourly) starting 0anacron Sep 01 22:01:01 ded101527.smartservers.com.au run-parts[1246097]: (/etc/cron.hourly) finished 0anacron Sep 01 22:01:14 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:01:14.309Z INFO: Chrome shutdown on port 6922 Sep 01 22:01:52 ded101527.smartservers.com.au sshd[1246172]: Accepted publickey for root from 203.144.8.104 port 51154 ssh2: RSA SHA256:tcPKurz6SzFalCYR11/NbxxR9F8Ir4/yIjxaXvXmRbc Sep 01 22:01:52 ded101527.smartservers.com.au systemd-logind[1544]: New session 291 of user root. -- Subject: A new session 291 has been created for user root -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID 291 has been created for the user root. -- -- The leading process of the session is 1246172. Sep 01 22:01:52 ded101527.smartservers.com.au systemd[1]: Started Session 291 of user root. -- Subject: Unit session-291.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit session-291.scope has finished starting up. -- -- The start-up result is done. Sep 01 22:01:52 ded101527.smartservers.com.au sshd[1246172]: pam_unix(sshd:session): session opened for user root by (uid=0) Sep 01 22:02:00 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:00.719Z INFO: Chrome shutdown on port 6923 Sep 01 22:02:14 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:14.277Z INFO: >> Generating EXOZ-voucher-Q0xvBr.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964127/216592679/36def4aae77de7e12d54bf8bb09e130b5239045e on port 6932 Sep 01 22:02:14 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:14.277Z INFO: << EXOZ-voucher-Q0xvBr.pdf generated for https://transactional.ticketmates.net.au/voucher/4964127/216592679/36def4aae77de7e12d54bf8bb09e130b5239045e on /tmp/EXOZ-voucher-Q0xvBr.pdf Sep 01 22:02:14 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 22:02:14 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 22:02:14 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 22:02:14 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 22:02:14 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964127/216592679/36def4aae77de7e12d54bf8bb09e130b5239045e Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: Wait for load took 80ms Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: Wait for js execution took 3ms Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: Wait for animations took 100ms Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-Q0xvBr.pdf Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 22:02:15 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:15.341Z INFO: Chrome shutdown on port 6924 Sep 01 22:02:17 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:17.249Z INFO: Chrome shutdown on port 6925 Sep 01 22:02:17 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:17.563Z INFO: Chrome shutdown on port 6926 Sep 01 22:02:29 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:29.874Z INFO: Chrome shutdown on port 6927 Sep 01 22:02:31 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:31.302Z INFO: Chrome shutdown on port 6928 Sep 01 22:02:58 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:02:58.047Z INFO: Chrome shutdown on port 6929 Sep 01 22:03:11 ded101527.smartservers.com.au su[1244756]: pam_unix(su:session): session closed for user tmadmin Sep 01 22:03:13 ded101527.smartservers.com.au sshd[1244723]: Received disconnect from 203.144.7.121 port 57748:11: disconnected by user Sep 01 22:03:13 ded101527.smartservers.com.au sshd[1244723]: Disconnected from user jason 203.144.7.121 port 57748 Sep 01 22:03:13 ded101527.smartservers.com.au sshd[1244704]: pam_unix(sshd:session): session closed for user jason Sep 01 22:03:13 ded101527.smartservers.com.au systemd-logind[1544]: Session 290 logged out. Waiting for processes to exit. Sep 01 22:03:13 ded101527.smartservers.com.au systemd[1]: session-290.scope: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit session-290.scope has successfully entered the 'dead' state. Sep 01 22:03:13 ded101527.smartservers.com.au systemd-logind[1544]: Removed session 290. -- Subject: Session 290 has been terminated -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A session with the ID 290 has been terminated. Sep 01 22:03:26 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:03:26.821Z INFO: >> Generating EXOZ-voucher-P1Nfmg.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964120/216592669/bdd18bf6e2320bc0d30ee909e8b5d6ed9ea15cb9 on port 6933 Sep 01 22:03:26 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:03:26.822Z INFO: << EXOZ-voucher-P1Nfmg.pdf generated for https://transactional.ticketmates.net.au/voucher/4964120/216592669/bdd18bf6e2320bc0d30ee909e8b5d6ed9ea15cb9 on /tmp/EXOZ-voucher-P1Nfmg.pdf Sep 01 22:03:26 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 22:03:26 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 22:03:26 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 22:03:26 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964120/216592669/bdd18bf6e2320bc0d30ee909e8b5d6ed9ea15cb9 Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: Wait for load took 129ms Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: Wait for js execution took 4ms Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: Wait for animations took 100ms Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-P1Nfmg.pdf Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 22:03:27 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 22:03:32 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:03:32.306Z INFO: >> Generating EXOZ-voucher-cdyEXE.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964126/216592677/0e59747a297e8b3a723246b0f2e2ab2b5a9e387d on port 6934 Sep 01 22:03:32 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:03:32.307Z INFO: << EXOZ-voucher-cdyEXE.pdf generated for https://transactional.ticketmates.net.au/voucher/4964126/216592677/0e59747a297e8b3a723246b0f2e2ab2b5a9e387d on /tmp/EXOZ-voucher-cdyEXE.pdf Sep 01 22:03:32 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 22:03:32 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 22:03:32 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 22:03:32 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 22:03:32 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964126/216592677/0e59747a297e8b3a723246b0f2e2ab2b5a9e387d Sep 01 22:03:33 ded101527.smartservers.com.au node[32625]: Wait for load took 92ms Sep 01 22:03:33 ded101527.smartservers.com.au node[32625]: Wait for js execution took 0ms Sep 01 22:03:33 ded101527.smartservers.com.au node[32625]: Wait for animations took 100ms Sep 01 22:03:33 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-cdyEXE.pdf Sep 01 22:03:33 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 22:03:33 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 22:03:33 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 22:04:21 ded101527.smartservers.com.au sshd[1246564]: Connection closed by 127.0.0.1 port 46896 [preauth] Sep 01 22:04:31 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:04:31.951Z INFO: >> Generating EXOZ-voucher-yfmvqQ.pdf for URL: https://transactional.ticketmates.net.au/voucher/4964120/216592669/bdd18bf6e2320bc0d30ee909e8b5d6ed9ea15cb9 on port 6935 Sep 01 22:04:31 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:04:31.952Z INFO: << EXOZ-voucher-yfmvqQ.pdf generated for https://transactional.ticketmates.net.au/voucher/4964120/216592669/bdd18bf6e2320bc0d30ee909e8b5d6ed9ea15cb9 on /tmp/EXOZ-voucher-yfmvqQ.pdf Sep 01 22:04:31 ded101527.smartservers.com.au node[32625]: Using google-chrome Sep 01 22:04:31 ded101527.smartservers.com.au node[32625]: Waiting for chrome to became available Sep 01 22:04:32 ded101527.smartservers.com.au node[32625]: Chrome port open! Sep 01 22:04:32 ded101527.smartservers.com.au node[32625]: Connected to HeadlessChrome/93.0.4577.63, protocol 1.3 Sep 01 22:04:32 ded101527.smartservers.com.au node[32625]: Opening https://transactional.ticketmates.net.au/voucher/4964120/216592669/bdd18bf6e2320bc0d30ee909e8b5d6ed9ea15cb9 Sep 01 22:04:32 ded101527.smartservers.com.au node[32625]: Wait for load took 120ms Sep 01 22:04:32 ded101527.smartservers.com.au node[32625]: Wait for js execution took 6ms Sep 01 22:04:32 ded101527.smartservers.com.au node[32625]: Wait for animations took 100ms Sep 01 22:04:33 ded101527.smartservers.com.au node[32625]: Saved /tmp/EXOZ-voucher-yfmvqQ.pdf Sep 01 22:04:33 ded101527.smartservers.com.au node[32625]: Chrome stopped (null) Sep 01 22:04:33 ded101527.smartservers.com.au node[32625]: (chrome) (out) [object Object] Sep 01 22:04:33 ded101527.smartservers.com.au node[32625]: (chrome) (err) [object Object] Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping nginx - high performance web server... -- Subject: Unit nginx.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit nginx.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping PAPI Service - 5057... -- Subject: Unit papi.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit papi.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping AdMan Service - 5051... -- Subject: Unit adman.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit adman.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping ISAPI Service - 5054... -- Subject: Unit isapi.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit isapi.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping ITAPI Service - 5056... -- Subject: Unit itapi.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit itapi.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping TAPI Service - 5061... -- Subject: Unit tapi2.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tapi2.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping TAPI Load Balance Service - 5062... -- Subject: Unit tapi-lb.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tapi-lb.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping TAPI Service - 5055... -- Subject: Unit tapi.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tapi.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping ICAPI Service - 5053... -- Subject: Unit icapi.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit icapi.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping CAPI Service - 5052... -- Subject: Unit capi.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit capi.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping Dashboard Service - 5059... -- Subject: Unit tm-dashboard.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tm-dashboard.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopping TM Admin Service - 5058... -- Subject: Unit tm-admin.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tm-admin.service has begun shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: isapi.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit isapi.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped ISAPI Service - 5054. -- Subject: Unit isapi.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit isapi.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: capi.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit capi.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped CAPI Service - 5052. -- Subject: Unit capi.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit capi.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: icapi.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit icapi.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped ICAPI Service - 5053. -- Subject: Unit icapi.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit icapi.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: papi.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit papi.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped PAPI Service - 5057. -- Subject: Unit papi.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit papi.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: nginx.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit nginx.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped nginx - high performance web server. -- Subject: Unit nginx.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit nginx.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: adman.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit adman.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped AdMan Service - 5051. -- Subject: Unit adman.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit adman.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: itapi.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit itapi.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped ITAPI Service - 5056. -- Subject: Unit itapi.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit itapi.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: tapi2.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit tapi2.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped TAPI Service - 5061. -- Subject: Unit tapi2.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tapi2.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: tapi.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit tapi.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped TAPI Service - 5055. -- Subject: Unit tapi.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tapi.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: tm-admin.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit tm-admin.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped TM Admin Service - 5058. -- Subject: Unit tm-admin.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tm-admin.service has finished shutting down. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: tm-dashboard.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit tm-dashboard.service has successfully entered the 'dead' state. Sep 01 22:04:57 ded101527.smartservers.com.au systemd[1]: Stopped Dashboard Service - 5059. -- Subject: Unit tm-dashboard.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tm-dashboard.service has finished shutting down. Sep 01 22:05:04 ded101527.smartservers.com.au systemd[1]: tapi-lb.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit tapi-lb.service has successfully entered the 'dead' state. Sep 01 22:05:04 ded101527.smartservers.com.au systemd[1]: Stopped TAPI Load Balance Service - 5062. -- Subject: Unit tapi-lb.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit tapi-lb.service has finished shutting down. Sep 01 22:05:09 ded101527.smartservers.com.au sshd[1247070]: Accepted publickey for root from 203.144.8.104 port 51165 ssh2: RSA SHA256:tcPKurz6SzFalCYR11/NbxxR9F8Ir4/yIjxaXvXmRbc Sep 01 22:05:09 ded101527.smartservers.com.au systemd-logind[1544]: New session 292 of user root. -- Subject: A new session 292 has been created for user root -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID 292 has been created for the user root. -- -- The leading process of the session is 1247070. Sep 01 22:05:09 ded101527.smartservers.com.au systemd[1]: Started Session 292 of user root. -- Subject: Unit session-292.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit session-292.scope has finished starting up. -- -- The start-up result is done. Sep 01 22:05:09 ded101527.smartservers.com.au sshd[1247070]: pam_unix(sshd:session): session opened for user root by (uid=0) Sep 01 22:05:41 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:05:41.887Z INFO: Chrome shutdown on port 6930 Sep 01 22:05:49 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:05:49.211Z INFO: Chrome shutdown on port 6931 Sep 01 22:06:14 ded101527.smartservers.com.au sshd[1247088]: Accepted publickey for root from 203.144.8.104 port 51170 ssh2: RSA SHA256:tcPKurz6SzFalCYR11/NbxxR9F8Ir4/yIjxaXvXmRbc Sep 01 22:06:14 ded101527.smartservers.com.au systemd-logind[1544]: New session 293 of user root. -- Subject: A new session 293 has been created for user root -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID 293 has been created for the user root. -- -- The leading process of the session is 1247088. Sep 01 22:06:14 ded101527.smartservers.com.au systemd[1]: Started Session 293 of user root. -- Subject: Unit session-293.scope has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit session-293.scope has finished starting up. -- -- The start-up result is done. Sep 01 22:06:14 ded101527.smartservers.com.au sshd[1247088]: pam_unix(sshd:session): session opened for user root by (uid=0) Sep 01 22:06:20 ded101527.smartservers.com.au systemd[1]: Stopping MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun shutting down. Sep 01 22:06:20 ded101527.smartservers.com.au maxscale[32287]: Stopped MaxScale REST API Sep 01 22:06:20 ded101527.smartservers.com.au maxscale[32287]: MaxScale is shutting down. Sep 01 22:06:20 ded101527.smartservers.com.au maxscale[32287]: All workers have shut down. Sep 01 22:06:21 ded101527.smartservers.com.au maxscale[32287]: MaxScale shutdown completed. Sep 01 22:06:21 ded101527.smartservers.com.au maxscale[32287]: MaxScale received signal SIGTERM. Exiting. Sep 01 22:06:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has successfully entered the 'dead' state. Sep 01 22:06:21 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:06:23 ded101527.smartservers.com.au mariadbd[1910]: 2021-09-01 22:06:23 9 [Warning] Aborted connection 9 to db: 'unconnected' user: 'maxuser' host: '127.0.0.1' (Got an error writing communication packets) Sep 01 22:06:25 ded101527.smartservers.com.au sudo[1247121]: jason : TTY=pts/0 ; PWD=/home/jason ; USER=root ; COMMAND=/bin/systemctl start adman Sep 01 22:06:25 ded101527.smartservers.com.au sudo[1247121]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice Sep 01 22:06:25 ded101527.smartservers.com.au sudo[1247121]: pam_unix(sudo:session): session opened for user root by jason(uid=0) Sep 01 22:06:26 ded101527.smartservers.com.au systemd[1]: Started AdMan Service - 5051. -- Subject: Unit adman.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit adman.service has finished starting up. -- -- The start-up result is done. Sep 01 22:06:26 ded101527.smartservers.com.au sudo[1247121]: pam_unix(sudo:session): session closed for user root Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: Reloading. Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: Started Adcore file compress. -- Subject: Unit adcore.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit adcore.service has finished starting up. -- -- The start-up result is done. Sep 01 22:06:56 ded101527.smartservers.com.au gzip[1247259]: gzip: /misc/adcore/CAPIXMLExport.xml.gz already exists; not overwritten Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: adcore.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: adcore.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit adcore.service has entered the 'failed' state with result 'exit-code'. Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: Reloading. Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: Started Adcore file compress. -- Subject: Unit adcore.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit adcore.service has finished starting up. -- -- The start-up result is done. Sep 01 22:06:56 ded101527.smartservers.com.au gzip[1247282]: gzip: /misc/adcore/CAPIXMLExport.xml.gz already exists; not overwritten Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: adcore.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: adcore.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit adcore.service has entered the 'failed' state with result 'exit-code'. Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: Started /usr/bin/systemctl start man-db-cache-update. -- Subject: Unit run-rd3bed1c9dbee47b9834846734b11b5f9.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit run-rd3bed1c9dbee47b9834846734b11b5f9.service has finished starting up. -- -- The start-up result is done. Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: Starting man-db-cache-update.service... -- Subject: Unit man-db-cache-update.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit man-db-cache-update.service has begun starting up. Sep 01 22:06:56 ded101527.smartservers.com.au systemd[1]: Started /usr/bin/systemctl start man-db-cache-update. -- Subject: Unit run-r7a6734630ad942f3ac8bc41223f6b48c.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit run-r7a6734630ad942f3ac8bc41223f6b48c.service has finished starting up. -- -- The start-up result is done. Sep 01 22:06:57 ded101527.smartservers.com.au systemd[1]: man-db-cache-update.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit man-db-cache-update.service has successfully entered the 'dead' state. Sep 01 22:06:57 ded101527.smartservers.com.au systemd[1]: Started man-db-cache-update.service. -- Subject: Unit man-db-cache-update.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit man-db-cache-update.service has finished starting up. -- -- The start-up result is done. Sep 01 22:06:57 ded101527.smartservers.com.au systemd[1]: run-rd3bed1c9dbee47b9834846734b11b5f9.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-rd3bed1c9dbee47b9834846734b11b5f9.service has successfully entered the 'dead' state. Sep 01 22:06:57 ded101527.smartservers.com.au systemd[1]: run-r7a6734630ad942f3ac8bc41223f6b48c.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit run-r7a6734630ad942f3ac8bc41223f6b48c.service has successfully entered the 'dead' state. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:09 ded101527.smartservers.com.au kernel: traps: maxscale[1247747] trap invalid opcode ip:7f97b3f479d9 sp:7fffbe3b4920 error:0 in libmaxscale-common.so.1.0.0[7f97b3c6f000+37d000] Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247748/UID 0). -- Subject: Unit systemd-coredump@1968-1247748-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1968-1247748-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:09 ded101527.smartservers.com.au systemd-coredump[1247749]: Process 1247747 (maxscale) of user 977 dumped core. Stack trace of thread 1247747: #0 0x00007f97b3f479d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f97b3d5a5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f97b421d8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f97b421d9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f97b420efda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247747 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247747 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1968-1247748-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1968-1247748-0.service has successfully entered the 'dead' state. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:09 ded101527.smartservers.com.au kernel: traps: maxscale[1247761] trap invalid opcode ip:7fa1264689d9 sp:7ffdca7d40e0 error:0 in libmaxscale-common.so.1.0.0[7fa126190000+37d000] Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247762/UID 0). -- Subject: Unit systemd-coredump@1969-1247762-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1969-1247762-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:09 ded101527.smartservers.com.au systemd-coredump[1247763]: Process 1247761 (maxscale) of user 977 dumped core. Stack trace of thread 1247761: #0 0x00007fa1264689d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fa12627b5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fa12673e8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fa12673e9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fa12672ffda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247761 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247761 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:09 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1969-1247762-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1969-1247762-0.service has successfully entered the 'dead' state. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 2. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:10 ded101527.smartservers.com.au kernel: traps: maxscale[1247777] trap invalid opcode ip:7fb5ecb649d9 sp:7ffd3d857100 error:0 in libmaxscale-common.so.1.0.0[7fb5ec88c000+37d000] Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247778/UID 0). -- Subject: Unit systemd-coredump@1970-1247778-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1970-1247778-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:10 ded101527.smartservers.com.au systemd-coredump[1247779]: Process 1247777 (maxscale) of user 977 dumped core. Stack trace of thread 1247777: #0 0x00007fb5ecb649d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fb5ec9775e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fb5ece3a8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fb5ece3a9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fb5ece2bfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247777 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247777 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1970-1247778-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1970-1247778-0.service has successfully entered the 'dead' state. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 3. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:10 ded101527.smartservers.com.au kernel: traps: maxscale[1247791] trap invalid opcode ip:7fc037fd69d9 sp:7ffc191512a0 error:0 in libmaxscale-common.so.1.0.0[7fc037cfe000+37d000] Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247792/UID 0). -- Subject: Unit systemd-coredump@1971-1247792-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1971-1247792-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:10 ded101527.smartservers.com.au systemd-coredump[1247793]: Process 1247791 (maxscale) of user 977 dumped core. Stack trace of thread 1247791: #0 0x00007fc037fd69d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fc037de95e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fc0382ac8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fc0382ac9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fc03829dfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247791 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247791 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:10 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1971-1247792-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1971-1247792-0.service has successfully entered the 'dead' state. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 4. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:11 ded101527.smartservers.com.au kernel: traps: maxscale[1247804] trap invalid opcode ip:7f867af3a9d9 sp:7ffd95f6d080 error:0 in libmaxscale-common.so.1.0.0[7f867ac62000+37d000] Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247805/UID 0). -- Subject: Unit systemd-coredump@1972-1247805-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1972-1247805-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:11 ded101527.smartservers.com.au systemd-coredump[1247806]: Process 1247804 (maxscale) of user 977 dumped core. Stack trace of thread 1247804: #0 0x00007f867af3a9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f867ad4d5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f867b2108ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f867b2109ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f867b201fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247804 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247804 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1972-1247805-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1972-1247805-0.service has successfully entered the 'dead' state. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:11 ded101527.smartservers.com.au kernel: traps: maxscale[1247817] trap invalid opcode ip:7ff00fa119d9 sp:7fff95fe2f40 error:0 in libmaxscale-common.so.1.0.0[7ff00f739000+37d000] Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247818/UID 0). -- Subject: Unit systemd-coredump@1973-1247818-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1973-1247818-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:11 ded101527.smartservers.com.au systemd-coredump[1247819]: Process 1247817 (maxscale) of user 977 dumped core. Stack trace of thread 1247817: #0 0x00007ff00fa119d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007ff00f8245e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007ff00fce78ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007ff00fce79ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007ff00fcd8fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247817 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247817 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:11 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1973-1247818-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1973-1247818-0.service has successfully entered the 'dead' state. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 6. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:12 ded101527.smartservers.com.au kernel: traps: maxscale[1247832] trap invalid opcode ip:7f313484a9d9 sp:7ffc6dba6800 error:0 in libmaxscale-common.so.1.0.0[7f3134572000+37d000] Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247833/UID 0). -- Subject: Unit systemd-coredump@1974-1247833-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1974-1247833-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:12 ded101527.smartservers.com.au systemd-coredump[1247834]: Process 1247832 (maxscale) of user 977 dumped core. Stack trace of thread 1247832: #0 0x00007f313484a9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f313465d5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f3134b208ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f3134b209ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f3134b11fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247832 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247832 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1974-1247833-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1974-1247833-0.service has successfully entered the 'dead' state. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 7. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:12 ded101527.smartservers.com.au kernel: traps: maxscale[1247845] trap invalid opcode ip:7f6f166ec9d9 sp:7fff4c5fa680 error:0 in libmaxscale-common.so.1.0.0[7f6f16414000+37d000] Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247846/UID 0). -- Subject: Unit systemd-coredump@1975-1247846-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1975-1247846-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:12 ded101527.smartservers.com.au systemd-coredump[1247847]: Process 1247845 (maxscale) of user 977 dumped core. Stack trace of thread 1247845: #0 0x00007f6f166ec9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f6f164ff5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f6f169c28ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f6f169c29ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f6f169b3fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247845 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247845 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:12 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1975-1247846-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1975-1247846-0.service has successfully entered the 'dead' state. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 8. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:13 ded101527.smartservers.com.au kernel: traps: maxscale[1247858] trap invalid opcode ip:7f9ef42fc9d9 sp:7ffd748823c0 error:0 in libmaxscale-common.so.1.0.0[7f9ef4024000+37d000] Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247859/UID 0). -- Subject: Unit systemd-coredump@1976-1247859-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1976-1247859-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:13 ded101527.smartservers.com.au systemd-coredump[1247860]: Process 1247858 (maxscale) of user 977 dumped core. Stack trace of thread 1247858: #0 0x00007f9ef42fc9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f9ef410f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f9ef45d28ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f9ef45d29ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f9ef45c3fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247858 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247858 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1976-1247859-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1976-1247859-0.service has successfully entered the 'dead' state. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 9. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:13 ded101527.smartservers.com.au kernel: traps: maxscale[1247871] trap invalid opcode ip:7fb99f87b9d9 sp:7ffce0e035a0 error:0 in libmaxscale-common.so.1.0.0[7fb99f5a3000+37d000] Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247872/UID 0). -- Subject: Unit systemd-coredump@1977-1247872-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1977-1247872-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:13 ded101527.smartservers.com.au systemd-coredump[1247873]: Process 1247871 (maxscale) of user 977 dumped core. Stack trace of thread 1247871: #0 0x00007fb99f87b9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fb99f68e5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fb99fb518ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fb99fb519ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fb99fb42fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247871 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247871 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:13 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1977-1247872-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1977-1247872-0.service has successfully entered the 'dead' state. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 10. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247887/UID 0). -- Subject: Unit systemd-coredump@1978-1247887-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1978-1247887-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:14 ded101527.smartservers.com.au node[32625]: 2021-09-01T12:07:14.354Z INFO: Chrome shutdown on port 6932 Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:14 ded101527.smartservers.com.au systemd-coredump[1247888]: Process 1247886 (maxscale) of user 977 dumped core. Stack trace of thread 1247886: #0 0x00007eff96fb49d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007eff96dc75e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007eff9728a8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007eff9728a9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007eff9727bfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247886 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247886 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1978-1247887-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1978-1247887-0.service has successfully entered the 'dead' state. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 11. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:14 ded101527.smartservers.com.au kernel: show_signal: 1 callbacks suppressed Sep 01 22:07:14 ded101527.smartservers.com.au kernel: traps: maxscale[1247900] trap invalid opcode ip:7f051f4a79d9 sp:7ffcbda84360 error:0 in libmaxscale-common.so.1.0.0[7f051f1cf000+37d000] Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247901/UID 0). -- Subject: Unit systemd-coredump@1979-1247901-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1979-1247901-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:14 ded101527.smartservers.com.au systemd-coredump[1247902]: Process 1247900 (maxscale) of user 977 dumped core. Stack trace of thread 1247900: #0 0x00007f051f4a79d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f051f2ba5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f051f77d8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f051f77d9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f051f76efda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247900 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247900 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:14 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1979-1247901-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1979-1247901-0.service has successfully entered the 'dead' state. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 12. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:15 ded101527.smartservers.com.au kernel: traps: maxscale[1247914] trap invalid opcode ip:7fdcfec4c9d9 sp:7ffcdc04ab80 error:0 in libmaxscale-common.so.1.0.0[7fdcfe974000+37d000] Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247915/UID 0). -- Subject: Unit systemd-coredump@1980-1247915-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1980-1247915-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:15 ded101527.smartservers.com.au systemd-coredump[1247916]: Process 1247914 (maxscale) of user 977 dumped core. Stack trace of thread 1247914: #0 0x00007fdcfec4c9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fdcfea5f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fdcfef228ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fdcfef229ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fdcfef13fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247914 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247914 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1980-1247915-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1980-1247915-0.service has successfully entered the 'dead' state. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 13. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:15 ded101527.smartservers.com.au kernel: traps: maxscale[1247927] trap invalid opcode ip:7f3e0ebf99d9 sp:7ffcd36f05a0 error:0 in libmaxscale-common.so.1.0.0[7f3e0e921000+37d000] Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247928/UID 0). -- Subject: Unit systemd-coredump@1981-1247928-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1981-1247928-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:15 ded101527.smartservers.com.au systemd-coredump[1247929]: Process 1247927 (maxscale) of user 977 dumped core. Stack trace of thread 1247927: #0 0x00007f3e0ebf99d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f3e0ea0c5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f3e0eecf8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f3e0eecf9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f3e0eec0fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247927 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247927 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:15 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1981-1247928-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1981-1247928-0.service has successfully entered the 'dead' state. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 14. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:16 ded101527.smartservers.com.au kernel: traps: maxscale[1247940] trap invalid opcode ip:7f2d862269d9 sp:7ffebc958340 error:0 in libmaxscale-common.so.1.0.0[7f2d85f4e000+37d000] Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247941/UID 0). -- Subject: Unit systemd-coredump@1982-1247941-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1982-1247941-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:16 ded101527.smartservers.com.au systemd-coredump[1247942]: Process 1247940 (maxscale) of user 977 dumped core. Stack trace of thread 1247940: #0 0x00007f2d862269d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f2d860395e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f2d864fc8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f2d864fc9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f2d864edfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247940 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247940 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1982-1247941-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1982-1247941-0.service has successfully entered the 'dead' state. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 15. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:16 ded101527.smartservers.com.au kernel: traps: maxscale[1247953] trap invalid opcode ip:7f292b49e9d9 sp:7fff63371d80 error:0 in libmaxscale-common.so.1.0.0[7f292b1c6000+37d000] Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247954/UID 0). -- Subject: Unit systemd-coredump@1983-1247954-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1983-1247954-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:16 ded101527.smartservers.com.au systemd-coredump[1247955]: Process 1247953 (maxscale) of user 977 dumped core. Stack trace of thread 1247953: #0 0x00007f292b49e9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f292b2b15e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f292b7748ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f292b7749ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f292b765fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247953 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247953 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:16 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1983-1247954-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1983-1247954-0.service has successfully entered the 'dead' state. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 16. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:17 ded101527.smartservers.com.au kernel: traps: maxscale[1247966] trap invalid opcode ip:7f365b1bf9d9 sp:7ffc29e91ae0 error:0 in libmaxscale-common.so.1.0.0[7f365aee7000+37d000] Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247967/UID 0). -- Subject: Unit systemd-coredump@1984-1247967-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1984-1247967-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:17 ded101527.smartservers.com.au systemd-coredump[1247968]: Process 1247966 (maxscale) of user 977 dumped core. Stack trace of thread 1247966: #0 0x00007f365b1bf9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f365afd25e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f365b4958ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f365b4959ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f365b486fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247966 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247966 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1984-1247967-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1984-1247967-0.service has successfully entered the 'dead' state. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 17. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:17 ded101527.smartservers.com.au kernel: traps: maxscale[1247979] trap invalid opcode ip:7f151db219d9 sp:7ffc32f33880 error:0 in libmaxscale-common.so.1.0.0[7f151d849000+37d000] Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247980/UID 0). -- Subject: Unit systemd-coredump@1985-1247980-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1985-1247980-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:17 ded101527.smartservers.com.au systemd-coredump[1247981]: Process 1247979 (maxscale) of user 977 dumped core. Stack trace of thread 1247979: #0 0x00007f151db219d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f151d9345e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f151ddf78ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f151ddf79ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f151dde8fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247979 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247979 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1985-1247980-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1985-1247980-0.service has successfully entered the 'dead' state. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 18. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:18 ded101527.smartservers.com.au kernel: traps: maxscale[1247992] trap invalid opcode ip:7fd58293c9d9 sp:7fffc5106240 error:0 in libmaxscale-common.so.1.0.0[7fd582664000+37d000] Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1247993/UID 0). -- Subject: Unit systemd-coredump@1986-1247993-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1986-1247993-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:18 ded101527.smartservers.com.au systemd-coredump[1247994]: Process 1247992 (maxscale) of user 977 dumped core. Stack trace of thread 1247992: #0 0x00007fd58293c9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fd58274f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fd582c128ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fd582c129ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fd582c03fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1247992 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1247992 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1986-1247993-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1986-1247993-0.service has successfully entered the 'dead' state. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 19. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:18 ded101527.smartservers.com.au kernel: traps: maxscale[1248005] trap invalid opcode ip:7f5521a1a9d9 sp:7fffb5b49660 error:0 in libmaxscale-common.so.1.0.0[7f5521742000+37d000] Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248006/UID 0). -- Subject: Unit systemd-coredump@1987-1248006-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1987-1248006-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:18 ded101527.smartservers.com.au systemd-coredump[1248007]: Process 1248005 (maxscale) of user 977 dumped core. Stack trace of thread 1248005: #0 0x00007f5521a1a9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f552182d5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f5521cf08ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f5521cf09ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f5521ce1fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248005 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248005 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:18 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1987-1248006-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1987-1248006-0.service has successfully entered the 'dead' state. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 20. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:19 ded101527.smartservers.com.au kernel: traps: maxscale[1248019] trap invalid opcode ip:7f33030459d9 sp:7ffcf565dba0 error:0 in libmaxscale-common.so.1.0.0[7f3302d6d000+37d000] Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248020/UID 0). -- Subject: Unit systemd-coredump@1988-1248020-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1988-1248020-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:19 ded101527.smartservers.com.au systemd-coredump[1248021]: Process 1248019 (maxscale) of user 977 dumped core. Stack trace of thread 1248019: #0 0x00007f33030459d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f3302e585e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f330331b8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f330331b9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f330330cfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248019 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248019 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1988-1248020-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1988-1248020-0.service has successfully entered the 'dead' state. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 21. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248034/UID 0). -- Subject: Unit systemd-coredump@1989-1248034-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1989-1248034-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:19 ded101527.smartservers.com.au systemd-coredump[1248035]: Process 1248033 (maxscale) of user 977 dumped core. Stack trace of thread 1248033: #0 0x00007fabb5ea59d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fabb5cb85e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fabb617b8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fabb617b9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fabb616cfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248033 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248033 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:19 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1989-1248034-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1989-1248034-0.service has successfully entered the 'dead' state. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 22. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:20 ded101527.smartservers.com.au kernel: show_signal: 1 callbacks suppressed Sep 01 22:07:20 ded101527.smartservers.com.au kernel: traps: maxscale[1248046] trap invalid opcode ip:7fdfbe1c89d9 sp:7ffcc4d05940 error:0 in libmaxscale-common.so.1.0.0[7fdfbdef0000+37d000] Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248047/UID 0). -- Subject: Unit systemd-coredump@1990-1248047-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1990-1248047-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:20 ded101527.smartservers.com.au systemd-coredump[1248048]: Process 1248046 (maxscale) of user 977 dumped core. Stack trace of thread 1248046: #0 0x00007fdfbe1c89d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fdfbdfdb5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fdfbe49e8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fdfbe49e9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fdfbe48ffda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248046 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248046 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1990-1248047-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1990-1248047-0.service has successfully entered the 'dead' state. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 23. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:20 ded101527.smartservers.com.au kernel: traps: maxscale[1248059] trap invalid opcode ip:7f8f4f4239d9 sp:7ffca9d39b60 error:0 in libmaxscale-common.so.1.0.0[7f8f4f14b000+37d000] Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248060/UID 0). -- Subject: Unit systemd-coredump@1991-1248060-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1991-1248060-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:20 ded101527.smartservers.com.au systemd-coredump[1248061]: Process 1248059 (maxscale) of user 977 dumped core. Stack trace of thread 1248059: #0 0x00007f8f4f4239d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f8f4f2365e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f8f4f6f98ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f8f4f6f99ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f8f4f6eafda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248059 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248059 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:20 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1991-1248060-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1991-1248060-0.service has successfully entered the 'dead' state. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 24. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:21 ded101527.smartservers.com.au kernel: traps: maxscale[1248072] trap invalid opcode ip:7f00ae5329d9 sp:7ffebeef8d00 error:0 in libmaxscale-common.so.1.0.0[7f00ae25a000+37d000] Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248073/UID 0). -- Subject: Unit systemd-coredump@1992-1248073-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1992-1248073-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:21 ded101527.smartservers.com.au systemd-coredump[1248074]: Process 1248072 (maxscale) of user 977 dumped core. Stack trace of thread 1248072: #0 0x00007f00ae5329d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f00ae3455e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f00ae8088ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f00ae8089ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f00ae7f9fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248072 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248072 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1992-1248073-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1992-1248073-0.service has successfully entered the 'dead' state. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 25. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:21 ded101527.smartservers.com.au kernel: traps: maxscale[1248085] trap invalid opcode ip:7fa50c5c09d9 sp:7ffebb0f23c0 error:0 in libmaxscale-common.so.1.0.0[7fa50c2e8000+37d000] Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248086/UID 0). -- Subject: Unit systemd-coredump@1993-1248086-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1993-1248086-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:21 ded101527.smartservers.com.au systemd-coredump[1248087]: Process 1248085 (maxscale) of user 977 dumped core. Stack trace of thread 1248085: #0 0x00007fa50c5c09d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fa50c3d35e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fa50c8968ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fa50c8969ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fa50c887fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248085 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248085 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:21 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1993-1248086-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1993-1248086-0.service has successfully entered the 'dead' state. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 26. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:22 ded101527.smartservers.com.au kernel: traps: maxscale[1248100] trap invalid opcode ip:7f7c5d4e09d9 sp:7ffee5ecfaa0 error:0 in libmaxscale-common.so.1.0.0[7f7c5d208000+37d000] Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248101/UID 0). -- Subject: Unit systemd-coredump@1994-1248101-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1994-1248101-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:22 ded101527.smartservers.com.au systemd-coredump[1248102]: Process 1248100 (maxscale) of user 977 dumped core. Stack trace of thread 1248100: #0 0x00007f7c5d4e09d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f7c5d2f35e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f7c5d7b68ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f7c5d7b69ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f7c5d7a7fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248100 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248100 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1994-1248101-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1994-1248101-0.service has successfully entered the 'dead' state. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 27. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:22 ded101527.smartservers.com.au kernel: traps: maxscale[1248113] trap invalid opcode ip:7fc3f50479d9 sp:7ffc71b09560 error:0 in libmaxscale-common.so.1.0.0[7fc3f4d6f000+37d000] Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248114/UID 0). -- Subject: Unit systemd-coredump@1995-1248114-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1995-1248114-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:22 ded101527.smartservers.com.au systemd-coredump[1248115]: Process 1248113 (maxscale) of user 977 dumped core. Stack trace of thread 1248113: #0 0x00007fc3f50479d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fc3f4e5a5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fc3f531d8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fc3f531d9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fc3f530efda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248113 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248113 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:22 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1995-1248114-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1995-1248114-0.service has successfully entered the 'dead' state. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 28. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:23 ded101527.smartservers.com.au kernel: traps: maxscale[1248126] trap invalid opcode ip:7fbaf4dff9d9 sp:7fffa9e31460 error:0 in libmaxscale-common.so.1.0.0[7fbaf4b27000+37d000] Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248127/UID 0). -- Subject: Unit systemd-coredump@1996-1248127-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1996-1248127-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:23 ded101527.smartservers.com.au systemd-coredump[1248128]: Process 1248126 (maxscale) of user 977 dumped core. Stack trace of thread 1248126: #0 0x00007fbaf4dff9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fbaf4c125e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fbaf50d58ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fbaf50d59ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fbaf50c6fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248126 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248126 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1996-1248127-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1996-1248127-0.service has successfully entered the 'dead' state. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 29. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:23 ded101527.smartservers.com.au kernel: traps: maxscale[1248140] trap invalid opcode ip:7f8f156b49d9 sp:7fff84c2d2a0 error:0 in libmaxscale-common.so.1.0.0[7f8f153dc000+37d000] Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248141/UID 0). -- Subject: Unit systemd-coredump@1997-1248141-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1997-1248141-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:23 ded101527.smartservers.com.au systemd-coredump[1248142]: Process 1248140 (maxscale) of user 977 dumped core. Stack trace of thread 1248140: #0 0x00007f8f156b49d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f8f154c75e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f8f1598a8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f8f1598a9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f8f1597bfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248140 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248140 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:23 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1997-1248141-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1997-1248141-0.service has successfully entered the 'dead' state. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 30. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:24 ded101527.smartservers.com.au kernel: traps: maxscale[1248153] trap invalid opcode ip:7f0e4ca8f9d9 sp:7ffc8e0f6ee0 error:0 in libmaxscale-common.so.1.0.0[7f0e4c7b7000+37d000] Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248154/UID 0). -- Subject: Unit systemd-coredump@1998-1248154-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1998-1248154-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:24 ded101527.smartservers.com.au systemd-coredump[1248155]: Process 1248153 (maxscale) of user 977 dumped core. Stack trace of thread 1248153: #0 0x00007f0e4ca8f9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f0e4c8a25e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f0e4cd658ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f0e4cd659ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f0e4cd56fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248153 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248153 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1998-1248154-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1998-1248154-0.service has successfully entered the 'dead' state. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 31. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:24 ded101527.smartservers.com.au kernel: traps: maxscale[1248166] trap invalid opcode ip:7f916f87c9d9 sp:7ffe6f8728e0 error:0 in libmaxscale-common.so.1.0.0[7f916f5a4000+37d000] Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248167/UID 0). -- Subject: Unit systemd-coredump@1999-1248167-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@1999-1248167-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:24 ded101527.smartservers.com.au systemd-coredump[1248168]: Process 1248166 (maxscale) of user 977 dumped core. Stack trace of thread 1248166: #0 0x00007f916f87c9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f916f68f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f916fb528ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f916fb529ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f916fb43fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248166 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248166 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:24 ded101527.smartservers.com.au systemd[1]: systemd-coredump@1999-1248167-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@1999-1248167-0.service has successfully entered the 'dead' state. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 32. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248180/UID 0). -- Subject: Unit systemd-coredump@2000-1248180-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2000-1248180-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:25 ded101527.smartservers.com.au systemd-coredump[1248181]: Process 1248179 (maxscale) of user 977 dumped core. Stack trace of thread 1248179: #0 0x00007fc7ecde39d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fc7ecbf65e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fc7ed0b98ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fc7ed0b99ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fc7ed0aafda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248179 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248179 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2000-1248180-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2000-1248180-0.service has successfully entered the 'dead' state. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 33. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:25 ded101527.smartservers.com.au kernel: show_signal: 1 callbacks suppressed Sep 01 22:07:25 ded101527.smartservers.com.au kernel: traps: maxscale[1248192] trap invalid opcode ip:7f52621809d9 sp:7ffd5b352d40 error:0 in libmaxscale-common.so.1.0.0[7f5261ea8000+37d000] Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248193/UID 0). -- Subject: Unit systemd-coredump@2001-1248193-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2001-1248193-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:25 ded101527.smartservers.com.au systemd-coredump[1248194]: Process 1248192 (maxscale) of user 977 dumped core. Stack trace of thread 1248192: #0 0x00007f52621809d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f5261f935e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f52624568ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f52624569ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f5262447fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248192 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248192 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:25 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2001-1248193-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2001-1248193-0.service has successfully entered the 'dead' state. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 34. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:26 ded101527.smartservers.com.au kernel: traps: maxscale[1248205] trap invalid opcode ip:7f6e730329d9 sp:7ffcc2b28340 error:0 in libmaxscale-common.so.1.0.0[7f6e72d5a000+37d000] Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248207/UID 0). -- Subject: Unit systemd-coredump@2002-1248207-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2002-1248207-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:26 ded101527.smartservers.com.au systemd-coredump[1248208]: Process 1248205 (maxscale) of user 977 dumped core. Stack trace of thread 1248205: #0 0x00007f6e730329d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f6e72e455e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f6e733088ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f6e733089ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f6e732f9fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248205 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248205 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2002-1248207-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2002-1248207-0.service has successfully entered the 'dead' state. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 35. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:26 ded101527.smartservers.com.au kernel: traps: maxscale[1248219] trap invalid opcode ip:7f76a755c9d9 sp:7fff85680020 error:0 in libmaxscale-common.so.1.0.0[7f76a7284000+37d000] Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248220/UID 0). -- Subject: Unit systemd-coredump@2003-1248220-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2003-1248220-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:26 ded101527.smartservers.com.au systemd-coredump[1248221]: Process 1248219 (maxscale) of user 977 dumped core. Stack trace of thread 1248219: #0 0x00007f76a755c9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f76a736f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f76a78328ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f76a78329ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f76a7823fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248219 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248219 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:26 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2003-1248220-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2003-1248220-0.service has successfully entered the 'dead' state. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 36. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:27 ded101527.smartservers.com.au kernel: traps: maxscale[1248233] trap invalid opcode ip:7f5d95b489d9 sp:7ffdbc8ff780 error:0 in libmaxscale-common.so.1.0.0[7f5d95870000+37d000] Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248234/UID 0). -- Subject: Unit systemd-coredump@2004-1248234-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2004-1248234-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:27 ded101527.smartservers.com.au systemd-coredump[1248235]: Process 1248233 (maxscale) of user 977 dumped core. Stack trace of thread 1248233: #0 0x00007f5d95b489d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f5d9595b5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f5d95e1e8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f5d95e1e9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f5d95e0ffda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248233 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248233 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2004-1248234-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2004-1248234-0.service has successfully entered the 'dead' state. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 37. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:27 ded101527.smartservers.com.au kernel: traps: maxscale[1248247] trap invalid opcode ip:7f6995b689d9 sp:7ffc9dd8c4c0 error:0 in libmaxscale-common.so.1.0.0[7f6995890000+37d000] Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248248/UID 0). -- Subject: Unit systemd-coredump@2005-1248248-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2005-1248248-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:27 ded101527.smartservers.com.au systemd-coredump[1248249]: Process 1248247 (maxscale) of user 977 dumped core. Stack trace of thread 1248247: #0 0x00007f6995b689d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f699597b5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f6995e3e8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f6995e3e9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f6995e2ffda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248247 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248247 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:27 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2005-1248248-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2005-1248248-0.service has successfully entered the 'dead' state. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 38. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:28 ded101527.smartservers.com.au kernel: traps: maxscale[1248261] trap invalid opcode ip:7f121d25e9d9 sp:7ffc1c0b06e0 error:0 in libmaxscale-common.so.1.0.0[7f121cf86000+37d000] Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248262/UID 0). -- Subject: Unit systemd-coredump@2006-1248262-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2006-1248262-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:28 ded101527.smartservers.com.au systemd-coredump[1248263]: Process 1248261 (maxscale) of user 977 dumped core. Stack trace of thread 1248261: #0 0x00007f121d25e9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f121d0715e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f121d5348ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f121d5349ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f121d525fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248261 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248261 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2006-1248262-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2006-1248262-0.service has successfully entered the 'dead' state. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 39. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:28 ded101527.smartservers.com.au kernel: traps: maxscale[1248275] trap invalid opcode ip:7fa93761b9d9 sp:7fff1fada620 error:0 in libmaxscale-common.so.1.0.0[7fa937343000+37d000] Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248276/UID 0). -- Subject: Unit systemd-coredump@2007-1248276-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2007-1248276-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:28 ded101527.smartservers.com.au systemd-coredump[1248277]: Process 1248275 (maxscale) of user 977 dumped core. Stack trace of thread 1248275: #0 0x00007fa93761b9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fa93742e5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fa9378f18ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fa9378f19ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fa9378e2fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248275 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248275 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:28 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2007-1248276-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2007-1248276-0.service has successfully entered the 'dead' state. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 40. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:29 ded101527.smartservers.com.au kernel: traps: maxscale[1248288] trap invalid opcode ip:7fa92687b9d9 sp:7fff656a7e60 error:0 in libmaxscale-common.so.1.0.0[7fa9265a3000+37d000] Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248289/UID 0). -- Subject: Unit systemd-coredump@2008-1248289-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2008-1248289-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:29 ded101527.smartservers.com.au systemd-coredump[1248290]: Process 1248288 (maxscale) of user 977 dumped core. Stack trace of thread 1248288: #0 0x00007fa92687b9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fa92668e5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fa926b518ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fa926b519ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fa926b42fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248288 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248288 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2008-1248289-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2008-1248289-0.service has successfully entered the 'dead' state. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 41. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:29 ded101527.smartservers.com.au kernel: traps: maxscale[1248301] trap invalid opcode ip:7f8e77cc49d9 sp:7ffe84b03b20 error:0 in libmaxscale-common.so.1.0.0[7f8e779ec000+37d000] Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248302/UID 0). -- Subject: Unit systemd-coredump@2009-1248302-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2009-1248302-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:29 ded101527.smartservers.com.au systemd-coredump[1248303]: Process 1248301 (maxscale) of user 977 dumped core. Stack trace of thread 1248301: #0 0x00007f8e77cc49d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f8e77ad75e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f8e77f9a8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f8e77f9a9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f8e77f8bfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248301 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248301 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:29 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2009-1248302-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2009-1248302-0.service has successfully entered the 'dead' state. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 42. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:30 ded101527.smartservers.com.au kernel: traps: maxscale[1248314] trap invalid opcode ip:7fcff592f9d9 sp:7fffb3c69620 error:0 in libmaxscale-common.so.1.0.0[7fcff5657000+37d000] Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248315/UID 0). -- Subject: Unit systemd-coredump@2010-1248315-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2010-1248315-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:30 ded101527.smartservers.com.au systemd-coredump[1248316]: Process 1248314 (maxscale) of user 977 dumped core. Stack trace of thread 1248314: #0 0x00007fcff592f9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fcff57425e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fcff5c058ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fcff5c059ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fcff5bf6fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248314 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248314 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2010-1248315-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2010-1248315-0.service has successfully entered the 'dead' state. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 43. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:30 ded101527.smartservers.com.au kernel: traps: maxscale[1248328] trap invalid opcode ip:7f71eeb749d9 sp:7ffc58e617a0 error:0 in libmaxscale-common.so.1.0.0[7f71ee89c000+37d000] Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248329/UID 0). -- Subject: Unit systemd-coredump@2011-1248329-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2011-1248329-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:30 ded101527.smartservers.com.au systemd-coredump[1248330]: Process 1248328 (maxscale) of user 977 dumped core. Stack trace of thread 1248328: #0 0x00007f71eeb749d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f71ee9875e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f71eee4a8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f71eee4a9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f71eee3bfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248328 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248328 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:30 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2011-1248329-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2011-1248329-0.service has successfully entered the 'dead' state. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 44. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:31 ded101527.smartservers.com.au kernel: traps: maxscale[1248341] trap invalid opcode ip:7f217482f9d9 sp:7ffec13f2e40 error:0 in libmaxscale-common.so.1.0.0[7f2174557000+37d000] Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248342/UID 0). -- Subject: Unit systemd-coredump@2012-1248342-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2012-1248342-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:31 ded101527.smartservers.com.au systemd-coredump[1248343]: Process 1248341 (maxscale) of user 977 dumped core. Stack trace of thread 1248341: #0 0x00007f217482f9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f21746425e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f2174b058ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f2174b059ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f2174af6fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248341 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248341 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2012-1248342-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2012-1248342-0.service has successfully entered the 'dead' state. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 45. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:31 ded101527.smartservers.com.au kernel: traps: maxscale[1248354] trap invalid opcode ip:7fd50b5b69d9 sp:7ffd46b4e420 error:0 in libmaxscale-common.so.1.0.0[7fd50b2de000+37d000] Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248355/UID 0). -- Subject: Unit systemd-coredump@2013-1248355-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2013-1248355-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:31 ded101527.smartservers.com.au systemd-coredump[1248356]: Process 1248354 (maxscale) of user 977 dumped core. Stack trace of thread 1248354: #0 0x00007fd50b5b69d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fd50b3c95e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fd50b88c8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fd50b88c9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fd50b87dfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248354 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248354 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:31 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2013-1248355-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2013-1248355-0.service has successfully entered the 'dead' state. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 46. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:32 ded101527.smartservers.com.au kernel: traps: maxscale[1248368] trap invalid opcode ip:7f541efb89d9 sp:7ffe85157520 error:0 in libmaxscale-common.so.1.0.0[7f541ece0000+37d000] Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248369/UID 0). -- Subject: Unit systemd-coredump@2014-1248369-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2014-1248369-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:32 ded101527.smartservers.com.au systemd-coredump[1248370]: Process 1248368 (maxscale) of user 977 dumped core. Stack trace of thread 1248368: #0 0x00007f541efb89d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f541edcb5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f541f28e8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f541f28e9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f541f27ffda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248368 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248368 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2014-1248369-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2014-1248369-0.service has successfully entered the 'dead' state. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 47. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:32 ded101527.smartservers.com.au kernel: traps: maxscale[1248381] trap invalid opcode ip:7fbeb08b69d9 sp:7ffda00d58c0 error:0 in libmaxscale-common.so.1.0.0[7fbeb05de000+37d000] Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248382/UID 0). -- Subject: Unit systemd-coredump@2015-1248382-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2015-1248382-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:32 ded101527.smartservers.com.au systemd-coredump[1248383]: Process 1248381 (maxscale) of user 977 dumped core. Stack trace of thread 1248381: #0 0x00007fbeb08b69d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fbeb06c95e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fbeb0b8c8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fbeb0b8c9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fbeb0b7dfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248381 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248381 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:32 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2015-1248382-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2015-1248382-0.service has successfully entered the 'dead' state. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 48. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:33 ded101527.smartservers.com.au kernel: traps: maxscale[1248394] trap invalid opcode ip:7f658edaa9d9 sp:7ffe8acaef60 error:0 in libmaxscale-common.so.1.0.0[7f658ead2000+37d000] Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248395/UID 0). -- Subject: Unit systemd-coredump@2016-1248395-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2016-1248395-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:33 ded101527.smartservers.com.au systemd-coredump[1248396]: Process 1248394 (maxscale) of user 977 dumped core. Stack trace of thread 1248394: #0 0x00007f658edaa9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f658ebbd5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f658f0808ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f658f0809ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f658f071fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248394 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248394 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2016-1248395-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2016-1248395-0.service has successfully entered the 'dead' state. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 49. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:33 ded101527.smartservers.com.au kernel: traps: maxscale[1248407] trap invalid opcode ip:7fbcefcb79d9 sp:7ffc2b80b1e0 error:0 in libmaxscale-common.so.1.0.0[7fbcef9df000+37d000] Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248408/UID 0). -- Subject: Unit systemd-coredump@2017-1248408-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2017-1248408-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:33 ded101527.smartservers.com.au systemd-coredump[1248409]: Process 1248407 (maxscale) of user 977 dumped core. Stack trace of thread 1248407: #0 0x00007fbcefcb79d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fbcefaca5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fbceff8d8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fbceff8d9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fbceff7efda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248407 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248407 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:33 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2017-1248408-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2017-1248408-0.service has successfully entered the 'dead' state. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 50. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:34 ded101527.smartservers.com.au kernel: traps: maxscale[1248420] trap invalid opcode ip:7fbd3dfdb9d9 sp:7ffc40746c80 error:0 in libmaxscale-common.so.1.0.0[7fbd3dd03000+37d000] Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248421/UID 0). -- Subject: Unit systemd-coredump@2018-1248421-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2018-1248421-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:34 ded101527.smartservers.com.au systemd-coredump[1248422]: Process 1248420 (maxscale) of user 977 dumped core. Stack trace of thread 1248420: #0 0x00007fbd3dfdb9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fbd3ddee5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fbd3e2b18ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fbd3e2b19ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fbd3e2a2fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248420 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248420 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2018-1248421-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2018-1248421-0.service has successfully entered the 'dead' state. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 51. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:34 ded101527.smartservers.com.au kernel: traps: maxscale[1248433] trap invalid opcode ip:7fce5e86c9d9 sp:7ffe0569c840 error:0 in libmaxscale-common.so.1.0.0[7fce5e594000+37d000] Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248434/UID 0). -- Subject: Unit systemd-coredump@2019-1248434-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2019-1248434-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:34 ded101527.smartservers.com.au systemd-coredump[1248435]: Process 1248433 (maxscale) of user 977 dumped core. Stack trace of thread 1248433: #0 0x00007fce5e86c9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fce5e67f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fce5eb428ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fce5eb429ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fce5eb33fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248433 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248433 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:34 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2019-1248434-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2019-1248434-0.service has successfully entered the 'dead' state. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 52. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:35 ded101527.smartservers.com.au kernel: traps: maxscale[1248447] trap invalid opcode ip:7f31a34ac9d9 sp:7ffe64c23a20 error:0 in libmaxscale-common.so.1.0.0[7f31a31d4000+37d000] Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248448/UID 0). -- Subject: Unit systemd-coredump@2020-1248448-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2020-1248448-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:35 ded101527.smartservers.com.au systemd-coredump[1248449]: Process 1248447 (maxscale) of user 977 dumped core. Stack trace of thread 1248447: #0 0x00007f31a34ac9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f31a32bf5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f31a37828ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f31a37829ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f31a3773fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248447 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248447 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2020-1248448-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2020-1248448-0.service has successfully entered the 'dead' state. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 53. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248461/UID 0). -- Subject: Unit systemd-coredump@2021-1248461-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2021-1248461-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:35 ded101527.smartservers.com.au systemd-coredump[1248462]: Process 1248460 (maxscale) of user 977 dumped core. Stack trace of thread 1248460: #0 0x00007f14d711b9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f14d6f2e5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f14d73f18ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f14d73f19ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f14d73e2fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248460 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248460 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:35 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2021-1248461-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2021-1248461-0.service has successfully entered the 'dead' state. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 54. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:36 ded101527.smartservers.com.au kernel: show_signal: 1 callbacks suppressed Sep 01 22:07:36 ded101527.smartservers.com.au kernel: traps: maxscale[1248473] trap invalid opcode ip:7ff787fd39d9 sp:7ffd015eb900 error:0 in libmaxscale-common.so.1.0.0[7ff787cfb000+37d000] Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248474/UID 0). -- Subject: Unit systemd-coredump@2022-1248474-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2022-1248474-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:36 ded101527.smartservers.com.au systemd-coredump[1248475]: Process 1248473 (maxscale) of user 977 dumped core. Stack trace of thread 1248473: #0 0x00007ff787fd39d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007ff787de65e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007ff7882a98ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007ff7882a99ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007ff78829afda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248473 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248473 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2022-1248474-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2022-1248474-0.service has successfully entered the 'dead' state. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 55. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:36 ded101527.smartservers.com.au kernel: traps: maxscale[1248486] trap invalid opcode ip:7f440551b9d9 sp:7fff12e65a20 error:0 in libmaxscale-common.so.1.0.0[7f4405243000+37d000] Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248487/UID 0). -- Subject: Unit systemd-coredump@2023-1248487-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2023-1248487-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:36 ded101527.smartservers.com.au systemd-coredump[1248488]: Process 1248486 (maxscale) of user 977 dumped core. Stack trace of thread 1248486: #0 0x00007f440551b9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f440532e5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f44057f18ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f44057f19ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f44057e2fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248486 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248486 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:36 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2023-1248487-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2023-1248487-0.service has successfully entered the 'dead' state. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 56. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:37 ded101527.smartservers.com.au kernel: traps: maxscale[1248499] trap invalid opcode ip:7fed530eb9d9 sp:7ffe2fbdd6a0 error:0 in libmaxscale-common.so.1.0.0[7fed52e13000+37d000] Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248500/UID 0). -- Subject: Unit systemd-coredump@2024-1248500-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2024-1248500-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:37 ded101527.smartservers.com.au systemd-coredump[1248501]: Process 1248499 (maxscale) of user 977 dumped core. Stack trace of thread 1248499: #0 0x00007fed530eb9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fed52efe5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fed533c18ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fed533c19ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fed533b2fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248499 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248499 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2024-1248500-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2024-1248500-0.service has successfully entered the 'dead' state. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 57. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:37 ded101527.smartservers.com.au kernel: traps: maxscale[1248512] trap invalid opcode ip:7f11ee6e29d9 sp:7ffd38ddfe40 error:0 in libmaxscale-common.so.1.0.0[7f11ee40a000+37d000] Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248513/UID 0). -- Subject: Unit systemd-coredump@2025-1248513-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2025-1248513-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:37 ded101527.smartservers.com.au systemd-coredump[1248514]: Process 1248512 (maxscale) of user 977 dumped core. Stack trace of thread 1248512: #0 0x00007f11ee6e29d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f11ee4f55e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f11ee9b88ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f11ee9b89ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f11ee9a9fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248512 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248512 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:37 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2025-1248513-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2025-1248513-0.service has successfully entered the 'dead' state. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 58. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:38 ded101527.smartservers.com.au kernel: traps: maxscale[1248525] trap invalid opcode ip:7fba141c59d9 sp:7fffbd2d7600 error:0 in libmaxscale-common.so.1.0.0[7fba13eed000+37d000] Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248526/UID 0). -- Subject: Unit systemd-coredump@2026-1248526-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2026-1248526-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:38 ded101527.smartservers.com.au systemd-coredump[1248527]: Process 1248525 (maxscale) of user 977 dumped core. Stack trace of thread 1248525: #0 0x00007fba141c59d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fba13fd85e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fba1449b8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fba1449b9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fba1448cfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248525 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248525 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2026-1248526-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2026-1248526-0.service has successfully entered the 'dead' state. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 59. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:38 ded101527.smartservers.com.au kernel: traps: maxscale[1248538] trap invalid opcode ip:7fe32db429d9 sp:7ffebf531a00 error:0 in libmaxscale-common.so.1.0.0[7fe32d86a000+37d000] Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248539/UID 0). -- Subject: Unit systemd-coredump@2027-1248539-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2027-1248539-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:38 ded101527.smartservers.com.au systemd-coredump[1248540]: Process 1248538 (maxscale) of user 977 dumped core. Stack trace of thread 1248538: #0 0x00007fe32db429d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fe32d9555e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fe32de188ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fe32de189ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fe32de09fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248538 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248538 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:38 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2027-1248539-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2027-1248539-0.service has successfully entered the 'dead' state. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 60. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:39 ded101527.smartservers.com.au kernel: traps: maxscale[1248551] trap invalid opcode ip:7fbefccc59d9 sp:7ffd715322a0 error:0 in libmaxscale-common.so.1.0.0[7fbefc9ed000+37d000] Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248552/UID 0). -- Subject: Unit systemd-coredump@2028-1248552-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2028-1248552-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:39 ded101527.smartservers.com.au systemd-coredump[1248553]: Process 1248551 (maxscale) of user 977 dumped core. Stack trace of thread 1248551: #0 0x00007fbefccc59d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007fbefcad85e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007fbefcf9b8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007fbefcf9b9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007fbefcf8cfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248551 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248551 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2028-1248552-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2028-1248552-0.service has successfully entered the 'dead' state. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 61. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:39 ded101527.smartservers.com.au kernel: traps: maxscale[1248564] trap invalid opcode ip:7f2cc43ac9d9 sp:7ffed6d87500 error:0 in libmaxscale-common.so.1.0.0[7f2cc40d4000+37d000] Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248565/UID 0). -- Subject: Unit systemd-coredump@2029-1248565-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2029-1248565-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:39 ded101527.smartservers.com.au systemd-coredump[1248566]: Process 1248564 (maxscale) of user 977 dumped core. Stack trace of thread 1248564: #0 0x00007f2cc43ac9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f2cc41bf5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f2cc46828ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f2cc46829ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f2cc4673fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248564 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248564 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:39 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2029-1248565-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2029-1248565-0.service has successfully entered the 'dead' state. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 62. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:40 ded101527.smartservers.com.au kernel: traps: maxscale[1248577] trap invalid opcode ip:7f25659f19d9 sp:7fffaeae46e0 error:0 in libmaxscale-common.so.1.0.0[7f2565719000+37d000] Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248578/UID 0). -- Subject: Unit systemd-coredump@2030-1248578-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2030-1248578-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:40 ded101527.smartservers.com.au systemd-coredump[1248579]: Process 1248577 (maxscale) of user 977 dumped core. Stack trace of thread 1248577: #0 0x00007f25659f19d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f25658045e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f2565cc78ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f2565cc79ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f2565cb8fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248577 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248577 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2030-1248578-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2030-1248578-0.service has successfully entered the 'dead' state. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 63. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:40 ded101527.smartservers.com.au kernel: traps: maxscale[1248590] trap invalid opcode ip:7f921aa1c9d9 sp:7fff90ca86e0 error:0 in libmaxscale-common.so.1.0.0[7f921a744000+37d000] Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248591/UID 0). -- Subject: Unit systemd-coredump@2031-1248591-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2031-1248591-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:40 ded101527.smartservers.com.au systemd-coredump[1248592]: Process 1248590 (maxscale) of user 977 dumped core. Stack trace of thread 1248590: #0 0x00007f921aa1c9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f921a82f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f921acf28ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f921acf29ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f921ace3fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248590 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248590 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:40 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2031-1248591-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2031-1248591-0.service has successfully entered the 'dead' state. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 64. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248604/UID 0). -- Subject: Unit systemd-coredump@2032-1248604-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2032-1248604-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:41 ded101527.smartservers.com.au systemd-coredump[1248605]: Process 1248603 (maxscale) of user 977 dumped core. Stack trace of thread 1248603: #0 0x00007f22038469d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f22036595e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f2203b1c8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f2203b1c9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f2203b0dfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248603 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248603 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2032-1248604-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2032-1248604-0.service has successfully entered the 'dead' state. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 65. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:41 ded101527.smartservers.com.au kernel: show_signal: 1 callbacks suppressed Sep 01 22:07:41 ded101527.smartservers.com.au kernel: traps: maxscale[1248617] trap invalid opcode ip:7f7849cf49d9 sp:7ffed9c81b00 error:0 in libmaxscale-common.so.1.0.0[7f7849a1c000+37d000] Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248618/UID 0). -- Subject: Unit systemd-coredump@2033-1248618-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2033-1248618-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:41 ded101527.smartservers.com.au systemd-coredump[1248619]: Process 1248617 (maxscale) of user 977 dumped core. Stack trace of thread 1248617: #0 0x00007f7849cf49d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f7849b075e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f7849fca8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f7849fca9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f7849fbbfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248617 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248617 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:41 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2033-1248618-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2033-1248618-0.service has successfully entered the 'dead' state. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 66. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:42 ded101527.smartservers.com.au kernel: traps: maxscale[1248630] trap invalid opcode ip:7f21fb8df9d9 sp:7ffcd5d22120 error:0 in libmaxscale-common.so.1.0.0[7f21fb607000+37d000] Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248631/UID 0). -- Subject: Unit systemd-coredump@2034-1248631-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2034-1248631-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:42 ded101527.smartservers.com.au systemd-coredump[1248632]: Process 1248630 (maxscale) of user 977 dumped core. Stack trace of thread 1248630: #0 0x00007f21fb8df9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f21fb6f25e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f21fbbb58ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f21fbbb59ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f21fbba6fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248630 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248630 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2034-1248631-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2034-1248631-0.service has successfully entered the 'dead' state. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 67. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:42 ded101527.smartservers.com.au kernel: traps: maxscale[1248643] trap invalid opcode ip:7f737a8019d9 sp:7ffe9a4deee0 error:0 in libmaxscale-common.so.1.0.0[7f737a529000+37d000] Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248644/UID 0). -- Subject: Unit systemd-coredump@2035-1248644-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2035-1248644-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:42 ded101527.smartservers.com.au systemd-coredump[1248645]: Process 1248643 (maxscale) of user 977 dumped core. Stack trace of thread 1248643: #0 0x00007f737a8019d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f737a6145e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f737aad78ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f737aad79ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f737aac8fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248643 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248643 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:42 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2035-1248644-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2035-1248644-0.service has successfully entered the 'dead' state. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 68. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:43 ded101527.smartservers.com.au kernel: traps: maxscale[1248656] trap invalid opcode ip:7f93fc47d9d9 sp:7ffed5010b60 error:0 in libmaxscale-common.so.1.0.0[7f93fc1a5000+37d000] Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248657/UID 0). -- Subject: Unit systemd-coredump@2036-1248657-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2036-1248657-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:43 ded101527.smartservers.com.au systemd-coredump[1248658]: Process 1248656 (maxscale) of user 977 dumped core. Stack trace of thread 1248656: #0 0x00007f93fc47d9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f93fc2905e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f93fc7538ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f93fc7539ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f93fc744fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248656 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248656 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2036-1248657-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2036-1248657-0.service has successfully entered the 'dead' state. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 69. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:43 ded101527.smartservers.com.au kernel: traps: maxscale[1248669] trap invalid opcode ip:7f1d4bb1c9d9 sp:7ffca50410c0 error:0 in libmaxscale-common.so.1.0.0[7f1d4b844000+37d000] Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248670/UID 0). -- Subject: Unit systemd-coredump@2037-1248670-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2037-1248670-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:43 ded101527.smartservers.com.au systemd-coredump[1248671]: Process 1248669 (maxscale) of user 977 dumped core. Stack trace of thread 1248669: #0 0x00007f1d4bb1c9d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f1d4b92f5e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f1d4bdf28ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f1d4bdf29ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f1d4bde3fda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248669 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248669 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:43 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2037-1248670-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2037-1248670-0.service has successfully entered the 'dead' state. Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: maxscale.service: Service RestartSec=100ms expired, scheduling restart. Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: maxscale.service: Scheduled restart job, restart counter is at 70. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit maxscale.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: Stopped MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has finished shutting down. Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: Starting MariaDB MaxScale Database Proxy... -- Subject: Unit maxscale.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has begun starting up. Sep 01 22:07:44 ded101527.smartservers.com.au kernel: traps: maxscale[1248682] trap invalid opcode ip:7f7c044649d9 sp:7ffd818e0e60 error:0 in libmaxscale-common.so.1.0.0[7f7c0418c000+37d000] Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: Started Process Core Dump (PID 1248683/UID 0). -- Subject: Unit systemd-coredump@2038-1248683-0.service has finished start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit systemd-coredump@2038-1248683-0.service has finished starting up. -- -- The start-up result is done. Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: maxscale.service: Control process exited, code=dumped status=4 Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: maxscale.service: Failed with result 'core-dump'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit maxscale.service has entered the 'failed' state with result 'core-dump'. Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy. -- Subject: Unit maxscale.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit maxscale.service has failed. -- -- The result is failed. Sep 01 22:07:44 ded101527.smartservers.com.au systemd-coredump[1248684]: Process 1248682 (maxscale) of user 977 dumped core. Stack trace of thread 1248682: #0 0x00007f7c044649d9 _ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0) #1 0x00007f7c042775e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0) #2 0x00007f7c0473a8ba call_init.part.0 (ld-linux-x86-64.so.2) #3 0x00007f7c0473a9ba _dl_init (ld-linux-x86-64.so.2) #4 0x00007f7c0472bfda _dl_start_user (ld-linux-x86-64.so.2) -- Subject: Process 1248682 (maxscale) dumped core -- Defined-By: systemd -- Support: https://access.redhat.com/support -- Documentation: man:core(5) -- -- Process 1248682 (maxscale) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Sep 01 22:07:44 ded101527.smartservers.com.au systemd[1]: systemd-coredump@2038-1248683-0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit systemd-coredump@2038-1248683-0.service has successfully entered the 'dead' state.