Moved default file search paths to gwdirs.h which is configured by CMake from gwdirs.h.in.
This commit is contained in:
Markus Makela
parent
17a7b2addb
commit
c500d23d04
@ -6,23 +6,28 @@ endif()
|
||||
|
||||
message(STATUS "CMake version: ${CMAKE_VERSION}")
|
||||
|
||||
|
||||
include(${CMAKE_SOURCE_DIR}/cmake/macros.cmake)
|
||||
|
||||
# Set the installation layout
|
||||
set(INSTALL_LAYOUT "STANDALONE" CACHE STRING "Install layout, options are: STANDALONE, RPM, DEB")
|
||||
include(${CMAKE_SOURCE_DIR}/cmake/install_layout.cmake)
|
||||
|
||||
enable_testing()
|
||||
|
||||
set(INSTALL_LAYOUT "STANDALONE" CACHE STRING "Install layout, options are: STANDALONE, RPM, DEB")
|
||||
if(${INSTALL_LAYOUT} MATCHES "STANDALONE")
|
||||
set(CMAKE_INSTALL_PREFIX "/usr/local/mariadb-maxscale" CACHE PATH "Prefix prepended to install directories.")
|
||||
else()
|
||||
set(CMAKE_INSTALL_PREFIX "/usr" CACHE PATH "Prefix prepended to install directories.")
|
||||
endif()
|
||||
|
||||
# Set default values for cache entries and set the MaxScale version
|
||||
set_variables()
|
||||
set_maxscale_version()
|
||||
|
||||
set(CMAKE_BUILD_TYPE "RelWithDebInfo" CACHE STRING "Choose the type of build, options are: None(CMAKE_CXX_FLAGS or CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel.")
|
||||
|
||||
set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${CMAKE_SOURCE_DIR}/cmake")
|
||||
|
||||
project(MaxScale)
|
||||
|
||||
# Set the installation layout
|
||||
include(${CMAKE_SOURCE_DIR}/cmake/install_layout.cmake)
|
||||
|
||||
#Do the platform check
|
||||
include(cmake/CheckPlatform.cmake)
|
||||
|
||||
@ -51,10 +56,10 @@ if(${MAXSCALE_VERSION} MATCHES "-stable")
|
||||
message(FATAL_ERROR "Could not find the release notes for this stable release: ${MAXSCALE_VERSION_NUMERIC}")
|
||||
endif()
|
||||
endif()
|
||||
set(CMAKE_INSTALL_RPATH ${CMAKE_INSTALL_RPATH}:${CMAKE_INSTALL_PREFIX}/${MAXSCALE_MODULE_INSTALL}:${CMAKE_INSTALL_PREFIX}/${MAXSCALE_LIBRARY_INSTALL})
|
||||
|
||||
file(MAKE_DIRECTORY ${CMAKE_BINARY_DIR}/server/include)
|
||||
configure_file(${CMAKE_SOURCE_DIR}/server/include/version.h.in ${CMAKE_BINARY_DIR}/server/include/version.h)
|
||||
configure_file(${CMAKE_SOURCE_DIR}/server/include/gwdirs.h.in ${CMAKE_BINARY_DIR}/server/include/gwdirs.h)
|
||||
configure_file(${CMAKE_SOURCE_DIR}/server/test/maxscale_test.h.in ${CMAKE_BINARY_DIR}/server/include/maxscale_test.h)
|
||||
configure_file(${CMAKE_SOURCE_DIR}/etc/postinst.in ${CMAKE_BINARY_DIR}/postinst)
|
||||
configure_file(${CMAKE_SOURCE_DIR}/etc/postrm.in ${CMAKE_BINARY_DIR}/postrm)
|
||||
|
||||
@ -1,37 +1,25 @@
|
||||
Installation and startup
|
||||
|
||||
Untar the binary distribution in the desired location,
|
||||
e.g. /usr/local/mariadb
|
||||
e.g. /usr/local/mariadb-maxscale
|
||||
|
||||
Alternatively build from the source code using the instructions
|
||||
in the README file and execute make install.
|
||||
in the [Building MaxScale from Source Code](../Getting-Started/Building-MaxScale-from-Source-Code.md) document.
|
||||
|
||||
Simply set the environment variable MAXSCALE_HOME to point to the
|
||||
MaxScale directory, found inside the path into which the files have been copied,
|
||||
e.g. MAXSCALE_HOME=/usr/local/mariadb-maxscale
|
||||
|
||||
Also you will need to optionally set LD_LIBRARY_PATH to include the 'lib' folder,
|
||||
found inside the path into which the files have been copied,
|
||||
e.g. LD_LIBRARY_PATH=/usr/local/mariadb-maxscale/lib
|
||||
|
||||
Because we need the libmysqld library for parsing we must create a
|
||||
valid my.cnf file to enable the library to be used. Copy the my.cnf
|
||||
to $MAXSCALE_HOME/mysql/my.cnf.
|
||||
|
||||
To start MaxScale execute the command 'maxscale' from the bin folder,
|
||||
e.g. /usr/local/mariadb-maxscale/bin/maxscale
|
||||
You can start MaxScale using `service maxscale start` or `systemctl start maxscale` if you installed the init.d scripts
|
||||
or by manually starting the process from the bin folder of the installation directory.
|
||||
|
||||
Configuration
|
||||
|
||||
You need to edit the file MaxScale.cnf in $MAXSCALE_HOME/etc, you should
|
||||
define the set of server definitions you require, with the addresses
|
||||
and ports of those servers. Also define the listening ports for your
|
||||
various services.
|
||||
You need to create or edit the MaxScale.cnf file in the /etc folder.
|
||||
Define the services you wish to provide, the set of server definitions
|
||||
you require, with the addresses and ports of those servers and also
|
||||
define the listening ports for your various services.
|
||||
|
||||
In order to view the internal activity of the gateway you can telnet to
|
||||
In order to view the internal activity of MaxScale you can either use
|
||||
the maxadmin client interface with the cli routing module or telnet to
|
||||
the port defined for the telnet listener. Initially you may login with
|
||||
the user name of "admin" and the password "mariadb". Once connected type
|
||||
help for an overview of the commands and help <command> for the more
|
||||
detailed help on commands. Use the add user command to add a new user,
|
||||
this will also remove the admin/mariadb user.
|
||||
|
||||
|
||||
@ -27,11 +27,9 @@ connection failover| When a connection currently being used between MaxScale and
|
||||
|
||||
The MaxScale configuration is read from a file which can be located in a number of placing, MaxScale will search for the configuration file in a number of locations.
|
||||
|
||||
1. If the environment variable `MAXSCALE_HOME` is set then MaxScale will look for a configuration file called `MaxScale.cnf` in the directory `$MAXSCALE_HOME/etc`.
|
||||
1. Location given with the --configdir=<path> command line argument
|
||||
|
||||
2. If `MAXSCALE_HOME` is not set or the configuration file is not in the location above MaxScale will look for a file in `/etc/MaxScale.cnf`.
|
||||
|
||||
Alternatively MaxScale can be started with the `-c` flag and the path of the MaxScale home directory tree.
|
||||
2. MaxScale will look for a configuration file called `MaxScale.cnf` in the directory `/etc/MaxScale.cnf`
|
||||
|
||||
An explicit path to a configuration file can be passed by using the `-f` option to MaxScale.
|
||||
|
||||
@ -524,7 +522,7 @@ Default value is `2`. Write Timeout is the timeout in seconds for each attempt t
|
||||
|
||||
## Protocol Modules
|
||||
|
||||
The protocols supported by MaxScale are implemented as external modules that are loaded dynamically into the MaxScale core. These modules reside in the directory `$MAXSCALE_HOME/modules`, if the environment variable `$MAXSCALE_HOME` is not set it defaults to `/usr/local/mariadb-maxscale`. It may also be set by passing the `-c` option on the MaxScale command line.
|
||||
The protocols supported by MaxScale are implemented as external modules that are loaded dynamically into the MaxScale core. These modules reside in the directory `/usr/lib64/maxscale`. The location can be overridden with the `libdir=PATH` parameter under the `[maxscale]` section. It may also be set by passing the `-B PATH` or `--libdir=PATH` option on the MaxScale command line.
|
||||
|
||||
### MySQLClient
|
||||
|
||||
|
||||
@ -62,11 +62,9 @@ shared objects that are loaded on demand. In order for MaxScale to find these
|
||||
modules it will search using a predescribed search path. The rules are:
|
||||
|
||||
1. Look in the current directory for the module
|
||||
2. Look in $MAXSCALE_HOME/modules
|
||||
3. Look in /usr/local/mariadb-maxscale/modules
|
||||
|
||||
Configuration is read by default from the file $MAXSCALE_HOME/etc/MaxScale.cnf, /etc/MaxScale.cnf. An example file is included in in the installation and can be found in the etc/ folder within the MaxScale installation. The default value of MAXSCALE_HOME can be overridden by using the -c flag on the command line. This should be immediately followed by the path to the MaxScale home directory. The -f flag can be used on the command line to set the name and the location of the configuration file. Without path expression the file is read from \$MAXSCALE_HOME/etc directory.
|
||||
2. Look in /usr/lib64/maxscale
|
||||
|
||||
Configuration is read by default from the file /etc/MaxScale.cnf. An example file is included in in the installation and can be found in the /usr/share/maxscale folder within the MaxScale installation. The -f flag can be used on the command line to set the name and the location of the configuration file. Without path expression the file is read from the /etc directory.
|
||||
|
||||
## Administration Of MaxScale
|
||||
|
||||
|
||||
@ -45,7 +45,7 @@ Options may be passed to the MaxScale binary that alter this default behavior, t
|
||||
<tr>
|
||||
<td>-f</td>
|
||||
<td>--config=</td>
|
||||
<td>Use the filename passed as an argument instead of looking in $MAXSCALE_HOME/etc/MaxScale.cnf</td>
|
||||
<td>Use the filename passed as an argument instead of looking in /etc/MaxScale.cnf</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>-l<file>|<shm></td>
|
||||
@ -79,7 +79,7 @@ or
|
||||
|
||||
MaxScale will also stop gracefully if it received a hangup signal, to find the process id of the MaxScale server use the ps command or read the contents of the maxscale.pid file located in the same directory as the logs.
|
||||
|
||||
$ kill -HUP `cat $MAXSCALE_HOME/log/maxscale.pid`
|
||||
$ kill -HUP `cat /log/maxscale.pid`
|
||||
|
||||
In order to shutdown MaxScale using the maxadmin command you may either connect with maxadmin in interactive mode or pass the "shutdown maxscale" command you wish to execute as an argument to maxadmin.
|
||||
|
||||
|
||||
@ -60,7 +60,7 @@ If you wish to use two different usernames for the two different roles of monito
|
||||
|
||||
### Creating Your MaxScale Configuration
|
||||
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory $MAXSCALE_HOME/etc, if you have installed in the default location then this file is available in /usr/local/mariadb-maxscale/etc/MaxScale.cnf. This is not created as part of the installation process and must be manually created. A template file does exist within this directory that may be use as a basis for your configuration.
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory /etc, if you have installed in the default location then this file is available in /usr/local/mariadb-maxscale/etc/MaxScale.cnf. This is not created as part of the installation process and must be manually created. A template file does exist within this directory that may be use as a basis for your configuration.
|
||||
|
||||
A global, maxscale, section is included within every MaxScale configuration file; this is used to set the values of various MaxScale wide parameters, perhaps the most important of these is the number of threads that MaxScale will use to execute the code that forwards requests and handles responses for clients.
|
||||
|
||||
|
||||
@ -62,7 +62,7 @@ If you wish to use two different usernames for the two different roles of monito
|
||||
|
||||
### Creating Your MaxScale Configuration
|
||||
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory $MAXSCALE_HOME/etc, if you have installed in the default location then this file is available in /usr/local/mariadb-maxscale/etc/MaxScale.cnf. This is not created as part of the installation process and must be manually created. A template file does exist within this directory that may be use as a basis for your configuration.
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory /etc, if you have installed in the default location then this file is available in /usr/local/mariadb-maxscale/etc/MaxScale.cnf. This is not created as part of the installation process and must be manually created. A template file does exist within this directory that may be use as a basis for your configuration.
|
||||
|
||||
A global, maxscale, section is included within every MaxScale configuration file; this is used to set the values of various MaxScale wide parameters, perhaps the most important of these is the number of threads that MaxScale will use to execute the code that forwards requests and handles responses for clients.
|
||||
|
||||
|
||||
@ -11,48 +11,59 @@ The service entry needs to define the service name, the type as service and the
|
||||
The specified user, with the password (plain or encrypted via maxpassword utility) is allowed to connect via MySQL protocol.
|
||||
Currently the user can connect to maxinfo from any remote IP and to localhost as well.
|
||||
|
||||
```
|
||||
[MaxInfo]
|
||||
type=service
|
||||
router=maxinfo
|
||||
user=monitor
|
||||
passwd=EBD2F49C3B375812A8CDEBA632ED8BBC
|
||||
```
|
||||
|
||||
The listener section defines the protocol, port and other information needed to create a listener for the service. To listen on a port using the MySQL protocol a section as shown below should be added to the configuration file.
|
||||
|
||||
```
|
||||
[MaxInfo Listener]
|
||||
type=listener
|
||||
service=MaxInfo
|
||||
protocol=MySQLClient
|
||||
port=9003
|
||||
```
|
||||
|
||||
To listen with the HTTP protocol and hence return JSON documents a section as should below is required.
|
||||
|
||||
```
|
||||
[MaxInfo JSON Listener]
|
||||
type=listener
|
||||
service=MaxInfo
|
||||
protocol=HTTPD
|
||||
port=8003
|
||||
|
||||
```
|
||||
|
||||
If both the MySQL and JSON responses are required then a single service can be configured with both types of listener.
|
||||
|
||||
As with any other listeners within MaxScale the listeners can be bound to a particular interface by use of the address= parameter. This allows the access to the maxinfo data to be limited to the localhost by adding an address=localhost parameter in the configuration file.
|
||||
|
||||
```
|
||||
[MaxInfo Listener]
|
||||
type=listener
|
||||
service=MaxInfo
|
||||
protocol=MySQLClient
|
||||
address=localhost
|
||||
port=9003
|
||||
```
|
||||
|
||||
# MySQL Interface to maxinfo
|
||||
|
||||
The maxinfo supports a small subset of SQL statements in addition to the MySQL status and ping requests. These may be used for simple monitoring of MaxScale.
|
||||
|
||||
```
|
||||
% mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pxyz ping
|
||||
mysqld is alive
|
||||
% mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pxyz status
|
||||
Uptime: 72 Threads: 1 Sessions: 11
|
||||
%
|
||||
```
|
||||
|
||||
The SQL command used to interact with maxinfo is the show command, a variety of show commands are available and will be described in the following sections.
|
||||
|
||||
@ -60,6 +71,7 @@ The SQL command used to interact with maxinfo is the show command, a variety of
|
||||
|
||||
The show variables command will display a set of name and value pairs for a number of MaxScale system variables.
|
||||
|
||||
```
|
||||
mysql> show variables;
|
||||
+--------------------+-------------------------+
|
||||
| Variable_name | Value |
|
||||
@ -77,9 +89,11 @@ The show variables command will display a set of name and value pairs for a numb
|
||||
9 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
The show variables command can also accept a limited like clause. This like clause must either be a literal string to match, a pattern starting with a %, a pattern ending with a % or a string with a % at both the start and the end.
|
||||
|
||||
```
|
||||
mysql> show variables like 'version';
|
||||
+---------------+----------------+
|
||||
| Variable_name | Value |
|
||||
@ -116,11 +130,13 @@ The show variables command can also accept a limited like clause. This like clau
|
||||
3 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show status
|
||||
|
||||
The show status command displays a set of status counters, as with show variables the show status command can be passed a simplified like clause to limit the values returned.
|
||||
|
||||
```
|
||||
mysql> show status;
|
||||
+---------------------------+-------+
|
||||
| Variable_name | Value |
|
||||
@ -151,11 +167,13 @@ The show status command displays a set of status counters, as with show variable
|
||||
22 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show services
|
||||
|
||||
The show services command will return a set of basic statistics regarding each of the configured services within MaxScale.
|
||||
|
||||
```
|
||||
mysql> show services;
|
||||
+----------------+----------------+--------------+----------------+
|
||||
| Service Name | Router Module | No. Sessions | Total Sessions |
|
||||
@ -172,6 +190,7 @@ The show services command will return a set of basic statistics regarding each o
|
||||
8 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
The show services command does not accept a like clause and will ignore any like clause that is given.
|
||||
|
||||
@ -179,6 +198,7 @@ The show services command does not accept a like clause and will ignore any like
|
||||
|
||||
The show listeners command will return a set of status information for every listener defined within the MaxScale configuration file.
|
||||
|
||||
```
|
||||
mysql> show listeners;
|
||||
+----------------+-----------------+-----------+------+---------+
|
||||
| Service Name | Protocol Module | Address | Port | State |
|
||||
@ -196,6 +216,7 @@ The show listeners command will return a set of status information for every lis
|
||||
9 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
The show listeners command will ignore any like clause passed to it.
|
||||
|
||||
@ -203,6 +224,7 @@ The show listeners command will ignore any like clause passed to it.
|
||||
|
||||
The show sessions command returns information on every active session within MaxScale. It will ignore any like clause passed to it.
|
||||
|
||||
```
|
||||
mysql> show sessions;
|
||||
+-----------+---------------+----------------+---------------------------+
|
||||
| Session | Client | Service | State |
|
||||
@ -222,11 +244,13 @@ The show sessions command returns information on every active session within Max
|
||||
11 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show clients
|
||||
|
||||
The show clients command reports a row for every client application connected to MaxScale. Like clauses are not available of the show clients command.
|
||||
|
||||
```
|
||||
mysql> show clients;
|
||||
+-----------+---------------+---------+---------------------------+
|
||||
| Session | Client | Service | State |
|
||||
@ -237,11 +261,13 @@ The show clients command reports a row for every client application connected to
|
||||
2 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show servers
|
||||
|
||||
The show servers command returns data for each backend server configured within the MaxScale configuration file. This data includes the current number of connections MaxScale has to that server and the state of that server as monitored by MaxScale.
|
||||
|
||||
```
|
||||
mysql> show servers;
|
||||
+---------+-----------+------+-------------+---------+
|
||||
| Server | Address | Port | Connections | Status |
|
||||
@ -254,11 +280,13 @@ The show servers command returns data for each backend server configured within
|
||||
4 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show modules
|
||||
|
||||
The show modules command reports the information on the modules currently loaded into MaxScale. This includes the name type and version of each module. It also includes the API version the module has been written against and the current release status of the module.
|
||||
|
||||
```
|
||||
mysql> show modules;
|
||||
+----------------+-------------+---------+-------------+----------------+
|
||||
| Module Name | Module Type | Version | API Version | Status |
|
||||
@ -277,12 +305,13 @@ The show modules command reports the information on the modules currently loaded
|
||||
10 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
|
||||
```
|
||||
|
||||
## Show monitors
|
||||
|
||||
The show monitors command reports each monitor configured within the system and the state of that monitor.
|
||||
|
||||
```
|
||||
mysql> show monitors;
|
||||
+---------------+---------+
|
||||
| Monitor | Status |
|
||||
@ -292,12 +321,13 @@ The show monitors command reports each monitor configured within the system and
|
||||
1 row in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
|
||||
```
|
||||
|
||||
## Show eventTimes
|
||||
|
||||
The show eventTimes command returns a table of statistics that reflect the performance of the event queuing and execution portion of the MaxScale core.
|
||||
|
||||
```
|
||||
mysql> show eventTimes;
|
||||
+---------------+-------------------+---------------------+
|
||||
| Duration | No. Events Queued | No. Events Executed |
|
||||
@ -336,6 +366,7 @@ The show eventTimes command returns a table of statistics that reflect the perfo
|
||||
30 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
```
|
||||
|
||||
Each row represents a time interval, in 100ms increments, with the counts representing the number of events that were in the event queue for the length of time that row represents and the number of events that were executing of the time indicated by the row.
|
||||
|
||||
@ -347,6 +378,7 @@ The simplified JSON interface takes the URL of the request made to maxinfo and m
|
||||
|
||||
The /variables URL will return the MaxScale variables, these variables can not be filtered via this interface.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/variables
|
||||
[ { "Variable_name" : "version", "Value" : "1.0.6-unstable"},
|
||||
{ "Variable_name" : "version_comment", "Value" : "MariaDB MaxScale"},
|
||||
@ -358,11 +390,13 @@ The /variables URL will return the MaxScale variables, these variables can not b
|
||||
{ "Variable_name" : "MAXSCALE_UPTIME", "Value" : 3948},
|
||||
{ "Variable_name" : "MAXSCALE_SESSIONS", "Value" : 12}]
|
||||
$
|
||||
```
|
||||
|
||||
## Status
|
||||
|
||||
Use of the /status URI will return the status information that would normally be returned by the show status command. No filtering of the status information is available via this interface
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/status
|
||||
[ { "Variable_name" : "Uptime", "Value" : 3831},
|
||||
{ "Variable_name" : "Uptime_since_flush_status", "Value" : 3831},
|
||||
@ -387,11 +421,13 @@ Use of the /status URI will return the status information that would normally be
|
||||
{ "Variable_name" : "Max_event_queue_time", "Value" : 0},
|
||||
{ "Variable_name" : "Max_event_execution_time", "Value" : 1}]
|
||||
$
|
||||
```
|
||||
|
||||
## Services
|
||||
|
||||
The /services URI returns the data regarding the services defined within the configuration of MaxScale. Two counters are returned, the current number of sessions attached to this service and the total number connected since the service started.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/services
|
||||
[ { "Service Name" : "Test Service", "Router Module" : "readconnroute", "No. Sessions" : 1, "Total Sessions" : 1},
|
||||
{ "Service Name" : "Split Service", "Router Module" : "readwritesplit", "No. Sessions" : 1, "Total Sessions" : 1},
|
||||
@ -402,11 +438,13 @@ The /services URI returns the data regarding the services defined within the con
|
||||
{ "Service Name" : "CLI", "Router Module" : "cli", "No. Sessions" : 1, "Total Sessions" : 1},
|
||||
{ "Service Name" : "MaxInfo", "Router Module" : "maxinfo", "No. Sessions" : 5, "Total Sessions" : 20}]
|
||||
$
|
||||
```
|
||||
|
||||
## Listeners
|
||||
|
||||
The /listeners URI will return a JSON array with one entry per listener, each entry is a JSON object that describes the configuration and state of that listener.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/listeners
|
||||
[ { "Service Name" : "Test Service", "Protocol Module" : "MySQLClient", "Address" : "*", "Port" : 4006, "State" : "Running"},
|
||||
{ "Service Name" : "Split Service", "Protocol Module" : "MySQLClient", "Address" : "*", "Port" : 4007, "State" : "Running"},
|
||||
@ -418,11 +456,13 @@ The /listeners URI will return a JSON array with one entry per listener, each en
|
||||
{ "Service Name" : "MaxInfo", "Protocol Module" : "MySQLClient", "Address" : "*", "Port" : 9003, "State" : "Running"},
|
||||
{ "Service Name" : "MaxInfo", "Protocol Module" : "HTTPD", "Address" : "*", "Port" : 8003, "State" : "Running"}]
|
||||
$
|
||||
```
|
||||
|
||||
## Modules
|
||||
|
||||
The /modules URI returns data for each plugin that has been loaded into MaxScale. The plugin name, type and version are returned as is the version of the plugin API that the plugin was built against and the release status of the plugin.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/modules
|
||||
[ { "Module Name" : "HTTPD", "Module Type" : "Protocol", "Version" : "V1.0.1", "API Version" : "1.0.0", "Status" : "In Development"},
|
||||
{ "Module Name" : "maxscaled", "Module Type" : "Protocol", "Version" : "V1.0.0", "API Version" : "1.0.0", "Status" : "GA"},
|
||||
@ -435,11 +475,13 @@ The /modules URI returns data for each plugin that has been loaded into MaxScale
|
||||
{ "Module Name" : "cli", "Module Type" : "Router", "Version" : "V1.0.0", "API Version" : "1.0.0", "Status" : "GA"},
|
||||
{ "Module Name" : "maxinfo", "Module Type" : "Router", "Version" : "V1.0.0", "API Version" : "1.0.0", "Status" : "Alpha"}]
|
||||
$
|
||||
```
|
||||
|
||||
## Sessions
|
||||
|
||||
The /sessions URI returns a JSON array with an object for each active session within MaxScale.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/sessions
|
||||
[ { "Session" : "0x1a8e9a0", "Client" : "80.176.79.245", "Service" : "MaxInfo", "State" : "Session ready for routing"},
|
||||
{ "Session" : "0x1a8e6d0", "Client" : "80.240.130.35", "Service" : "MaxInfo", "State" : "Session ready for routing"},
|
||||
@ -453,32 +495,38 @@ The /sessions URI returns a JSON array with an object for each active session wi
|
||||
{ "Session" : "0x1a5c530", "Client" : , "Service" : "Split Service", "State" : "Listener Session"},
|
||||
{ "Session" : "0x19ac1c0", "Client" : , "Service" : "Test Service", "State" : "Listener Session"}]
|
||||
$
|
||||
```
|
||||
|
||||
## Clients
|
||||
|
||||
The /clients URI is a limited version of the /sessions, in this case it only returns an entry for a session that represents a client connection.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/clients
|
||||
[ { "Session" : "0x1a90be0", "Client" : "80.176.79.245", "Service" : "MaxInfo", "State" : "Session ready for routing"},
|
||||
{ "Session" : "0x1a8e9a0", "Client" : "127.0.0.1", "Service" : "MaxInfo", "State" : "Session ready for routing"},
|
||||
{ "Session" : "0x1a8e6d0", "Client" : "80.240.130.35", "Service" : "MaxInfo", "State" : "Session ready for routing"}]
|
||||
$
|
||||
```
|
||||
|
||||
## Servers
|
||||
|
||||
The /servers URI is used to retrieve information for each of the servers defined within the MaxScale configuration. This information includes the connection count and the current status as monitored by MaxScale. The connection count is only those connections made by MaxScale to those servers.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/servers
|
||||
[ { "Server" : "server1", "Address" : "127.0.0.1", "Port" : 3306, "Connections" : 0, "Status" : "Running"},
|
||||
{ "Server" : "server2", "Address" : "127.0.0.1", "Port" : 3307, "Connections" : 0, "Status" : "Down"},
|
||||
{ "Server" : "server3", "Address" : "127.0.0.1", "Port" : 3308, "Connections" : 0, "Status" : "Down"},
|
||||
{ "Server" : "server4", "Address" : "127.0.0.1", "Port" : 3309, "Connections" : 0, "Status" : "Down"}]
|
||||
$
|
||||
```
|
||||
|
||||
## Event Times
|
||||
|
||||
The /event/times URI returns an array of statistics that reflect the performance of the event queuing and execution portion of the MaxScale core. Each element is an object that represents a time bucket, in 100ms increments, with the counts representing the number of events that were in the event queue for the length of time that row represents and the number of events that were executing of the time indicated by the object.
|
||||
|
||||
```
|
||||
$ curl http://maxscale.mariadb.com:8003/event/times
|
||||
[ { "Duration" : "< 100ms", "No. Events Queued" : 64, "No. Events Executed" : 63},
|
||||
{ "Duration" : " 100 - 200ms", "No. Events Queued" : 0, "No. Events Executed" : 0},
|
||||
@ -510,3 +558,4 @@ The /event/times URI returns an array of statistics that reflect the performance
|
||||
{ "Duration" : "2700 - 2800ms", "No. Events Queued" : 0, "No. Events Executed" : 0},
|
||||
{ "Duration" : "2800 - 2900ms", "No. Events Queued" : 0, "No. Events Executed" : 0},
|
||||
{ "Duration" : "> 3000ms", "No. Events Queued" : 0, "No. Events Executed" : 0}]
|
||||
```
|
||||
|
||||
@ -36,6 +36,7 @@ The first user required must be able to select data from the table mysql.user, t
|
||||
|
||||
2. Create the user, substituting the username, password and host on which maxscale runs within your environment
|
||||
|
||||
```
|
||||
MariaDB [(none)]> create user '*username*'@'*maxscalehost*' identified by '*password*';
|
||||
|
||||
**Query OK, 0 rows affected (0.00 sec)**
|
||||
@ -45,9 +46,11 @@ MariaDB [(none)]> create user '*username*'@'*maxscalehost*' identified by '*pass
|
||||
MariaDB [(none)]> grant SELECT on mysql.user to '*username*'@'*maxscalehost*';
|
||||
|
||||
**Query OK, 0 rows affected (0.03 sec)**
|
||||
```
|
||||
|
||||
Additionally, GRANT SELECT on the mysql.db table and SHOW DATABASES privileges are required in order to load databases name and grants suitable for database name authorization.
|
||||
|
||||
```
|
||||
MariaDB [(none)]> GRANT SELECT ON mysql.db TO 'username'@'maxscalehost';
|
||||
|
||||
**Query OK, 0 rows affected (0.00 sec)**
|
||||
@ -55,9 +58,11 @@ MariaDB [(none)]> GRANT SELECT ON mysql.db TO 'username'@'maxscalehost';
|
||||
MariaDB [(none)]> GRANT SHOW DATABASES ON *.* TO 'username'@'maxscalehost';
|
||||
|
||||
**Query OK, 0 rows affected (0.00 sec)**
|
||||
```
|
||||
|
||||
The second user is used to monitored the state of the cluster. This user, which may be the same username as the first, requires permissions to access the various sources of monitoring data. In order to monitor a replication cluster this user must be granted the roles REPLICATION SLAVE and REPLICATION CLIENT
|
||||
|
||||
```
|
||||
MariaDB [(none)]> grant REPLICATION SLAVE on *.* to '*username*'@'*maxscalehost*';
|
||||
|
||||
**Query OK, 0 rows affected (0.00 sec)**
|
||||
@ -65,220 +70,174 @@ MariaDB [(none)]> grant REPLICATION SLAVE on *.* to '*username*'@'*maxscalehost*
|
||||
MariaDB [(none)]> grant REPLICATION CLIENT on *.* to '*username*'@'*maxscalehost*';
|
||||
|
||||
**Query OK, 0 rows affected (0.00 sec)**
|
||||
```
|
||||
|
||||
If you wish to use two different usernames for the two different roles of monitoring and collecting user information then create a different username using the first two steps from above.
|
||||
|
||||
## Creating Your MaxScale Configuration
|
||||
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory $MAXSCALE_HOME/etc, if you have installed in the default location then this file is available in /usr/local/mariadb/maxscle/etc/MaxScale.cnf. This is not created as part of the installation process and must be manually created. A template file does exist within this directory that may be use as a basis for your configuration.
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory /etc. This is not created as part of the installation process and must be manually created. A template file does exist in the `/usr/share/maxscale` folder that can be use as a basis for your configuration.
|
||||
|
||||
A global, maxscale, section is included within every MaxScale configuration file; this is used to set the values of various MaxScale wide parameters, perhaps the most important of these is the number of threads that MaxScale will use to execute the code that forwards requests and handles responses for clients.
|
||||
|
||||
```
|
||||
[maxscale]
|
||||
|
||||
threads=4
|
||||
```
|
||||
|
||||
Since we are using MySQL Replication and connection routing we want two different ports to which the client application can connect; one that will be directed to the current master within the replication cluster and another that will load balance between the slaves. To achieve this within MaxScale we need to define two services in the ini file; one for the read/write operations that should be executed on the master server and another for connections to one of the slaves. Create a section for each in your MaxScale.ini file and set the type to service, the section names are the names of the services themselves and should be meaningful to the administrator. Names may contain whitespace.
|
||||
|
||||
```
|
||||
[Write Service]
|
||||
|
||||
type=service
|
||||
|
||||
[Read Service]
|
||||
|
||||
type=service
|
||||
|
||||
```
|
||||
The router for these two sections is identical, the readconnroute module, also the services should be provided with the list of servers that will be part of the cluster. The server names given here are actually the names of server sections in the configuration file and not the physical hostnames or addresses of the servers.
|
||||
|
||||
```
|
||||
[Write Service]
|
||||
|
||||
type=service
|
||||
|
||||
router=readconnroute
|
||||
|
||||
servers=dbserv1, dbserv2, dbserv3
|
||||
|
||||
[Read Service]
|
||||
|
||||
type=service
|
||||
|
||||
router=readconnroute
|
||||
|
||||
servers=dbserv1, dbserv2, dbserv3
|
||||
```
|
||||
|
||||
In order to instruct the router to which servers it should route we must add router options to the service. The router options are compared to the status that the monitor collects from the servers and used to restrict the eligible set of servers to which that service may route. In our case we use the two options master and slave for our two services.
|
||||
|
||||
```
|
||||
[Write Service]
|
||||
|
||||
type=service
|
||||
|
||||
router=readconnroute
|
||||
|
||||
router_options=master
|
||||
|
||||
servers=dbserv1, dbserv2, dbserv3
|
||||
|
||||
[Read Service]
|
||||
|
||||
type=service
|
||||
|
||||
router=readconnroute
|
||||
|
||||
router_options=slave
|
||||
|
||||
servers=dbserv1, dbserv2, dbserv3
|
||||
```
|
||||
|
||||
The final step in the service sections is to add the username and password that will be used to populate the user data from the database cluster. There are two options for representing the password, either plain text or encrypted passwords may be used. In order to use encrypted passwords a set of keys must be generated that will be used by the encryption and decryption process. To generate the keys use the maxkeys command and pass the name of the secrets file in which the keys are stored.
|
||||
|
||||
% maxkeys /usr/local/mariadb-maxscale/etc/.secrets
|
||||
|
||||
%
|
||||
```
|
||||
maxkeys /usr/local/mariadb-maxscale/etc/.secrets
|
||||
```
|
||||
|
||||
Once the keys have been created the maxpasswd command can be used to generate the encrypted password.
|
||||
|
||||
% maxpasswd plainpassword
|
||||
|
||||
```
|
||||
maxpasswd plainpassword
|
||||
96F99AA1315BDC3604B006F427DD9484
|
||||
|
||||
%
|
||||
```
|
||||
|
||||
The username and password, either encrypted or plain text, are stored in the service section using the user and passwd parameters.
|
||||
|
||||
```
|
||||
[Write Service]
|
||||
|
||||
type=service
|
||||
|
||||
router=readconnroute
|
||||
|
||||
router_options=master
|
||||
|
||||
servers=dbserv1, dbserv2, dbserv3
|
||||
|
||||
user=maxscale
|
||||
|
||||
passwd=96F99AA1315BDC3604B006F427DD9484
|
||||
|
||||
[Read Service]
|
||||
|
||||
type=service
|
||||
|
||||
router=readconnroute
|
||||
|
||||
router_options=slave
|
||||
|
||||
servers=dbserv1, dbserv2, dbserv3
|
||||
|
||||
user=maxscale
|
||||
|
||||
passwd=96F99AA1315BDC3604B006F427DD9484
|
||||
```
|
||||
|
||||
This completes the definitions required by the services, however listening ports must be associated with the services in order to allow network connections. This is done by creating a series of listener sections. These sections again are named for the convenience of the administrator and should be of type listener with an entry labeled service which contains the name of the service to associate the listener with. Each service may have multiple listeners.
|
||||
|
||||
```
|
||||
[Write Listener]
|
||||
|
||||
type=listener
|
||||
|
||||
service=Write Service
|
||||
|
||||
[Read Listener]
|
||||
|
||||
type=listener
|
||||
|
||||
service=Read Service
|
||||
```
|
||||
|
||||
A listener must also define the protocol module it will use for the incoming network protocol, currently this should be the MySQLClient protocol for all database listeners. The listener may then supply a network port to listen on and/or a socket within the file system.
|
||||
|
||||
```
|
||||
[Write Listener]
|
||||
|
||||
type=listener
|
||||
|
||||
service=Write Service
|
||||
|
||||
protocol=MySQLClient
|
||||
|
||||
port=4306
|
||||
|
||||
socket=/tmp/ClusterMaster
|
||||
|
||||
[Read Listener]
|
||||
|
||||
type=listener
|
||||
|
||||
service=Read Service
|
||||
|
||||
protocol=MySQLClient
|
||||
|
||||
port=4307
|
||||
```
|
||||
|
||||
An address parameter may be given if the listener is required to bind to a particular network address when using hosts with multiple network addresses. The default behavior is to listen on all network interfaces.
|
||||
|
||||
The next stage is the configuration is to define the server information. This defines how to connect to each of the servers within the cluster, again a section is created for each server, with the type set to server, the network address and port to connect to and the protocol to use to connect to the server. Currently the protocol for all database connections in MySQLBackend.
|
||||
|
||||
```
|
||||
[dbserv1]
|
||||
|
||||
type=server
|
||||
|
||||
address=192.168.2.1
|
||||
|
||||
port=3306
|
||||
|
||||
protocol=MySQLBackend
|
||||
|
||||
[dbserv2]
|
||||
|
||||
type=server
|
||||
|
||||
address=192.168.2.2
|
||||
|
||||
port=3306
|
||||
|
||||
protocol=MySQLBackend
|
||||
|
||||
[dbserv3]
|
||||
|
||||
type=server
|
||||
|
||||
address=192.168.2.3
|
||||
|
||||
port=3306
|
||||
|
||||
protocol=MySQLBackend
|
||||
```
|
||||
|
||||
In order for MaxScale to monitor the servers using the correct monitoring mechanisms a section should be provided that defines the monitor to use and the servers to monitor. Once again a section is created with a symbolic name for the monitor, with the type set to monitor. Parameters are added for the module to use, the list of servers to monitor and the username and password to use when connecting to the the servers with the monitor.
|
||||
|
||||
```
|
||||
[Replication Monitor]
|
||||
|
||||
type=monitor
|
||||
|
||||
module=mysqlmon
|
||||
|
||||
servers=dbserv1, dbserv2, dbserv3
|
||||
|
||||
user=maxscale
|
||||
|
||||
passwd=96F99AA1315BDC3604B006F427DD9484
|
||||
```
|
||||
|
||||
As with the password definition in the server either plain text or encrypted passwords may be used.
|
||||
|
||||
The final stage in the configuration is to add the option service which is used by the maxadmin command to connect to MaxScale for monitoring and administration purposes. This creates a service section and a listener section.
|
||||
|
||||
```
|
||||
[CLI]
|
||||
|
||||
type=service
|
||||
|
||||
router=cli
|
||||
|
||||
[CLI Listener]
|
||||
|
||||
type=listener
|
||||
|
||||
service=CLI
|
||||
|
||||
protocol=maxscaled
|
||||
|
||||
address=localhost
|
||||
|
||||
port=6603
|
||||
```
|
||||
|
||||
In the case of the example above it should be noted that an address parameter has been given to the listener, this limits connections to maxadmin commands that are executed on the same machine that hosts MaxScale.
|
||||
|
||||
@ -286,14 +245,19 @@ In the case of the example above it should be noted that an address parameter ha
|
||||
|
||||
Upon completion of the configuration process MaxScale is ready to be started for the first time. This may either be done manually by running the maxscale command or via the service interface.
|
||||
|
||||
% maxscale
|
||||
```
|
||||
maxscale
|
||||
```
|
||||
|
||||
or
|
||||
|
||||
% service maxscale start
|
||||
```
|
||||
service maxscale start
|
||||
```
|
||||
|
||||
Check the error log in /usr/local/mariadb-maxscale/log to see if any errors are detected in the configuration file and to confirm MaxScale has been started. Also the maxadmin command may be used to confirm that MaxScale is running and the services, listeners etc have been correctly configured.
|
||||
Check the error log in /var/log/lomaxscale/ to see if any errors are detected in the configuration file and to confirm MaxScale has been started. Also the maxadmin command may be used to confirm that MaxScale is running and the services, listeners etc have been correctly configured.
|
||||
|
||||
```
|
||||
% maxadmin -pmariadb list services
|
||||
|
||||
Services.
|
||||
@ -349,6 +313,7 @@ CLI | maxscaled | localhost | 6603 | Running
|
||||
---------------------+--------------------+-----------------+-------+--------
|
||||
|
||||
%
|
||||
```
|
||||
|
||||
MaxScale is now ready to start accepting client connections and routing them to the master or slaves within your cluster. Other configuration options are available that can alter the criteria used for routing, these include monitoring the replication lag within the cluster and routing only to slaves that are within a predetermined delay from the current master or using weights to obtain unequal balancing operations. These options may be found in the MaxScale Configuration Guide. More detail on the use of maxadmin can be found in the document "MaxAdmin - The MaxScale Administration & Monitoring Client Application".
|
||||
MaxScale is now ready to start accepting client connections and routing them to the master or slaves within your cluster. Other configuration options are available that can alter the criteria used for routing, these include monitoring the replication lag within the cluster and routing only to slaves that are within a predetermined delay from the current master or using weights to obtain unequal balancing operations. These options may be found in the MaxScale Configuration Guide. More detail on the use of maxadmin can be found in the document [MaxAdmin - The MaxScale Administration & Monitoring Client Application](Administration-Tutorial.md).
|
||||
|
||||
|
||||
@ -70,7 +70,7 @@ If you wish to use two different usernames for the two different roles of monito
|
||||
|
||||
## Creating Your MaxScale Configuration
|
||||
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory $MAXSCALE_HOME/etc, if you have installed in the default location then this file is available in /usr/local/mariadb-maxscale/etc/MaxScale.cnf. This is not created as part of the installation process and must be manually created. A template file does exist within this directory that may be use as a basis for your configuration.
|
||||
MaxScale configuration is held in an ini file that is located in the file MaxScale.cnf in the directory /etc, if you have installed in the default location then this file is available in /usr/local/mariadb-maxscale/etc/MaxScale.cnf. This is not created as part of the installation process and must be manually created. A template file does exist within this directory that may be use as a basis for your configuration.
|
||||
|
||||
A global, maxscale, section is included within every MaxScale configuration file; this is used to set the values of various MaxScale wide parameters, perhaps the most important of these is the number of threads that MaxScale will use to execute the code that forwards requests and handles responses for clients.
|
||||
|
||||
|
||||
@ -84,7 +84,7 @@ This optional parameter allows for the administrator to define the number of the
|
||||
|
||||
### binlogdir
|
||||
|
||||
This parameter allows the location that MaxScale uses to store binlog files to be set. If this parameter is not set to a directory name then MaxScale will store the binlog files in the directory $MAXSCALE_HOME/<Service Name>.
|
||||
This parameter allows the location that MaxScale uses to store binlog files to be set. If this parameter is not set to a directory name then MaxScale will store the binlog files in the directory /var/cache/maxscale/<Service Name>.
|
||||
|
||||
### heartbeat
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ The Query Log All (QLA) filter is a filter module for MaxScale that is
|
||||
|
||||
## Configuration
|
||||
|
||||
The configuration block for the QLA filter requires the minimal filter options in it's section within the MaxScale.cnf file, stored in $MAXSCALE_HOME/etc/MaxScale.cnf.
|
||||
The configuration block for the QLA filter requires the minimal filter options in it's section within the MaxScale.cnf file, stored in /etc/MaxScale.cnf.
|
||||
```
|
||||
[MyLogFilter]
|
||||
type=filter
|
||||
|
||||
@ -5,7 +5,7 @@ This filter is designed to extract queries and transform them into a canonical f
|
||||
|
||||
## Configuration
|
||||
|
||||
The configuration block for the **mqfilter** filter requires the minimal filter options in it’s section within the MaxScale.cnf file, stored in $MAXSCALE_HOME/etc/MaxScale.cnf. Although the filter will start, it will use the default values which only work with a freshly installed RabbitMQ server and use its default values. This setup is mostly intended for testing the filter.
|
||||
The configuration block for the **mqfilter** filter requires the minimal filter options in it’s section within the MaxScale.cnf file, stored in /etc/MaxScale.cnf. Although the filter will start, it will use the default values which only work with a freshly installed RabbitMQ server and use its default values. This setup is mostly intended for testing the filter.
|
||||
|
||||
The following is an example of a mqfilter configuration in the MaxScale.cnf file used for actual logging of queries to a RabbitMQ broker on a different host.
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ The regex filter is a filter module for MaxScale that is able to rewrite query c
|
||||
|
||||
# Configuration
|
||||
|
||||
The configuration block for the Regex filter requires the minimal filter options in it’s section within the MaxScale.cnf file, stored in $MAXSCALE_HOME/etc/MaxScale.cnf.
|
||||
The configuration block for the Regex filter requires the minimal filter options in it’s section within the MaxScale.cnf file, stored in /etc/MaxScale.cnf.
|
||||
|
||||
```
|
||||
[MyRegexFilter]
|
||||
|
||||
@ -6,7 +6,7 @@ The tee filter is a filter module for MaxScale is a "plumbing" fitting in the Ma
|
||||
|
||||
# Configuration
|
||||
|
||||
The configuration block for the TEE filter requires the minimal filter parameters in it’s section within the MaxScale.cnf file, stored in $MAXSCALE_HOME/etc/MaxScale.cnf, that defines the filter to load and the service to send the duplicates to. Currently the tee filter does not support multi-statements.
|
||||
The configuration block for the TEE filter requires the minimal filter parameters in it’s section within the MaxScale.cnf file, stored in /etc/MaxScale.cnf, that defines the filter to load and the service to send the duplicates to. Currently the tee filter does not support multi-statements.
|
||||
|
||||
```
|
||||
[DataMartFilter]
|
||||
|
||||
@ -6,7 +6,7 @@ The top filter is a filter module for MaxScale that monitors every SQL statement
|
||||
|
||||
# Configuration
|
||||
|
||||
The configuration block for the TOP filter requires the minimal filter options in it’s section within the MaxScale.cnf file, stored in $MAXSCALE_HOME/etc/MaxScale.cnf.
|
||||
The configuration block for the TOP filter requires the minimal filter options in it’s section within the MaxScale.cnf file, stored in /etc/MaxScale.cnf.
|
||||
|
||||
```
|
||||
[MyLogFilter]
|
||||
|
||||
@ -3,18 +3,12 @@
|
||||
# STANDALONE - Installs to /usr/local/mariadb-maxscale
|
||||
# RPM - Installs to /usr
|
||||
# DEB - Installs to /usr
|
||||
if(${TYPE} MATCHES "STANDALONE")
|
||||
include(GNUInstallDirs)
|
||||
|
||||
set(CMAKE_INSTALL_PREFIX "/usr/local/mariadb-maxscale" CACHE PATH "Prefix prepended to install directories.")
|
||||
|
||||
# RPM and DEB are the same until differences are found
|
||||
else()
|
||||
set(CMAKE_INSTALL_PREFIX "/usr" CACHE PATH "Prefix prepended to install directories.")
|
||||
endif()
|
||||
|
||||
set(MAXSCALE_LIBDIR lib64/maxscale CACHE PATH "Library installation path")
|
||||
set(MAXSCALE_BINDIR bin CACHE PATH "Executable installation path")
|
||||
set(MAXSCALE_SHAREDIR share/maxscale CACHE PATH "Share file installation path, includes licence and readme files")
|
||||
set(MAXSCALE_DOCDIR share/doc/maxscale CACHE PATH "Documentation installation path, text versions only")
|
||||
set(MAXSCALE_CONFDIR etc CACHE PATH "Configuration file installation path, this is not usually needed")
|
||||
set(MAXSCALE_LIBDIR ${CMAKE_INSTALL_LIBDIR}/maxscale CACHE PATH "Library installation path")
|
||||
set(MAXSCALE_BINDIR ${CMAKE_INSTALL_BINDIR} CACHE PATH "Executable installation path")
|
||||
set(MAXSCALE_SHAREDIR ${CMAKE_INSTALL_DATADIR}/maxscale CACHE PATH "Share file installation path, includes licence and readme files")
|
||||
set(MAXSCALE_DOCDIR ${CMAKE_INSTALL_DOCDIR}/maxscale CACHE PATH "Documentation installation path, text versions only")
|
||||
set(MAXSCALE_CONFDIR ${CMAKE_INSTALL_SYSCONFDIR} CACHE PATH "Configuration file installation path, this is not usually needed")
|
||||
set(MAXSCALE_VARDIR /var CACHE PATH "Data file path (usually /var/)")
|
||||
|
||||
|
||||
@ -505,15 +505,9 @@ static bool resolve_maxscale_conf_fname(
|
||||
* directory.
|
||||
* '-f MaxScale.cnf'
|
||||
*/
|
||||
home_etc_dir = (char*)malloc(strlen(home_dir)+strlen("/etc")+1);
|
||||
snprintf(home_etc_dir,
|
||||
strlen(home_dir)+strlen("/etc")+1,
|
||||
"%s/etc",
|
||||
home_dir);
|
||||
*cnf_full_path = get_expanded_pathname(NULL,
|
||||
home_etc_dir,
|
||||
home_dir,
|
||||
cnf_file_arg);
|
||||
free(home_etc_dir);
|
||||
|
||||
if (*cnf_full_path != NULL)
|
||||
{
|
||||
@ -1026,11 +1020,11 @@ static void usage(void)
|
||||
" -L|--logdir=... path to log file directory\n"
|
||||
" (default: /var/log/maxscale)\n"
|
||||
" -D|--datadir=... path to data directory\n"
|
||||
" (default: /var/lib/maxscale)\n"
|
||||
" (default: /usr/lib64/maxscale)\n"
|
||||
" -C|--configdir=... path to configuration file directory\n"
|
||||
" (default: /etc/)\n"
|
||||
" -B|--libdir=... path to module directory\n"
|
||||
" (default: /var/lib/maxscale)\n"
|
||||
" -B|--libdir=... path to module directory\n"
|
||||
" (default: /usr/lib64/maxscale)\n"
|
||||
" -A|--cachedir=... path to cache directory\n"
|
||||
" (default: /var/cache/maxscale)\n"
|
||||
" -s|--syslog= log messages to syslog.\n"
|
||||
@ -1588,63 +1582,6 @@ int main(int argc, char **argv)
|
||||
sprintf(mysql_home, "%s/mysql", cachedir);
|
||||
setenv("MYSQL_HOME", mysql_home, 1);
|
||||
|
||||
/*<
|
||||
* If MaxScale home directory wasn't set by command-line argument.
|
||||
* Next, resolve it from environment variable and further on,
|
||||
* try to use default.
|
||||
*/
|
||||
/*
|
||||
|
||||
if (home_dir == NULL)
|
||||
{
|
||||
if (!resolve_maxscale_homedir(&home_dir))
|
||||
{
|
||||
ss_dassert(home_dir != NULL);
|
||||
rc = MAXSCALE_HOMELESS;
|
||||
goto return_main;
|
||||
}
|
||||
|
||||
}
|
||||
else
|
||||
{
|
||||
char* log_context = strdup("Home directory command-line argument");
|
||||
char* errstr;
|
||||
|
||||
errstr = check_dir_access(home_dir,true,true);
|
||||
|
||||
if (errstr != NULL)
|
||||
{
|
||||
char* logstr = (char*)malloc(strlen(log_context)+
|
||||
1+
|
||||
strlen(errstr)+
|
||||
1);
|
||||
|
||||
snprintf(logstr,
|
||||
strlen(log_context)+
|
||||
1+
|
||||
strlen(errstr)+1,
|
||||
"%s: %s",
|
||||
log_context,
|
||||
errstr);
|
||||
|
||||
print_log_n_stderr(true, true, logstr, logstr, 0);
|
||||
|
||||
free(errstr);
|
||||
free(logstr);
|
||||
rc = MAXSCALE_HOMELESS;
|
||||
goto return_main;
|
||||
}
|
||||
else if (!daemon_mode)
|
||||
{
|
||||
fprintf(stderr,
|
||||
"Using %s as MAXSCALE_HOME = %s\n",
|
||||
log_context,
|
||||
home_dir);
|
||||
}
|
||||
free(log_context);
|
||||
}
|
||||
*/
|
||||
|
||||
/**
|
||||
* Resolve the full pathname for configuration file and check for
|
||||
* read accessibility.
|
||||
|
||||
@ -1,5 +1,25 @@
|
||||
#ifndef _GW_HG
|
||||
#define _GW_HG
|
||||
|
||||
/*
|
||||
* This file is distributed as part of the MariaDB Corporation MaxScale. It is free
|
||||
* software: you can redistribute it and/or modify it under the terms of the
|
||||
* GNU General Public License as published by the Free Software Foundation,
|
||||
* version 2.
|
||||
*
|
||||
* This program is distributed in the hope that it will be useful, but WITHOUT
|
||||
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
||||
* FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
|
||||
* details.
|
||||
*
|
||||
* You should have received a copy of the GNU General Public License along with
|
||||
* this program; if not, write to the Free Software Foundation, Inc., 51
|
||||
* Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
||||
*
|
||||
* Copyright MariaDB Corporation Ab 2013-2014
|
||||
*/
|
||||
|
||||
|
||||
#include <stdio.h>
|
||||
#include <ctype.h>
|
||||
#include <errno.h>
|
||||
@ -19,17 +39,7 @@
|
||||
#include <netinet/in.h>
|
||||
#include <arpa/inet.h>
|
||||
#include <stdbool.h>
|
||||
|
||||
/** Default file locations */
|
||||
static const char* default_cnf_fname = "MaxScale.cnf";
|
||||
static const char* default_configdir = "/etc/";
|
||||
static const char* default_logdir = "/var/log/maxscale/";
|
||||
static const char* default_datadir = "/var/cache/maxscale/";
|
||||
static const char* default_libdir = "/lib64/maxscale/";
|
||||
static const char* default_cachedir = "/var/cache/maxscale/";
|
||||
static const char* default_langdir = "/usr/share/mysql/english/"; /*< This is where the MariaDB
|
||||
* server installs errmsg.sys */
|
||||
static const char* default_piddir = "/var/run/maxscale/";
|
||||
#include <gwdirs.h>
|
||||
|
||||
#define EXIT_FAILURE 1
|
||||
|
||||
|
||||
33
server/include/gwdirs.h.in
Normal file
33
server/include/gwdirs.h.in
Normal file
@ -0,0 +1,33 @@
|
||||
#ifndef _GW_DIRS_HG
|
||||
#define _GW_DIRS_HG
|
||||
|
||||
/*
|
||||
* This file is distributed as part of the MariaDB Corporation MaxScale. It is free
|
||||
* software: you can redistribute it and/or modify it under the terms of the
|
||||
* GNU General Public License as published by the Free Software Foundation,
|
||||
* version 2.
|
||||
*
|
||||
* This program is distributed in the hope that it will be useful, but WITHOUT
|
||||
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
||||
* FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
|
||||
* details.
|
||||
*
|
||||
* You should have received a copy of the GNU General Public License along with
|
||||
* this program; if not, write to the Free Software Foundation, Inc., 51
|
||||
* Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
||||
*
|
||||
* Copyright MariaDB Corporation Ab 2015
|
||||
*/
|
||||
|
||||
/** Default file locations, configured by CMake */
|
||||
static const char* default_cnf_fname = "MaxScale.cnf";
|
||||
static const char* default_configdir = "/etc/";
|
||||
static const char* default_piddir = "/var/run/maxscale/";
|
||||
static const char* default_logdir = "/var/log/maxscale/";
|
||||
static const char* default_datadir = "/var/cache/maxscale/";
|
||||
static const char* default_libdir = "@CMAKE_INSTALL_PREFIX@/@MAXSCALE_LIBDIR@";
|
||||
static const char* default_cachedir = "/var/cache/maxscale/";
|
||||
static const char* default_langdir = "/usr/share/mysql/english/"; /*< This is where the MariaDB
|
||||
* server installs errmsg.sys */
|
||||
|
||||
#endif
|
||||
Loading…
x
Reference in New Issue
Block a user