Discover Centmin Mod today
Register Now

MariaDB MariaDB 10.1.18 now available

Discussion in 'MariaDB & General MySQL news & discussions' started by eva2000, Oct 1, 2016.

  1. eva2000

    eva2000 Administrator Staff Member

    54,647
    12,230
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,799
    Local Time:
    2:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.18. This is a Stable (GA) release. See the release notes and changelog for details. Download MariaDB 10.1.18 Release Notes Changelog What is MariaDB 10.1? MariaDB APT and YUM Repository Configuration Generator Thanks, and enjoy MariaDB!

    The post MariaDB 10.1.18 now available appeared first on MariaDB.org.


    Continue reading...
     
    Last edited: Oct 1, 2016
  2. rdan

    rdan Well-Known Member

    5,446
    1,408
    113
    May 25, 2014
    Ratings:
    +2,201
    Local Time:
    12:17 PM
    Mainline
    10.2
    Upgraded fine :).
     
  3. Revenge

    Revenge Active Member

    469
    93
    28
    Feb 21, 2016
    Portugal
    Ratings:
    +354
    Local Time:
    4:17 AM
    1.9.x
    10.1.x
    This is not common but today MariaDB restarted in my server.
    I only noticed because i received an email from Newrelic saying errors increased for a minute.

    In the logs i only have this:
    Code:
    Oct 11 13:11:36 systemd[1]: mariadb.service: main process exited, code=killed, status=9/KILL
    Oct 11 13:11:36 systemd[1]: Unit mariadb.service entered failed state.
    Oct 11 13:11:36 systemd[1]: mariadb.service failed.
    Oct 11 13:11:41 systemd[1]: mariadb.service holdoff time over, scheduling restart.
    Oct 11 13:11:41 systemd[1]: Starting MariaDB database server...
    Is there any place where we can check a more detailed reason of why MariaDB process failed?
     
  4. eva2000

    eva2000 Administrator Staff Member

    54,647
    12,230
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,799
    Local Time:
    2:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    maybe
    Code (Text):
    journalctl -u mariadb --no-pager
    journalctl -xn --no-pager
    systemctl -l status maridb.service
    

    also ensure mysql socket path set in my.cnf and check error log for invalid my.cnf options OR memory buffer allocation too high OR server crash as systemd file for mariadb has restart setting i.e. /usr/lib/systemd/system/mariadb.service holdoff time = 5s wait
    Code (Text):
    # Restart crashed server only, on-failure would also restart, for example, when
    # my.cnf contains unknown option
    Restart=on-abort
    RestartSec=5s


    check usual stuff like disk free space etc
     
  5. Xon

    Xon Active Member

    173
    61
    28
    Nov 16, 2015
    Ratings:
    +229
    Local Time:
    12:17 PM
    1.15.x
    MariaDB 10.3.x
  6. eva2000

    eva2000 Administrator Staff Member

    54,647
    12,230
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,799
    Local Time:
    2:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    sweet good to know :D
     
  7. Xon

    Xon Active Member

    173
    61
    28
    Nov 16, 2015
    Ratings:
    +229
    Local Time:
    12:17 PM
    1.15.x
    MariaDB 10.3.x
    When I turned MariaDB's deadlock logging on, this caused a 700mb log file to be generated in a week :p
     
  8. eva2000

    eva2000 Administrator Staff Member

    54,647
    12,230
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,799
    Local Time:
    2:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    guess that would be relatively small for the size of your forums and mysql activity ? :)
     
  9. Xon

    Xon Active Member

    173
    61
    28
    Nov 16, 2015
    Ratings:
    +229
    Local Time:
    12:17 PM
    1.15.x
    MariaDB 10.3.x
    Oh, relative to the total volume of alerts it was tiny. It was still a lot of deadlocks. Each deadlock description was ~2kb of text (it included both queries plus indexes, and stats for both queries).

    And over two weeks, not 1 week. Miss-remembered.
     
  10. Xon

    Xon Active Member

    173
    61
    28
    Nov 16, 2015
    Ratings:
    +229
    Local Time:
    12:17 PM
    1.15.x
    MariaDB 10.3.x
    I've had a Mariadb 10.1.18 server (in a 3 node galera cluster) just die with no logs, and instantly dies with no error messages when you try to start it. Twice so far.

    Since I was in a rush, I just blew it away and re-seeded.

    Weirdly it is just 1 server out of 3, and the other two where originally cloned of the 1 server which is having issues. :confused: But the HA worked!
     
  11. eva2000

    eva2000 Administrator Staff Member

    54,647
    12,230
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,799
    Local Time:
    2:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    you mean linode clone server feature cloned ?
     
  12. Xon

    Xon Active Member

    173
    61
    28
    Nov 16, 2015
    Ratings:
    +229
    Local Time:
    12:17 PM
    1.15.x
    MariaDB 10.3.x
    I used the snapshot feature on the source server, and then used the option to deploy a snapshot to a new linode VM.

    Since I bootstrapped the cluster from the first node it didn't matter if the db was inconsistent on the cloned servers.
     
  13. eva2000

    eva2000 Administrator Staff Member

    54,647
    12,230
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,799
    Local Time:
    2:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    interesting then that it's only the 2 copies that have issues.
     
    Last edited: Oct 21, 2016
  14. dorobo

    dorobo Active Member

    420
    104
    43
    Jun 6, 2014
    Ratings:
    +162
    Local Time:
    12:17 PM
    latest
    latest
  15. eva2000

    eva2000 Administrator Staff Member

    54,647
    12,230
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,799
    Local Time:
    2:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+