From: Michael Ellerman <mpe@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 7
Date: Tue, 08 Jan 2019 13:28:01 +1100 [thread overview]
Message-ID: <87k1jfc28e.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <87sgy4a7vi.fsf@concordia.ellerman.id.au>
Michael Ellerman <mpe@ellerman.id.au> writes:
> Michael Ellerman <mpe@ellerman.id.au> writes:
>> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>>> On Mon, Jan 7, 2019 at 5:08 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>> Status of my local build tests will be at
>>>> http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
>>>> advice about cross compilers/configs that work, we are always open to add
>>>> more builds.
>>>
>>> Proxy Error
>>> The proxy server received an invalid response from an upstream server.
>>> The proxy server could not handle the request GET /kisskb/.
>>>
>>> Reason: Error reading from remote server
>>>
>>> Apache/2.4.37 (Debian) Server at kisskb.ellerman.id.au Port 80
>>>
>>> Oops...
>>
>> Erk.
>>
>> Seems postgres is unhappy, database is corrupt.
>>
>> I'm restoring from a backup but it seems to be taking a long time, I may
>> not get it finished tonight.
>
> So I finally got the backup to restore.
>
> Then I restarted everything, and as soon as the first set of new results
> came in the DB appears to have wedged again.
Seems 00:56 me was a pit too impatient. It's up now and seems to be
working OK.
Sorry for the outage.
cheers
next prev parent reply other threads:[~2019-01-08 2:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 4:06 linux-next: Tree for Jan 7 Stephen Rothwell
2019-01-07 7:35 ` Geert Uytterhoeven
2019-01-07 11:49 ` Michael Ellerman
2019-01-07 13:56 ` Michael Ellerman
2019-01-08 2:28 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-07 15:43 Stephen Rothwell
2021-01-07 3:01 Stephen Rothwell
2020-01-07 6:03 Stephen Rothwell
2016-01-07 10:21 Stephen Rothwell
2015-01-07 4:16 Stephen Rothwell
2015-01-07 7:34 ` Sedat Dilek
2015-01-07 14:26 ` Guenter Roeck
2015-01-07 16:33 ` Paul E. McKenney
2015-01-07 17:30 ` Guenter Roeck
2015-01-07 18:09 ` Paul E. McKenney
2015-01-07 19:18 ` Guenter Roeck
2015-01-07 20:00 ` Christian Borntraeger
2015-01-07 20:33 ` Guenter Roeck
2014-01-07 6:38 Stephen Rothwell
2013-01-07 3:26 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1jfc28e.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).