Make WordPress Core

Opened 3 years ago

Closed 3 years ago

#52460 closed defect (bug) (invalid)

Error 502 since upgrade to 5.6.1 with PHP 8 in Admin or Login Area

Reported by: torstensbuechereckede's profile torstensbuechereckede Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.6.1
Component: General Keywords:
Focuses: Cc:

Description

Hello,

since upgrade to 5.6.1 in combination with PHP 8 login Aread and Admin Areas is not working anymore. With 5.6 and even before I used WordPress with PHP 8 without problems. I have tried dugging log but there are no errors shown. As soon as I switch back to PHP 7.4 the problems vanish. I have also tried JQuery Migrade but there are no errors or problems shown.

Homepage to reproduce: https://od.torstens-buecherecke.de (is not always available but should be most of the time)
Same page running with PHP 7.4 https://www.torstens-buecherecke.de

Change History (3)

#1 @torstensbuechereckede
3 years ago

Some additional information:
I have removed all plugins from plugin folder - no effect.

I have checked the logs from Php 8.0:
[07-Feb-2021 00:26:00] WARNING: [pool www] child 3546610 exited on signal 11 (SIGSEGV - core dumped) after 10229.739266 seconds from start
[07-Feb-2021 00:26:00] NOTICE: [pool www] child 3674842 started

Nginx log:
2021/02/07 00:26:00 [error] 2468#0: *3584 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.181.2, server: od.torstens-buecherecke.de, request: "GET /wp-admin/about.php?updated HTTP/2.0", upstream: "fastcgi://unix:/run/php/php8.0-fpm.sock:", host: "od.torstens-buecherecke.de", referrer: "https://od.torstens-buecherecke.de/wp-admin/update-core.php?action=do-core-upgrade"

#2 @torstensbuechereckede
3 years ago

This was a PHP bug, not a WordPress bug. After PHP update today it is working again.

#3 @SergeyBiryukov
3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Thanks for the follow-up!

Yeah, this sounds like an issue with a particular environment rather than WordPress core, as the error happens before WordPress even gets a chance to start.

Note: See TracTickets for help on using tickets.