In the message dated: Fri, 16 Feb 2007 20:07:58 +0100,
The pithy ruminations from Per Andreas Buer on 
<Re: [Bacula-users] mysql db dump problems, making sense of dbcheck results> we
re:
=> [EMAIL PROTECTED] wrote
=> >    [1] Are segmentation faults from "mysqldump" a known problem, and is 
=> >            there a known solution?
=> >   
=> 
=> No. Its usually the result of a bug in either mysql(dump | library | 

Hmmm... The problem has presisted through several versions of mysql.

=> server) or some serious corruption. Does the mysql error log reveal 
=> anything? How abount "check table" on the relevant tables?

Running
        check table $TABLE;
for each table produces the message:

        +----------------+-------+----------+----------+
        | Table          | Op    | Msg_type | Msg_text |
        +----------------+-------+----------+----------+
        | bacula.$TABLE  | check | status   | OK       | 
        +----------------+-------+----------+----------+

foreach $TABLE. There were no errors reported.



=> 
=> > (..)
=> >
=> >    [5] Are there any obvious things that can be done to improve the 
=> >            database reliability, stability, or performance?
=> >   
=> 
=> You might have a memory error. Have you tried running memtest? Could you 

Nope, I haven't tried it. However, this is a production machine, running a lot 
of other things--and there aren't other indications of a memory problem.

=> post your my.cnf together with your machine specs (uname -a and free -m) 
=> gives us the interesting parts.

Sure.

  uname -a:
        Linux parthenon 2.4.26-openmosix1 #10 SMP Wed Sep 14 10:18:08 EDT 2005 
i686 i686 i386 GNU/Linux

        
  free -m
                     total       used       free     shared    buffers     
cached
        Mem:         11841      11594        246          0         97      
10076
        -/+ buffers/cache:       1419      10421
        Swap:         6655        392       6263
        

###################   /etc/my.cnf   #######################################
# Example MySQL config file for large systems.
#
# This is for a large system with memory = 512M where the system runs mainly
# MySQL.

# The following options will be passed to all MySQL clients
[client]
#password       = your_password
port            = 3306
socket          = /var/lib/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port            = 3306
socket          = /var/lib/mysql/mysql.sock
skip-locking
key_buffer = 256M
max_allowed_packet = 8M
table_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 4


# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id       = 1


# Point the following paths to different dedicated disks
tmpdir          = /san3/var/tmp # It's a faster disk than /
#log-update     = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 64M
#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /var/lib/mysql/
innodb_data_file_path = ibdata1:100M:autoextend
innodb_log_group_home_dir = /var/lib/mysql/
innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 512M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 256M     # Default is 64M
innodb_log_buffer_size = 64M    # Default is 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 75

[mysqldump]
quick
max_allowed_packet = 64M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
safe-updates

[isamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
###########################################################################

Yes, the machine is doing way too many things to be the best choice for a 
bacula server...but that's going to change very soon.


Thanks for all your help,

Mark

=> 
=> 
=> Per.
=> 





The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. If the reader of 
this message is not the intended recipient or an agent responsible for 
delivering it to the intended recipient, you are hereby notified that you have 
received this document in error and that any review, dissemination, 
distribution, or copying of this message is strictly prohibited. If you have 
received this communication in error, please notify us immediately by e-mail, 
and delete the original message.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to