Mysql Startup Problem Re: [PLUG] (no subject)

[Robby Russell]

Thanks, that did the trick..
Ok, I did a:
...su mysql
mysql]$ safe_mysqld --pid-file=/var/lib/mysql/mysql.pd &
[1] 4458
[mysql at dns mysql]$ Starting mysqld daemon with databases from /var/lib/mysql

working fine now.
still curious as to what caused this..and how to get mysql to start up at
boot time instead of it attempting to and not actually starting


<?echo Matt King managed to take the time to type out the following:
> Who owns the directory /var/lib/mysql?
> You are starting it as root and even root may not have write access to
> that directory.
>
> --
> Matt King
> magnet | internet
> http://www.magnetinternet.com
>
>  Robby Russell busted out the keyboard and typed:
>> When I try to do the following, I get the following:
>>
>> [matchboy at dns root]$ safe_mysqld --pid-file=/var/lib/mysql/mysql.pid &
>> [1] 4155
>> [matchboy at dns root]$ Starting mysqld daemon with databases from
>> /var/lib/mysql
>> /usr/bin/safe_mysqld: line 229:
>> /var/lib/mysql/dns.robbyrussell.com.err: Permission denied
>> /usr/bin/safe_mysqld: line 235:
>> /var/lib/mysql/dns.robbyrussell.com.err: Permission denied
>> tee: /var/lib/mysql/dns.robbyrussell.com.err: Permission denied
>> 021112 07:45:18  mysqld ended
>> tee: /var/lib/mysql/dns.robbyrussell.com.err: Permission denied
>>
>>
>> <?echo Robby Russell managed to take the time to type out the
>> following:
>>> I'm trying to start up mysql...and keep running into this problem.
>>> any thoughts?
>>>
>>> 021112 07:20:39  mysqld started
>>> 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 agaist 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
>>> record_buffer=131072
>>> sort_buffer=2097144
>>> max_used_connections=0
>>> max_connections=100
>>> threads_connected=0
>>> It is possible that mysqld could use up to
>>> key_buffer_size + (record_buffer + sort_buffer)*max_connections =
>>> 225791 K bytes of memory
>>> Hope that's ok, if not, decrease some variables in the equation
>>>
>>> Attempting backtrace. You can use the following information to find
>>> out where mysqld died. If you see no messages after this, something
>>> went terribly wrong...
>>> Bogus stack limit or frame pointer, fp=0xbfffe0b8,
>>> stack_bottom=0x3bdbc910, thread_stack=65536, aborting backtrace.
>>> Trying to get some variables.
>>> Some pointers may be invalid and cause the dump to abort...
>>> thd->query at 0x3ac6fc20  is invalid pointer
>>> thd->thread_id=1919639395
>>>
>>> Successfully dumped variables, if you ran with --log, take a look at
>>> the details of what thread 1919639395 did to cause the crash.  In
>>> some cases of really
>>> bad corruption, the values shown above may be invalid
>>>
>>> The manual page at http://www.mysql.com/doc/C/r/Crashing.html
>>> contains information that should help you find out what is causing
>>> the crash 021112 07:20:39  mysqld ended
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> PLUG mailing list
>>> PLUG at lists.pdxlinux.org
>>> http://lists.pdxlinux.org/mailman/listinfo/plug
>>
>>
>>
>>
>> _______________________________________________
>> PLUG mailing list
>> PLUG at lists.pdxlinux.org
>> http://lists.pdxlinux.org/mailman/listinfo/plug
>
>
>
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug