References: <CAHwjr37=puHdnbDaLYM83ioCECwvRqDE8NO-YpG3xsUBW1x-fA@mail.gmail.com> <4F0C8B9E.40808@nothome.org> <CA+cSEmPYZbeCAk_DbXrOo12HSSQiHUenECyhv5RBPNsBw-WpzQ@mail.gmail.com> <CA+cSEmO24GwH8=2BEMiNN6jSvVgDuszDjBqa4NNfPs9m8SYapA@mail.gmail.com>
In-Reply-To: <CA+cSEmO24GwH8=2BEMiNN6jSvVgDuszDjBqa4NNfPs9m8SYapA@mail.gmail.com>
Mime-Version: 1.0 (iPod Mail 8C148)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <2B149571-CAE6-463D-BDD7-EE2CA5B74977@gmail.com>
Cc: Nathan Angelacos <nangel@nothome.org>,
 "alpine-infra@alpinelinux.org" <alpine-infra@alpinelinux.org>
From: Jeff Bilyk <jbilyk@gmail.com>
Subject: Re: Bugs.a.o
Date: Tue, 10 Jan 2012 16:14:18 -0500
To: Carlo Landmeter <clandmeter@gmail.com>

Only other thing I can think to try is to dump the binlogs since it's during=
 recovery that the crash occurs.  Logs say there's only one transaction that=
's trying to apply...

Jeff

On Jan 10, 2012, at 3:02 PM, Carlo Landmeter <clandmeter@gmail.com> wrote:

> I'm getting the below, not sure what to do now. Already updated mysql
> to latest 2.2 version.
>=20
>=20
> 120110 19:53:23 InnoDB: highest supported file format is Barracuda.
> InnoDB: Log scan progressed past the checkpoint lsn 15160684415
> 120110 19:53:23  InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> InnoDB: Doing recovery: scanned up to log sequence number 15163771045
> InnoDB: 1 transaction(s) which must be rolled back or cleaned up
> InnoDB: in total 12 row operations to undo
> InnoDB: Trx id counter is 6DE8E00
> 120110 19:53:24  InnoDB: Starting an apply batch of log records to the
> database...
> InnoDB: Progress in percents: 0 1 120110 19:53:24 - mysqld got signal 11 ;=

> This could be because you hit a bug. It is also possible that this binary
> or one of the libraries it was linked against is corrupt, improperly built=
,
> or misconfigured. This error can also be caused by malfunctioning hardware=
.
> We will try our best to scrape up some info that will hopefully help diagn=
ose
> the problem, but since we have already crashed, something is definitely wr=
ong
> and this may fail.
>=20
> key_buffer_size=3D16777216
> read_buffer_size=3D262144
> max_used_connections=3D0
> max_threads=3D151
> thread_count=3D0
> connection_count=3D0
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =3D 13=
3434 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>=20
> Thread pointer: 0x0
> Attempting backtrace. You can use the following information to find out
> where mysqld died. If you see no messages after this, something went
> terribly wrong...
> stack_bottom =3D (nil) thread_stack 0x30000
> /usr/sbin/mysqld(my_print_stacktrace+0x46)[0xb73bb529]
> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contain=
s
> information that should help you find out what is causing the crash.
> 120110 19:53:24 mysqld_safe mysqld from pid file
> /var/run/mysqld/mysqld.pid ended
>=20
>=20
> On Tue, Jan 10, 2012 at 8:08 PM, Carlo Landmeter <clandmeter@gmail.com> wr=
ote:
>> Ill be able to check in a minute if needed.
>>=20
>> Carlo
>>=20
>> On Jan 10, 2012 8:03 PM, "Nathan Angelacos" <nangel@nothome.org> wrote:
>>>=20
>>> On 01/10/2012 09:49 AM, Jeff Bilyk wrote:
>>>>=20
>>>> Hi Everyone,
>>>>=20
>>>> Redmine on bugs.a.o is having issues this afternoon.  Fastcgi is
>>>> crashing, by the looks of things because of multiple spiders hitting
>>>> it at once.  Banning the user agents in lightty config hasn't helped,
>>>> neither has upping the redmine sockets to 32 (from 4) but I'm out of
>>>> time to keep trying to fix it.  If anyone else has some time to take a
>>>> look, that'd be awesome,
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Jeff
>>>>=20
>>>=20
>>> Mysql died, so far I'm unable to restart it
>>>=20
>>=20