Alex,
let us see. A known bug with Innobase is that <sys/stat> was not included
in univ.i in directory mysql/innobase/include. Then Innobase files are
created with arbitrary access permissions on some Unixes.
Could you look with ls -l what permissions Innobase data file ibdat1 has
on your machine and also the permissions in
log files in /usr/local/mysql/var/innobase_logs/ ?
In the config parameters below you should not define
innobase_log_arch_dir = innobase_log_group_home_dir,
but write the path:
innobase_log_arch_dir = /usr/local/mysql/var/innobase_logs/
Your archived log file has now been created in the default
directory: if you can find ib_arch_log_0000000000 somewhere,
you could also look at the file access permissions and mail the
output of ls -l to me.
If you try to recreate an Innobase database, you should delete all
Innobase data files, log files, the small archived log file,
and all .frm files for Innobase tables.
I will also try to build 3.23.35 on our Solaris machine and look
what happens.
Regards,
Heikki
> # Innobase > innobase_data_home_dir = /usr/local/mysql/var/innobase_data/
> innobase_data_file_path = ibdata1:500M
> set-variable = innobase_mirrored_log_groups=1
> innobase_log_group_home_dir = /usr/local/mysql/var/innobase_logs/
> set-variable = innobase_log_files_in_group=3
> set-variable = innobase_log_file_size=5M
> set-variable = innobase_log_buffer_size=8M
> innobase_flush_log_at_trx_commit=0
> innobase_log_arch_dir = innobase_log_group_home_dir
> innobase_log_archive=0
> set-variable = innobase_buffer_pool_size=64M
> set-variable = innobase_additional_mem_pool_size=2M
> set-variable = innobase_file_io_threads=4
> set-variable = innobase_lock_wait_timeout=50
>
============================================================================
========================
> > Here is my problem : >
> With even no queries on the server, I continually have the
> "Warning: Got signal 14 from thread X" in the log of Mysqld : >
> 010320 10:48:46 mysqld started > Innobase: Started
> /usr/local/mysql/libexec/mysqld: ready for connections
> 010320 10:49:32 Warning: Got signal 14 from thread 4
> 010320 10:49:34 Warning: Got signal 14 from thread 3
> 010320 10:49:36 Warning: Got signal 14 from thread 5
> 010320 10:49:38 Warning: Got signal 14 from thread 4
> 010320 10:49:40 Warning: Got signal 14 from thread 4
> 010320 10:49:42 Warning: Got signal 14 from thread 6
> 010320 10:49:44 Warning: Got signal 14 from thread 5
> 010320 10:49:46 Warning: Got signal 14 from thread 4
> 010320 10:49:48 Warning: Got signal 14 from thread 3
> 010320 10:49:50 Warning: Got signal 14 from thread 5
> 010320 10:49:52 Warning: Got signal 14 from thread 4 > ... >
> I did not have that with 3.23.32 ... but I did not have Innobase
> with 3.23.32 ... > > Is it a known bug ? >
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
