[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-sparc
Subject:    Re: MySQL 4.0.17/8 on OpenBSD 3.4 SPARC64
From:       tonyb () vegan ! net
Date:       2004-05-26 4:40:28
Message-ID: Pine.LNX.4.58.0405221109060.884 () automator ! vegan ! net
[Download RAW message or body]

Hi All,

I've found a resolution to this issue.  Thanks to Sean, who on a Slashdot
post mentioned seeing something about an issue on OpenBSD 2.8 in the MySQL
Manual.  I found it here:

http://dev.mysql.com/doc/mysql/en/OpenBSD_2.8.html

His slashdot reponse was in response to an article I did on OSNews
evaluating OpenBSD SPARC64 that found it's way into the BSD section.

The MySQL entry appears to deal with two separate issues; one dealing with
threading on 2.8, and one dealing with OpenBSD in general (at least with
3.4 and 3.5 on SPARC64, probably other versions and platforms as well),
which was the issue I was seeing.

It turns out it was a file discriptor problem, only I was trying to change
it with sysctl, when the --open-files-limit option is what ended up being
the resolution.

I've since been able to run MySQL with no problems.  I've also run
benchmarks for 3.4, 3.5, and 3.5's new MySQL 4.0.18 package (3.4 didn't
have a 4.0.x package or port).  The 3.5 MySQL 4.0.18 package seems to
already include the open files limit option by default.

Those benchmarks are available in an article just published on OSNews.com:

http://www.osnews.com/story.php?news_id=7152

Thanks to everyone, especially Sean, that helped find a resoltion.

Cheers,

Tony



On Sat, 10 Apr 2004 tonyb@vegan.net wrote:

> > Error code   9:  Bad file descriptor - so you might need to increase your file
> > descriptors even more, I've seen them over 32,000 for some things.
>
> > It might not be that directory thats the problem, it my just be having a
> > problem allocating temp space. If the error code doesn't explain enough you
> > could try launching the mysqld daemon with --tempdir=path with path being a
> > volume that the mysql user can read/write too that has a lot of free space.
> > > or this:
>
> OK, I tried those suggestions, still no dice.
>
> I put tmpdir on a partition with 5 GB free, where mysql had full
> read/write to the directory.  I kicked up maxfiles to 32,000:
>
> sysctl -w kern.maxfiles=32000
>
> Also of interesting note, I compiled PostgreSQL 7.4.2 from source, and ran
> sql-bench against that (sql-bench can run against MySQL, Postgres, mSQL,
> and Solid Server)
>
> Most of the tests died with:
>
> Bus error (core dumped)
>
> Next, I'm going to try a ports-compiled PostgreSQL.
>
> Tony

[prev in list] [next in list] [prev in thread] [next in thread]