OpenBSD Journal

mysql got finally stable on -current

Contributed by jose on from the stable-databases dept.

Dmitry Dorofeev writes: "I have been with OpenBSD since 2.5. It was always a trick to get mysql running without crashes. Now I have OpenBSD 3.0 becouse it is the latest which can run mysql smoothly (with custom pth port from 2.9). The problem was always somewhere in the OpenBSD threads library. At some point Marco S Hyman started his hacks on threads. OpenBSD 3.3 was much better, but still not perfect. And finally at Apr 30 2003 it all got fixed. uthread_sig.c Are patches available for 3.3-stable? Anyway, I just cvsuped /src/lib/libpthread on top of my 3.3-release recompiled libpthread, relinked mysql (from ports) and IT IS WORKING WITHOUT CRASHES !!!. Thanks to all who made it reality. Gotta buy some T-shirts and posters." Hey, always good to see a satisfied customer. I should see what else was fixed by the recent threading fixups ...

(Comments are closed)

Comments

  1. By Brad () brad at comstyle dot com on mailto:brad at comstyle dot com

    Try checking uthread_sig.c which you pointed to
    and you would notice that the -stable branch has
    this fixed already. There is also a fix for uthread_kill.c too.

    Comments

    1. By Anonymous Coward () on

      I work with -current and I've got this all the time

      pid 29854: Fatal error '_pq_first: pq_active' at line 219 in file
      /usr/src/lib/libpthread/uthread/uthread_priority_queue.c (errno = 35)
      Abort
      030523 13:32:10 mysqld restarted
      /usr/local/libexec/mysqld: ready for connections

  2. By djm () on

    Weird, I have been running a (lightly loaded) MySQL on OpenBSD since 2.9 and have never seen crashes.

    Comments

    1. By Brad () brad at comstyle.com dot com on mailto:brad at comstyle.com dot com

      Well I'm the maintainer of the MySQL port but I can admit that a lot of the weird problems only tend to happen when under a somewhat heavy load. Light loads don't tend to trigger the bugs in the pthreads library when using MySQL. The bugs situation is much better on i386 but a lot of the other archs are not so good.

    2. By Mike () on

      Comments

    3. By Anonymous Coward () on

      Sorry, but I have to chime in with a "metoo". I've had a MySQL-powered web site up since at least 2.9, with no crashes.

      If the problems are load-related, this would explain a lot of things. My server gets loaded up only at peak times -- it's never constantly loaded.

  3. By ViPER () viper@dmrt.net on http://www.dmrt.net

    Are you for real ? What did you had to do with it to make it crash ? I'm a bit confused here since i'm running around 3 70k hits a day php/backend sql sites wich isn't offcourse an `enterprised` env. by far but i'm speaking the truth when i say mysqld never EVER let me down from bsd 2.9 till today 3.3 and since i'm trying to keep it that way can you please enlighten me what made it unstable at your env. ?
    --
    Fixes a pthread issue noticed by several users reports regarding mysql crashing unexpectedly.
    --
    In short, what triggerd the issue ?

  4. By Chris Humphries () on

    learn a real db, like postgresql, all you lazy bastids ;)

    mysql is basically SQL syntax to dbm. it is sad that people confuse it with a real database and think they are doing something really cool.

  5. By Joseph Garcia () bsd_usr@yahoo.com on mailto:bsd_usr@yahoo.com

    MySQL might be fast and have a whole lot of support, but PostgreSQL does have all the features and it holds a license that even Theo would approve of. I'm thinking that the BSD community as a whole should embrace PostgreSQL, support it, and promote it on BSD platforms. But, that's my opinion and I just wanted to share it.

    Comments

    1. By Brad () brad at comstyle.com dot com on mailto:brad at comstyle.com dot com

      Re-read the license, Theo would not approve of it.

      Comments

      1. By Joseph Garcia () bsd_usr@yahoo.com on mailto:bsd_usr@yahoo.com

        From http://www.postgresql.org/licence.html:

        PostgreSQL is released under the BSD licence.

        PostgreSQL Database Management System
        (formerly known as Postgres, then as Postgres95)

        Portions Copyright (c) 1996-2002, The PostgreSQL Global Development Group

        Portions Copyright (c) 1994, The Regents of the University of California

        Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.

        IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

        THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.


        That's not acceptable?

        Comments

        1. By Brent Graveland () brent@graveland.net on brent.graveland.net

          This part:
          > documentation for any purpose, without fee,
          > and without a written agreement

          The "without fee" part is similar to the ntp license that Theo just recently commented on. It basically says that you cannot charge for it - the intent quite likely was correct, but the wording is ambiguous.

          Close, but not quite close enough. Oh well, I'll still use it :) It kicks MySQL's virtual ass.

          Comments

          1. By Anonymous Coward () on

            I parsed that as saying that you don't need to pay a fee to distribute it...

            Comments

            1. By vincent- () on

              that's why it's wrong, it's ambiguous, something you do not want in legal stuff...

              Comments

    2. By Anonymous Coward () on

      But it has such a stupid name...

      We should only promote packages with cool names.

      How about "MatriXQL"? It uses the new "XQL" standard query language, which includes the "DWIM" keyowrd that always returns the set you really wanted.

      Comments

      1. By Anonymous Coward () on

        FFS XML (XQL query) is NOT the answer to everything. It's a poor answer to most things

  6. By tony () tony@libpcap.net on http://libpcap.net

    I just cvs'd the latest stable branch.. now that I have rebuilt my whole system, do I have to rebuild/reinstall the mysql port too?

    Comments

    1. By Bruno Rohée () bruno@rohee.com on mailto:bruno@rohee.com

      That's what dynamic linking is for, your compiled mysql will use the patched library automatically, the major number didn't change as there was no API change.

      Comments

      1. By tony () tony@libpcap.net on http://libpcap.net

        Awesome, thanks for the re-assurence :)

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]