From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Ellerman Subject: Re: linux-next: Tree for Jan 7 Date: Tue, 08 Jan 2019 13:28:01 +1100 Message-ID: <87k1jfc28e.fsf@concordia.ellerman.id.au> References: <20190107150609.0510def3@canb.auug.org.au> <87va30adsg.fsf@concordia.ellerman.id.au> <87sgy4a7vi.fsf@concordia.ellerman.id.au> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <87sgy4a7vi.fsf@concordia.ellerman.id.au> Sender: linux-kernel-owner@vger.kernel.org To: Geert Uytterhoeven , Stephen Rothwell Cc: Linux Next Mailing List , Linux Kernel Mailing List List-Id: linux-next.vger.kernel.org Michael Ellerman writes: > Michael Ellerman writes: >> Geert Uytterhoeven writes: >>> On Mon, Jan 7, 2019 at 5:08 AM Stephen Rothwell 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