Re: bugs.php.net downtime

From: Date: Sat, 21 Jul 2018 10:04:20 +0000
Subject: Re: bugs.php.net downtime
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to internals+get-102931@lists.php.net to get a copy of this message
Still doesn't work for me. I get a white screen and the comment does not appear even after I reload the page. Nikita On Sat, Jul 21, 2018 at 11:51 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote: > That one should be fixed. It was actually posting the comments, but > getting an error after. If you reload the bug you see it. > > On Sat, Jul 21, 2018 at 5:41 AM, Christoph M. Becker <cmbecker69@gmx.de> > wrote: > >> On 21.07.2018 at 10:46, Nikita Popov wrote: >> >> > On Tue, Jul 17, 2018 at 10:38 PM, Rasmus Lerdorf <rasmus@lerdorf.com> >> wrote: >> > >> >> I need to move bugs.php.net to another server sometime today. I won't >> be >> >> able to do it without a little bit of downtime as I have to stop new >> >> activity on the existing box, copy the DB over and then point DNS to >> the >> >> new box. The DNS TTL is only 5 minutes, so it shouldn't be unavailable >> for >> >> much longer than that. >> >> >> >> Hopefully the new box will be a bit quicker too. It is moving from PHP >> 5.5 >> >> to 7.2 on faster hardware. >> > >> > I'm getting a WSOD when trying to add a comment to a bug while logged >> in. >> > Not sure what's different for me, as it seems to work for other @ >> php.net >> > users. >> >> Same for me; it doesn't matter whether I'm logged in as cmb@ or just >> commenting as user. Interestingly, altough I get the 500, I can change >> the meta information (status, summary, etc.), but no comment is added. >> >> -- >> Christoph M. Becker >> > >

« previous php.internals (#102931) next »