初期診断

Restore test: injected HTTP 500 after write-back

レシピ 20261112-restore-check-fail (restore-check-fail) · 最新の実行 2026-11-12 · 初回公開 2026-11-13 · 更新 2026-11-13 · Restore test

注入した障害

Injected fault: after write-back starts changing the site, the test server returns HTTP 500 for site pages, so the check after write-back fails.

出典:復元テスト(WP119 のテストサーバーで注入した障害)。フォーラムのスレッドはありません。

テスト構成と、障害再現後に観測した状態

テストサイト:WordPress 7.1、PHP 8.3。下の表は、レシピどおりに障害を再現した後のトップページとログインページの HTTP ステータスです。

サーバー構成トップページログインページ備考
Apache + PHP-FPM200500
Apache + php-cgi (mod_cgid)500500
Apache + mod_php200200
nginx + PHP-FPM500500

各実行の結果

日付(UTC)サーバー構成接続方式復旧料ファイルとデータベース(スナップショットとの比較)案件開始前に追加したコメント製品バージョン備考
2026-11-12Apache + PHP-FPMFTP全額返金Match except file ownersPresent2.1.460
2026-11-12Apache + PHP-FPMSSH全額返金Match except file ownersPresent2.1.460
2026-11-12Apache + php-cgi (mod_cgid)FTP全額返金Match except file ownersPresent2.1.460
2026-11-12Apache + php-cgi (mod_cgid)SSH全額返金Match except file ownersPresent2.1.460
2026-11-12Apache + mod_phpFTP全額返金Match except file ownersPresent2.1.460
2026-11-12Apache + mod_phpSSH全額返金Match except file ownersPresent2.1.460
2026-11-12nginx + PHP-FPMFTP全額返金Match except file ownersPresent2.1.460
2026-11-12nginx + PHP-FPMSSH全額返金Match except file ownersPresent2.1.460

ギャップと修正版

結果が「Matches snapshot」でない実行、または注入した障害が実際に発生したのに結果が「Recovered」になった実行は、すべてここに記載します:変更内容、修正を含むバージョン、再テストの日付と結果。

発見日サーバー構成接続方式変更内容修正版再実行
2026-11-12Apache + PHP-FPMFTPFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—
2026-11-12Apache + PHP-FPMSSHFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—
2026-11-12Apache + php-cgi (mod_cgid)FTPFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—
2026-11-12Apache + php-cgi (mod_cgid)SSHFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—
2026-11-12Apache + mod_phpFTPFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—
2026-11-12Apache + mod_phpSSHFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—
2026-11-12nginx + PHP-FPMFTPFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—
2026-11-12nginx + PHP-FPMSSHFound after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet.対応中—

補足

Runs from the acceptance testing of version 2.1.460 on 2026-11-12, on the small test site. Before each case, two problems were planted on the test site so that the case reaches write-back; the first table shows the HTTP status after that step. Payment in these runs is simulated; the recovery fee column shows the refund the system recorded for that payment.

これらは当社のテストサーバー上で、特定のバージョン・特定の日に記録したものであり、どのサイトについても結果を約束するものではありません。ホスティング、PHP、WordPress のバージョンが異なれば結果も異なることがあります。

初期診断 →