Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MySQL 4.0.18 server problem on FreeBSD 5.2-Current

0 views
Skip to first unread message

Ganbold

unread,
Mar 23, 2004, 7:27:50 AM3/23/04
to
Hi,

Today I wanted to upgrade mysql-4.0.17 to mysql-4.0.18 in FreeBSD-5.2-CURRENT.
I used following options to compile from ports collection:

make WITH_CHARSET=cp1251 WITH_LINUXTHREADS=yes BUILD_STATIC=yes install

However when I tried to run mysql server log says:
------------------------------------------------
...
040323 19:52:50 mysqld restarted
040323 19:52:50 InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
Version: '4.0.18-log' socket: '/tmp/mysql.sock' port: 3306
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=402653184
read_buffer_size=2093056
max_used_connections=0
max_connections=1000
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
290904 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Number of processes running now: 0
040323 19:52:54 mysqld restarted
040323 19:52:55 InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
Version: '4.0.18-log' socket: '/tmp/mysql.sock' port: 3306
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.
...
---------------------------------------------------------------
I tried with linuxthreads-2.2.3_15 and linuxthreads-2.2.3_13 but mysql
server says same error.
I even tried to build without linuxthreads but it says same error.
I even tried to downgrade mysql server to 4.0.17 but same error.

FreeBSD was updated on March 3 2004. I tried when it was update on March 3,
same problem.
Then I updated FreeBSD server using cvsup and the tried to install and run
mysql. Same problem.

Before mysql update was really easy, but now I have big problem.
What should do in this case? Is there anybody solved this problem before?

tia,

Ganbold

_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

Alex Dupre

unread,
Mar 23, 2004, 8:41:52 AM3/23/04
to
Ganbold wrote:

> Before mysql update was really easy, but now I have big problem.
> What should do in this case? Is there anybody solved this problem before?

You should read the mailing lists before posting on them...btw, it seems
to be a problem with CPUTYPE not set in /etc/make.conf.....currently it
is known to work with CPUTYPE=p3 and to not work without
CPUTYPE....otherwise you can remove --with-libwrap from your Makefile
and loose the tcpwrapper support.

--
Alex Dupre

Daniel Eischen

unread,
Mar 23, 2004, 10:59:56 AM3/23/04
to
On Tue, 23 Mar 2004, Alex Dupre wrote:

> Ganbold wrote:
>
> > Before mysql update was really easy, but now I have big problem.
> > What should do in this case? Is there anybody solved this problem before?
>
> You should read the mailing lists before posting on them...btw, it seems
> to be a problem with CPUTYPE not set in /etc/make.conf.....currently it
> is known to work with CPUTYPE=p3 and to not work without
> CPUTYPE....otherwise you can remove --with-libwrap from your Makefile

I don't set CPUTYPE and it works just fine. The only flags
I have are CFLAGS=-O -pipe.

> and loose the tcpwrapper support.

ldd on my mysqld shows that libwrap is referenced (first entry
shown when displayed).

--
Dan Eischen

Alex Dupre

unread,
Mar 23, 2004, 11:29:15 AM3/23/04
to
Daniel Eischen wrote:

> I don't set CPUTYPE and it works just fine. The only flags
> I have are CFLAGS=-O -pipe.

Strange...are you sure *tcp* connections work? I personally tested with
p3 and p4 (work) and without cputype (not work).

--
Alex Dupre

Daniel Eischen

unread,
Mar 23, 2004, 12:07:57 PM3/23/04
to
On Tue, 23 Mar 2004, Alex Dupre wrote:

> Daniel Eischen wrote:
>
> > I don't set CPUTYPE and it works just fine. The only flags
> > I have are CFLAGS=-O -pipe.
>
> Strange...are you sure *tcp* connections work? I personally tested with
> p3 and p4 (work) and without cputype (not work).

Does the perl script I sent you utilize tcp connections? If so,
then yes they work. I was running the script on the same system
as the server.

--
Dan Eischen

Alex Dupre

unread,
Mar 23, 2004, 12:35:27 PM3/23/04
to
Daniel Eischen wrote:

> Does the perl script I sent you utilize tcp connections? If so,
> then yes they work. I was running the script on the same system
> as the server.

In fact it doesn't use tcp connections. That script use the local socket
connections. To test remote tcp connections you have to create a new
mysql user that can connect from any host and then use "mysql -h <ip>"
to connect (even on the same system, but using the real ip).
So I'm quite sure it'll not work for you.

--
Alex Dupre

Ganbold

unread,
Mar 23, 2004, 9:16:38 PM3/23/04
to
Hi,

Thanks for the reply.

While I was waiting for the email from mailing lists, I downloaded latest
snapshot mysql-4.0.19-nightly-20040323.tar.gz from Mysql.com web site and
installed with following options:

CFLAGS="-DHAVE_BROKEN_REALPATH -D__USE_UNIX98 -D_REENTRANT -D_THREAD_SAFE
-I/usr/local/include/pthread/linuxthreads"
CXXFLAGS="-DHAVE_BROKEN_REALPATH -D__USE_UNIX98 -D_REENTRANT -D_THREAD_SAFE
-I/usr/local/include/pthread/linuxthreads"

./configure --prefix=/usr/local --localstatedir=/var/db/mysql
--libexecdir=/usr/local/libexec --enable-thread-safe-client
--enable-local-infile --enable-assembler
--with-named-thread-libs="-DHAVE_GLIBC2_STYLE_GETHOSTBYNAME_R
-D_THREAD_SAFE -I /usr/local/include/pthread/linuxthreads -L/usr/local/lib
-llthread -llgcc_r" --disable-shared --with-embedded-server --with-innodb
make
make install

I didn't change anything in /etc/make.conf.
Now it works just fine. Tcp connections work fine too.

Another thing is I installed Mysql-4.0.18 from ports in another
FreeBSD-5.2-CURRENT machine without any problem.
I didn't add CPUTYPE in /etc/make.conf there either and it works fine. I
will try to make tcp connections there and let you know
the results.

regards,


Ganbold

Ganbold

unread,
Mar 23, 2004, 9:59:06 PM3/23/04
to
Hi,

It seems like tcp connections is not working in another machine with
mysql-4.0.18.
I will add CPUTYPE=p4 in /etc/make.conf and install it and test it.
I will let you know the results.

Ganbold

unread,
Mar 23, 2004, 11:28:40 PM3/23/04
to
Hi Alex,

I tested mysql-4.0.18 server from ports with CPUTYPE=p4 options in
/etc/make.conf.
I works fine, even tcp connections work fine.
I will wait when comes out mysql-4.0.19 and leave another server with
latest snapshot of mysql.
Thank you for your great help.

0 new messages