Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3349

maxscale does not consider log location

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 2.5.6
    • N/A
    • Core
    • None
    • Linux, Debian 10, n.a.

    Description

      MaxScale does not consider my options and want to write/create into /var/log/maxscale:

      maxscale --nodaemon --config=/home/mysql/etc/maxscale_load_split.cnf --log=stdout --libdir=${BASEDIR}/lib/x86_64-linux-gnu/maxscale --persistdir=/home/mysql/tmp --datadir=/home/mysql/tmp --logdir=/home/mysql/log/maxscale_load_split.log --config-check
      alert  : Cannot create log directory '/var/log/maxscale': Permission denied.
      alert  : Can't access '/home/mysql/log/maxscale_load_split.log/'.
      

      Attachments

        Activity

          johan.wikman Johan Wikman added a comment -

          The primary problem is logdir=/home/mysql/log/maxscale_load_split.log because the argument to --logdir should be an existing directory and not the name of a file.

          The log directory is set immediately when the flag is encountered and as --config-check has not been seen at that point, MaxScale will attempt to log it to the default log, which is that /var/log/maxscale and fail.

          You can fix the problem by

          • Putting --config-check first, in which case MaxScale will just complain about that non-existent /home/mysql/log/maxscale_load_split.log, or
          • provide an existing directory as argument to --logdir in which case there will be nothing to complain about the arguments themselves.
          johan.wikman Johan Wikman added a comment - The primary problem is logdir=/home/mysql/log/maxscale_load_split.log because the argument to --logdir should be an existing directory and not the name of a file. The log directory is set immediately when the flag is encountered and as --config-check has not been seen at that point, MaxScale will attempt to log it to the default log, which is that /var/log/maxscale and fail. You can fix the problem by Putting --config-check first, in which case MaxScale will just complain about that non-existent /home/mysql/log/maxscale_load_split.log , or provide an existing directory as argument to --logdir in which case there will be nothing to complain about the arguments themselves.

          People

            johan.wikman Johan Wikman
            oli Oli Sennhauser
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.