[chaos]

Hi

I'm having problems with MySQL dying on OpenBSD 3.5. I have installed MySQL from ports.

From log:
---
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=13
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

040418 08:29:24 mysqld restarted
040418 8:29:25 InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
...
---

Hope that someone can help me with this.

[elmore]

I'm working on getting a couple of 3.5 boxes ready Chaos, I'll post back when I have them up and running ith mysql

[chaos]

I'm working on getting a couple of 3.5 boxes ready Chaos, I'll post back when I have them up and running ith mysql
OK, let me know if you have any problems.

Maybe my problem was caused by installing some stuff from CPAN. This may or may not have caused other packages to be updated.

make clean in ports and then recompiling MySQL from ports seams to have solved the isue.

[soup4you2]

is 3.5 released now? or is it still in beta?

[chaos]

OpenBSD 3.5 isn't officially released yet but it is tagged in CVS. The time from tagging to release is spend on building an release and compiling various ports.

So you can cvs up to 3.5 (or any other version) and build your own release when it is tagged in CVS.

[soup4you2]

ok thanks... thought i missed a anouncement there... :P

[chaos]

I'm still having problems with MySQL on OpenBSD 3.5. Sometimes it crashes. Anyone else having problems with this?

From log
---
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=10
max_connections=100
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

040429 14:11:35 mysqld restarted
040429 14:11:35 InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
---

[elmore]

Chaos-

This box is running 3.5 -Stable with mysql built out of the 3.5 -Stable ports tree. We had no issues on install and it seems to be running quite well atm.

Don't know when the last time you did a make realease was or when you last cvs'd your ports tree but we did ours on Friday and built everything from there. So far so good.

If you installed from a snapshot I know that they were broken the other day which might be one reason for the instability? How are are you starting mysql up? I use the mysql.server script in /usr/local/share/mysql

[chaos]

It is a while ago i upgraded a 3.4 box to 3.5 by building everyting from source. I then build my own release and installed this on the box I'm running MySQL on now.

I start MySQL with /usr/local/bin/mysqld_safe --bind-address=127.0.0.1

Maybe it has something to do with the way I start MySQL.

[elmore]

I'd definately try use use the mysql.server script the port provides. I haven't had any problems at all thus far with it.