Thank you for answer. The problem is that I wrote in previous message
that there is no sql backup just the files for binary backup. Hardware
we are using is a simple laptop with Windows 7 that runs 5.1 server in
case the originally installed files are in use. It runs an 5.5 server
paralelly as
Hello,
We are facing a strange innodb related problem. Our client ran mysql 5.1
on WinXP having file_per_table disabled. OS crashed after 5 years
continuous running and our client of course does not have any backup
(big company with own IT department so we do not have acces to their
system
Am 05.08.2015 um 17:06 schrieb Csepregi Árpád:
150805 17:02:31 InnoDB: Page dump in ascii and hex (16384 bytes):
hex...
150805 17:02:31 InnoDB: Page checksum 1094951825, prior-to-4.0.14-form
checksum 1449969277
InnoDB: stored checksum 1467223489, prior-to-4.0.14-form stored checksum
87759728
On Aug 11, 2011, at 2:30 PM, Keith Murphy wrote:
Hey everyone,
I have run across something that has me stumped. I have some systems that
have very large error logs because we haven't moved from statement-based to
mixed-based replication yet so they get a lot of warnings logged. I need to
this will help you
http://adminlinux.blogspot.com/2009/09/mysql-log-file-rotation.html
On Fri, Aug 12, 2011 at 9:43 AM, Paul DuBois paul.dub...@oracle.com wrote:
On Aug 11, 2011, at 2:30 PM, Keith Murphy wrote:
Hey everyone,
I have run across something that has me stumped. I have some
Hey everyone,
the problem was that I have the error log in /var/log/mysqld/mysql.error and
SELinux was not configured to allow it to rotate. I have compiled a custom
module to allow it so the problem is resolved. It was not an issue with
MySQL Server itself.
thanks again.
Keith
On Fri, Aug 12,
Hey everyone,
I have run across something that has me stumped. I have some systems that
have very large error logs because we haven't moved from statement-based to
mixed-based replication yet so they get a lot of warnings logged. I need to
rotate the error logs and have started looking at it
Kishore Jalleda schrieb:
Hi you may be having issues with the byte order on the opetron's and the
P4's , this was asked earlier in the list, and here's what Jimmy from Mysql
had to say
Kishore,
Thanks for the suggestion, but all x86 have the same byte order... and
as I wrote its
Could you post the error log entries from the slave and the binlog where the
slave hangs , also just to make sure d2 and d3 replicate well without any
problems from d1 right ? also as per your message d4 and d5 would work well
if no replication is enabled at all so essentially its only the
A neverending story.
I thought it worked (without having an idea what has been the problem),
but it broke down again after a few hours.
My current set up is:
-A p4 production server (Server1) running debian linux, 2.4 kernel,
mysql 4.1.13-standard-log. This server is replicating to several
Hi you may be having issues with the byte order on the opetron's and the
P4's , this was asked earlier in the list, and here's what Jimmy from Mysql
had to say
All machines used in the cluster must have the same architecture; that is,
all machines hosting nodes must be either
I thought I found the reason for my problems with the change in
join-behaviour in mysql 5, but Iwas wrong :( there is more trouble :(
my replications hangs with simple queries like insert into table
(a,b,c) values (1,2,3) on a myisam-table.
It just hangs forever with no cpu-load on the slave.
I've been trying to get my new mysql-5.0.18-servers running as slaves of our
production systems to check if all our applications work fine with mysql 5 and
to do some tests and tuning on the new servers.
The old servers are all P4s, 3GB RAM running debian-linux, 2.4-kernel and
official mysql
Greetings list,
I'm having a MySQL login problem that I cannot figure out, and (surprise
surprise), I'm something of a newcomer to MySQL. I have read two decent
MySQL books, searched the MySQL.com online manual, and searched the web for
everything I can think of, to no avail.
Here is my
Hi,
try command: flush privileges;
flush tables;
Michal Dvoracek [EMAIL PROTECTED]
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
On Thu, 23 Aug 2001, Dave Walcott wrote:
Greetings list,
I'm having a MySQL login problem that I cannot figure out, and (surprise
surprise), I'm something of a newcomer to MySQL. I have read two decent
MySQL books, searched the MySQL.com online manual, and searched the web for
everything
On Thu, Aug 23, 2001 at 12:24:53AM -0700, Dave Walcott wrote:
Greetings list,
I'm having a MySQL login problem that I cannot figure out, and
(surprise surprise), I'm something of a newcomer to MySQL. I have
read two decent MySQL books, searched the MySQL.com online manual,
and searched
On Thu, Aug 23, 2001 at 09:40:36AM +0100, Dvoøáèek Michal wrote:
Hi,
try command: flush privileges;
flush tables;
The flush is automatic with GRANT for him. The issue is with
'localhost' vs. all other hosts.
--
Jeremy D. Zawodny, [EMAIL PROTECTED]
Technical Yahoo - Yahoo
On Thu, Aug 23, 2001 at 03:45:05PM +0800, Alan Tai wrote:
grant all
on dbname.*
to user identified by 'password';
check the manual for more detail. seems like you are missing the
'host'.
That's okay. As the manual says, that's a shorthand way of specifying
user@%. But that doesn't
19 matches
Mail list logo
