Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.1.10
-
None
-
CentOS 7.2
-
2017-46
Description
As for the message I posted on https://jira.mariadb.org/browse/MXS-350, another way to generate an error like that one (OOM: mxs_realloc) is calling a non-existing configuration file, like below (observe that I have two "~"):
[root@maxscale ~]# maxscale -f ~ ~/maxscale_configs/basic.cnf |
* Error: Failed to start all MaxScale services. Exiting.
|
 |
MariaDB MaxScale /var/log/maxscale/maxscale.log Thu Nov 16 11:35:42 2017 |
----------------------------------------------------------------------------
|
^@^@^@2017-11-16 11:35:42 notice : Working directory: /var/log/maxscale |
2017-11-16 11:35:42 notice : MariaDB MaxScale 2.1.10 started |
2017-11-16 11:35:42 notice : MaxScale is running in process 4237 |
2017-11-16 11:35:42 notice : Configuration file: /root |
2017-11-16 11:35:42 notice : Log directory: /var/log/maxscale |
2017-11-16 11:35:42 notice : Data directory: /var/lib/maxscale |
2017-11-16 11:35:42 notice : Module directory: /usr/lib64/maxscale |
2017-11-16 11:35:42 notice : Service cache: /var/cache/maxscale |
2017-11-16 11:35:42 notice : Loading /root. |
2017-11-16 11:38:58 error : OOM: mxs_realloc |
2017-11-16 11:38:58 notice : /root.d does not exist, not reading. |
2017-11-16 11:38:58 notice : No query classifier specified, using default 'qc_sqlite'. |
2017-11-16 11:38:58 notice : Loaded module qc_sqlite: V1.0.0 from /usr/lib64/maxscale/libqc_sqlite.so |
2017-11-16 11:38:58 error : Failed to start all MaxScale services. Exiting. |
2017-11-16 11:38:58 MariaDB MaxScale is shut down. |
----------------------------------------------------
|
Thanks folks.
Attachments
Issue Links
- blocks
-
-
- Closed
-