[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] MYSQL Problem on 550
- Subject: Re: [cobalt-developers] MYSQL Problem on 550
- From: Anders <andersb@xxxxxxxxxxx>
- Date: Tue May 20 03:05:00 2003
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
jonchiew wrote:
> Ok I think I made a mistake on my previous mail. The mysqld-max, was
> normal. I think the problem happened after patching with the security
> patch. I saw the log - and it instructed me to disable the innodb using
> the my.cnf (my database format is ISAM and I dun think I want to
> convert)....but I counldn't find the %#@& my.cnf :'{ can anyone tell me
> what can I do to solve this...
Looks like you applied the latest and greatest glibc upgrade ?
Unfortunately, out of the box it breaks MySQL 3 functionality...
Read more here:
http://cobalt-forum.sun.com/forum/index.php?t=msg&th=1306
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75128
It's a bug with domain name resolving and small stack space...
Either a) remove dns lookups, or b) increase the thread stack ?
http://cobalt-knowledge.sun.com/cgi-bin/kbase.cfg/php/enduser/std_adp.php?
p_refno=030428-000000 (adding --skip-name-resolve to mysql startup script)
/etc/my.cnf:
set-variable = thread_stack=256k
--anders
> -----Original Message-----
> From: cobalt-developers-admin@xxxxxxxxxxxxxxx
> Sent: Tuesday, May 20, 2003 2:50 PM
> To: cobalt-developers@xxxxxxxxxxxxxxx
> Subject: [cobalt-developers] MYSQL Problem on 550
>
> Hi all,
>
> One of my staff just patched my 550 with the latest patch from:
>
> http://sunsolve.sun.com/pub-cgi/show.pl?target=cobalt/raq550.eng&nav=pat
> chpage
>
> After doing so - think my MYSQL was somehow upgraded (there is this
> "-max" thingy appearing)...everything was fine until I get some msg that
> will appear...once a while(every 10-15mins)! Anyone out there ever
> encounter this?