Spoken too soon...
Yesterday MySQL died again... there is nothing in the log files... (be
it mysqld.log, .err, or /var/log/messages).
The hosting provider is running an application called 'big-brother'
and a lot of sef-faults appear in the logs from this. I don't know if
thins is the cause...
Hi Gabriel,
Yesterday MySQL died again... there is nothing in the log files... (be
it mysqld.log, .err, or /var/log/messages).
The hosting provider is running an application called 'big-brother'
and a lot of sef-faults appear in the logs from this. I don't know if
thins is the cause... if this
Yup... For now the problem stopped...
These humongos values were because they were initialized at MAX_INT on
that 64bit machine...
In the my.cnf file they were not mentioned at all !
2^64 - 1 == 18446744073709551615
Now look at the values below !
--
Gabriel PREDA
Senior Web Developer
On
Hi list,
Since we bought a better hardware for our dedicated MySQL Server we
have been running into some problems.
We are using:
- Fedora Core 3 - 64bit version
- Kernel: 2.6.9-1.667smp - x86_64
- MySQL 5.0.21-standard - for 64bit
- RAM: 4 GB
- RAID 5 matrix with 3 SCSI disks at 15k rotations
Hi,
Please let us know what all variables you have configured in your my.cnf
files.
what is your total size of memory in box.
eg : max_connections
key_buffer_size
sort_buffer_size.
Gabriel PREDA wrote:
Hi list,
Since we bought a better hardware for our dedicated MySQL Server
Gabriel, in your SHOW VARIABLES, I see a handful of settings that are
much, much larger than normal:
| max_binlog_cache_size | 18446744073709551615
| max_join_size | 18446744073709551615
| max_seeks_for_key | 18446744073709551615
|
