NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Mysql server does not start in boot time NetBSD 6.0



2012/12/25, Sverre Froyen <sverre%viewmark.com@localhost>:
>
> On Dec 25, 2012, at 15:45, Edgar Rodolfo <rodolfobsd%gmail.com@localhost> 
> wrote:
>
>> 2012/12/25, Helge Mühlmeier <h_muehlmeier%gmx.de@localhost>:
>>> Hi,
>>>
>>> I think you have to use
>>>
>>> mysqld=YES in /etc/rc.conf instead of mysql=YES
>>
>> Ok, thanks for your reply, I do not remember exactly if it is mysql or
>> mysqld, but i copy the example script that NetBSD says when mysql
>> server finished the installation:
>> cp /usr/pkg/share/examples/rc.d/mysqld or mysql to /etc/rc.d/, is the
>> daemon that i am using in /etc/rc.conf.
>>
>> Yes is mysqld, sorry, but is the same, the daemon does not start in
>> boot time, i saw in boot time that says mysqld stating, but when i am
>> inside and put /etc/rc.d/mysqld status it says mysqld is not running,
>> for me is strange, because in another release for example 5.2 it
>> works, i remember that mysqld=YES was sufficient, thanks in advance
>> for your repley again!
>
> I see start failures on boot for mysqld 5.5.28 on amd64 NetBSD 6 and
> current. Using "/etc/rc.d/mysqld start" after boot seems to works fine. The
> mysqld error log shows a segmentation fault.
>
> I have an i386 NetBSD 6 system with mysqld 5.4.27 that works fine. I'm
> trying to determine if it is a i386 vs amd64 issue or if it is a mysqld
> version issue (I suspect the former).

Currently i have two machines (one virtual machine and real machine)
in both is the same, mysql 5.1 version and 5.5 is the same strange
behavior  they do not start in boot time :(, but is normally when i
write /etc/rc.d/mysqld start.
I have NetBSD 6.0 release i386 (NetBSD-6.0-i386)
I read some recomendations, e.g.
http://wiki.netbsd.org/pkgsrc/how_to_install_a_mysql_server/, but i
can not start mysql in boot time normally as i do in another release
(5.x)



>
> I have core dumps of mysqld and the backtraces are:
>
> NetBSD 6:
>
> Program terminated with signal 11, Segmentation fault.
> #0  0x00007f7ff56ecc6a in _lwp_kill () from /usr/lib/libc.so.12
> (gdb) bt
> #0  0x00007f7ff56ecc6a in _lwp_kill () from /usr/lib/libc.so.12
> #1  0x00007f7ff7807e28 in pthread_kill () from /usr/lib/libpthread.so.1
> #2  0x000000000065969b in handle_fatal_signal ()
> #3  <signal handler called>
> #4  0x00000000007383fd in Event_scheduler::dump_internal_status() ()
> #5  0x00000000005eee42 in Events::dump_internal_status() ()
> #6  0x00000000005cb79c in mysql_print_status() ()
> #7  0x000000000050a423 in signal_hand ()
> #8  0x00007f7ff7809edb in ?? () from /usr/lib/libpthread.so.1
> #9  0x00007f7ff5675a50 in ___lwp_park50 () from /usr/lib/libc.so.12
> #10 0x00007f7fe7400000 in ?? ()
> #11 0x00007f7ff7fffbc0 in ?? ()
> #12 0x0000000111110001 in ?? ()
> #13 0x0000000033330003 in ?? ()
> #14 0x0000000000000000 in ?? ()
>
> NetBSD-current:
>
> Program terminated with signal 11, Segmentation fault.
> #0  0x00007f7ff570686a in _lwp_kill () from /usr/lib/libc.so.12
> (gdb) bt
> #0  0x00007f7ff570686a in _lwp_kill () from /usr/lib/libc.so.12
> #1  0x00007f7ff7807d08 in pthread_kill () from /usr/lib/libpthread.so.1
> #2  0x000000000065975f in handle_fatal_signal ()
> #3  0x00007f7ff569a8d0 in opendir () from /usr/lib/libc.so.12
> #4  0x000000010000000b in ?? ()
> #5  0x0000000000000000 in ?? ()
>
> Like I said, the segfault only happens when mysqld is started at boot time.
>
> Regards,
> Sverre
>
>


Home | Main Index | Thread Index | Old Index