Why is mariadb.service failed to reload?

Discussion in 'Installation/Configuration' started by pecka33, Nov 2, 2023.

  1. pecka33

    pecka33 Member

    Hello

    i have a problem. Everthing what i need is working fine, databases etc. But in case i use command systemctl reload mariadb a get error
    Failed to reload mariadb.service: Job type reload is not applicable for unit mariadb.service.
    but can not found why. Mariadb services is working fine, stop and start working too,
    Code:
    root@:~# systemctl list-units --failed
      UNIT LOAD ACTIVE SUB DESCRIPTION
    0 loaded units listed.
    
    fine. Mariadb status is fine too

    Code:
    root@samantos:~# systemctl status mariadb
    ● mariadb.service - MariaDB 10.11.4 database server
         Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
        Drop-In: /etc/systemd/system/mysql.service.d
                 └─limits.conf
         Active: active (running) since Thu 2023-11-02 11:39:07 CET; 22s ago
           Docs: man:mariadbd(8)
                 https://mariadb.com/kb/en/library/systemd/
        Process: 1374602 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
        Process: 1374618 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
        Process: 1374620 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl>
        Process: 1374757 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
        Process: 1374759 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
       Main PID: 1374679 (mariadbd)
         Status: "Taking your SQL requests now..."
          Tasks: 31 (limit: 38398)
         Memory: 252.7M
            CPU: 3.015s
         CGroup: /system.slice/mariadb.service
                 └─1374679 /usr/sbin/mariadbd
    
    Nov 02 11:39:06 samantos mariadbd[1374679]: 2023-11-02 11:39:06 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
    Nov 02 11:39:06 samantos mariadbd[1374679]: 2023-11-02 11:39:06 0 [Note] InnoDB: log sequence number 43400965301; transaction id 22395263
    Nov 02 11:39:06 samantos mariadbd[1374679]: 2023-11-02 11:39:06 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
    Nov 02 11:39:06 samantos mariadbd[1374679]: 2023-11-02 11:39:06 0 [Note] Plugin 'FEEDBACK' is disabled.
    Nov 02 11:39:06 samantos mariadbd[1374679]: 2023-11-02 11:39:06 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
    Nov 02 11:39:06 samantos mariadbd[1374679]: 2023-11-02 11:39:06 0 [Note] Server socket created on IP: '127.0.0.1'.
    Nov 02 11:39:07 samantos mariadbd[1374679]: 2023-11-02 11:39:07 0 [Note] InnoDB: Buffer pool(s) load completed at 231102 11:39:07
    Nov 02 11:39:07 samantos mariadbd[1374679]: 2023-11-02 11:39:07 0 [Note] /usr/sbin/mariadbd: ready for connections.
    Nov 02 11:39:07 samantos mariadbd[1374679]: Version: '10.11.4-MariaDB-1~deb12u1'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 12
    Nov 02 11:39:07 samantos systemd[1]: Started mariadb.service - MariaDB 10.11.4 database server.
    
    Have anybody idea why?
     
  2. faille

    faille New Member

    You can restart the MariaDB service instead of reloading it. Restarting the service will cause it to reload its configuration files and restart all of its processes.
     
  3. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    It says
    It means reload is not supported operation for mariadb in systemctl. You need to read the docs to find out why this is the case.
     
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Like the message says, reloading is not supported for mariadb. You can restart it:
    Code:
    systemctl restart mariadb
     

Share This Page