![[技術英会話]【IT特化】本番環境で404エラーが発生した時の対処法とは？総集編 #英会話 #英語のリスニング](https://image.listen.style/img/t4uymGDdF4YD-8uCBuG7kDcqGSCqC2lfgcygCm8ObYQ/resize:fill:1200:1200/aHR0cHM6Ly9pbWFnZS5saXN0ZW4uc3R5bGUvcC8wMWp2ZXk1bnI5aHAwMGhoZjNuYTFjYXFtaC9pbWFnZXMvWlRBYUNSRWxtQXlXVkl3dHFwbXVJRWJPQm9iaksyMXROVzMwTTQ2Ui5wbmc.avif)
404エラーの概要
では今回は、本番環境で404エラーが発生というテーマの総集編ですね。
今回の会話で特に注目していただきたいのは、問題解決の場面でよく使われる
Tackle systematicallyというフレーズと、インシデント対応語に欠かせない
Postmodernという用語です。
これらの表現が会話中に出てきたら、リスニングの邪魔にならない程度に
軽く日本語の解説を挟みます。
このチャンネルでは、一般には見つけにくいサイバーセキュリティを題材にした
教育形式の英語教材を配信しています。
面白いと思っていただけたら、チャンネル登録とコメントをお願いします。
文章で内容を確認したい方は、ノートをご覧ください。
なお、次回以降はレベル別にコンテンツを分割していく予定です。
新シリーズにご期待ください。
システム対処法の実践
それでは、どのような内容なのかまとめて聞いてみましょう。
Stay Calm. Let's tackle this systematically.
First, confirm the exact URL that's giving the 404.
And has anything else changed on the server recently, besides the Project Phoenix deployment?
Any OS updates? Configuration tweaks? Anything?
Tackle Systematicallyは、思いついたコマンドをとりあえず試したりするのではなくて、
まず現状把握をしなければいけないというニュアンスです。
Tackleというのは、ある程度の困難が予想されるけれども、
諦めずに冷静にというニュアンスでよく出てくる動詞ですね。
Alright. Next, I need to see the directory listing of the document root.
Since this is production, be careful what you share.
Just show me the relevant directory.
Also, show me the virtual host configuration for www.example.com.
Don't paste the whole httpd.conference, just the relevant virtual host block.
Use cat and grep if you need to.
Okay. Here's the output.
And here's the relevant part of the Apache configuration.
Okay. Just as we suspected before, there's no aboutus.html or aboutus.php file in the document root.
But since this is production, we can't just assume it was a missing file.
Was this page ever working after the deployment?
404エラーの発生と対策
Did anyone confirm it?
Do we have any monitoring in place that would have caught this earlier?
Hi. I thought I checked it, but I can't be 100% sure.
We have basic uptime monitoring, but not specific page checks.
This is a huge oversight.
I'm contacting Catherine, the developer, right now to see if the file was even supposed to be part of this release.
Okay. Catherine confirmed that aboutus.html should have been included.
They're sending me the file now.
They're also checking the deployment package to see why it was missing.
This is turning into a bigger issue.
It happens. Focus on getting the page back up first.
Once you have the file, place it in //www.html.project-phoenix.
Then, before you do anything else, check the Apache configuration syntax, Apache CTL config test.
Okay. I've got the aboutus.html file.
I've put it in the correct directory.
Running Apache CTL config test now.
Good. Now, instead of a full restart, try a graceful reload, Apache CTL graceful.
This will minimize downtime.
Okay. I ran Apache CTL graceful.
Now, test the aboutus page.
And also check the main site functionality.
Make sure the graceful reload didn't cause any unexpected issues.
Use a different browser or incognito mode to avoid caching issues.
Yes. The aboutus page is working now.
And the rest of the site seems fine too.
Thank you so much, Sarah.
I'm so relieved.
I'll definitely be adding more thorough checks to our deployment process, including specific page checks.
404エラーの対処と分析
And we need to investigate why that file was missing in the first place.
Absolutely. This is a learning experience.
We need a postmortem on this incident.
We should discuss.
1. Improving our deployment checklist.
2. Implementing more comprehensive monitoring including content checks.
3. Automating deployments to reduce human error.
4. Reviewing the communication process between development and operations.
For now, monitor the site closely for the next few hours.
And let's schedule that postmortem meeting.
日本でいうなぜなぜ分析に近いイメージですね。
個人を追求するのではなくてプロセス改善につなげるのがポイントです。
