Either change it back, or delete the log files so that they will be built in the new size.
(Backup the entire tree, just in case.)
From: Manuel Arostegui [mailto:manuel@stripped]
Sent: Tuesday, July 23, 2013 1:05 PM
To: Rick James
Cc: Johan De Meersman; Luis H. Forchesatto; mysql list
Subject: Re: InnoDB problem.
2013/7/23 Rick James <rjames@stripped<mailto:rjames@stripped>>
Did you change innodb_log_file_size?
innodb_log_file_size error always appears in the logs...he only posted a few lines of his
log...but I guess (or I want to believe) he's gone through the whole log before starting
the thread :-)
> -----Original Message-----
> From: Johan De Meersman [mailto:vegivamp@stripped<mailto:vegivamp@stripped>]
> Sent: Tuesday, July 23, 2013 9:57 AM
> To: Luis H. Forchesatto; mysql list
> Subject: Re: InnoDB problem.
> No immediate clue here, but maybe someone else does - so please keep the
> list in CC at all times :-p
> Random question: were the files backed up from a different version? I'd
> expect some kind of warning about that in the logs, really, but you never
> ----- Original Message -----
> > From: "Luis H. Forchesatto"
> > To: "Johan De Meersman"
> > Sent: Tuesday, 23 July, 2013 6:34:47 PM
> > Subject: Re: InnoDB problem.
> > The error log:
> > 130723 10:04:23 [ERROR] Plugin 'InnoDB' init function returned error.
> > 130723 10:04:23 [ERROR] Plugin 'InnoDB' registration as a STORAGE
> > ENGINE failed.
> > 130723 10:04:23 [Note] Event Scheduler: Loaded 0 events
> > 130723 10:04:23 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for
> > connections.
> > Version: '5.1.41' socket: '' port: 3306 Source distribution
> > 2013/7/23 Johan De Meersman <
> vegivamp@stripped<mailto:vegivamp@stripped> >
> > --
> > Att.
> > Luis H. Forchesatto
> > http://br.linkedin.com/pub/luis-henrique-forchesatto/73/684/a67
> Unhappiness is discouraged and will be corrected with kitten pictures.