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

Maxscale fail to initiate maxscale.service (Missing /var/run/maxscale) directory

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 23.08.4
    • 23.08.5
    • Packaging
    • None

    Description

      Maxscale installation is fine.

       
      Created symlink from /etc/systemd/system/multi-user.target.wants/maxscale.service to /usr/lib/systemd/system/maxscale.service.
      
      

       
      [root@repl-maxscale maxscale]# stat /lib/systemd/system/maxscale.service
        File: ‘/lib/systemd/system/maxscale.service’
        Size: 663             Blocks: 8          IO Block: 4096   regular file
      Device: fd00h/64768d    Inode: 51064361    Links: 1
      Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
      Context: unconfined_u:object_r:systemd_unit_file_t:s0
      Access: 2024-02-27 03:45:29.030347816 -0500
      Modify: 2024-02-27 03:45:28.974347832 -0500
      Change: 2024-02-27 03:45:28.974347832 -0500
       Birth: -
      
      

       
      [root@repl-maxscale maxscale]# cat /lib/systemd/system/maxscale.service
      [Unit]
      Description=MariaDB MaxScale Database Proxy
      After=network.target
       
      [Service]
      Type=forking
      Restart=on-abort
       
       
       
       
      # Make sure /var/run/maxscale exists
      ExecStartPre=+/usr/bin/install -d /var/run/maxscale -o maxscale -g maxscale
      ExecStartPre=+/usr/bin/install -d /var/lib/maxscale -o maxscale -g maxscale
       
      PIDFile=/var/run/maxscale/maxscale.pid
       
      # Use the default user and group
      User=maxscale
      Group=maxscale
       
      ExecStart=/usr/bin/maxscale
      TimeoutStartSec=120
      LimitNOFILE=65535
      StartLimitBurst=0
      WatchdogSec=60s
      NotifyAccess=all
       
      # MaxScale should be restarted if it exits with 75 (BSD's EX_TEMPFAIL)
      RestartForceExitStatus=75
      
      

       
      [root@repl-maxscale maxscale]# stat /var/run/maxscale/maxscale.pid
        File: ‘/var/run/maxscale/maxscale.pid’
        Size: 4               Blocks: 8          IO Block: 4096   regular file
      Device: 14h/20d Inode: 76958       Links: 1
      Access: (0755/-rwxr-xr-x)  Uid: (  996/maxscale)   Gid: (  994/maxscale)
      Context: system_u:object_r:var_run_t:s0
      Access: 2024-02-27 03:46:49.912323884 -0500
      Modify: 2024-02-27 03:46:40.862326561 -0500
      Change: 2024-02-27 03:46:40.862326561 -0500
       Birth: -
      
      

      Upon reboot , Maxscale fail to initiate the maxscale.service leading to failure of /var/run/maxscale directory creation.

      ExecStartPre: Commands to run before the main service starts. Here, it creates directories /var/run/maxscale and /var/lib/maxscale with specific ownership.

      [root@repl-maxscale run]# maxscale --version
      MaxScale 23.08.4
      

      Error log :-

      MariaDB MaxScale  /var/log/maxscale/maxscale.log  Tue Feb 27 03:48:34 2024
      ----------------------------------------------------------------------------
      2024-02-27 03:48:34   notice : Module 'galeramon' loaded from '/usr/lib64/maxscale/libgaleramon.so'.
      2024-02-27 03:48:34   notice : Module 'readwritesplit' loaded from '/usr/lib64/maxscale/libreadwritesplit.so'.
      2024-02-27 03:48:34   notice : The logging of info messages has been enabled.
      2024-02-27 03:48:34   notice : Using up to 272.87MiB of memory for query classifier cache
      2024-02-27 03:48:34   notice : syslog logging is disabled.
      2024-02-27 03:48:34   notice : maxlog logging is enabled.
      2024-02-27 03:48:34   alert  : Can't access '/var/run/maxscale'.: No such file or directory
      2024-02-27 03:48:34   MariaDB MaxScale is shut down.
      ----------------------------------------------------
      
      

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              pramod.mahto@mariadb.com Pramod Mahto
              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.