Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • None
    • N/A
    • N/A
    • None
    • Debian 9.3
      mariaDB 10.1.41 -> 10.1.48 -> 10.6.5

    Description

      i has ok update to 10.6.5, db works ok, but –

      i got next message when reload nginx –

      Failed to get properties: Unit name mariadb-extra@.socket is missing the instance name.
      Failed to get properties: Unit name mariadb@.socket is missing the instance name.
      

      what?? why?? what to do???

      process upgrade log says –

      Installing new version of config file /etc/mysql/mariadb.conf.d/50-server.cnf ...
      mariadb-extra.socket is a disabled or a static unit, not starting it.
      mariadb-extra.socket is a disabled or a static unit, not starting it.
      Setting up mariadb-server (1:10.6.5+maria~stretch) ...
      

      so what to do with that weird message??
      and why i got that??

      Attachments

        Issue Links

          Activity

            221V Taras added a comment -

            so what to do ?

            221V Taras added a comment - so what to do ?
            danblack Daniel Black added a comment -

            illuusio, systemd stop nginx is meant to be systemctl stop nginx.

            Note how systemctl start mariadb.service above didn't output any "Failed to get properties:" messages.

            so what to do ?

            Stop using service, use systemctl.

            danblack Daniel Black added a comment - illuusio , systemd stop nginx is meant to be systemctl stop nginx . Note how systemctl start mariadb.service above didn't output any "Failed to get properties:" messages. so what to do ? Stop using service , use systemctl .

            As danblack said start using systemctl start nginx not service nginx start and as you see MariaDB is running and I assume NGinX (It's only warning) also but as said start using systemctl to get rid of warning.

            illuusio Tuukka Pasanen added a comment - As danblack said start using systemctl start nginx not service nginx start and as you see MariaDB is running and I assume NGinX (It's only warning) also but as said start using systemctl to get rid of warning.
            221V Taras added a comment -

            root@server1 ~ # systemctl stop mariadb.service
            root@server1 ~ # systemctl stop nginx
            root@server1 ~ # systemctl start mariadb.service
            root@server1 ~ # systemctl start nginx
            

            hmm.. really! wow!
            thank you!)))))

            221V Taras added a comment - root@server1 ~ # systemctl stop mariadb.service root@server1 ~ # systemctl stop nginx root@server1 ~ # systemctl start mariadb.service root@server1 ~ # systemctl start nginx hmm.. really! wow! thank you!)))))
            danblack Daniel Black added a comment -

            Closing "Not a bug", but really its "not our bug", as its in the service implementation of Debian.

            danblack Daniel Black added a comment - Closing "Not a bug", but really its "not our bug", as its in the service implementation of Debian.

            People

              illuusio Tuukka Pasanen
              221V Taras
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.