blocks|key|3734452|text|您需要启用PHP错误日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3734453|这是由于web服务器中的一些随机故障，当你遇到php错误时，它会抛出一个500内部错误(我也有同样的问题)。|3734454|如果您查看PHP错误日志，您应该会找到解决方案。|3734455|see+here+in+the+doc+of+how+to+enable+it+in+the+php.ini|offset|length|3734456|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/errorfunc.configuration.php^0|0|0|0|0|1I|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

You need to enable the PHP error log.

This is due to some random glitch in the web server when you have a php error, it throws a 500 internal error (i have the same issue).

If you look in the PHP error log, you should find your solution.

<a href="http://php.net/manual/en/errorfunc.configuration.php" rel="nofollow">see here in the doc of how to enable it in the php.ini</a>

blocks|key|291664|text|也许有什么东西关闭了错误输出。(我理解您是想说其他脚本可以正确地将它们的错误输出到errorlog中？)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|291665|您可以通过确定脚本退出脚本的位置来开始调试脚本(首先在脚本的第一行添加一个echo+1;+exit;，并检查浏览器是否输出1，然后将该行下移)。|offset|length|style|CODE|291666|entityMap^0|0|11|D|1P|1|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

Maybe something turns off error output. (I understand that you are trying to say that other scripts properly output their errors to the errorlog?)

You could start debugging the script by determining where it exits the script (start by adding a <code>echo 1; exit;</code> to the first line of the script and checking whether the browser outputs <code>1</code> and then move that line down).

blocks|key|3734530|text|扫描源文件以查找@。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3734531|From+php+documentation+site|3734532|3734533|目前，"@“错误控制操作符前缀甚至会禁用终止脚本执行的关键错误的错误报告。其中，这意味着如果您使用"@“来隐藏来自某个函数的错误，并且该函数不可用或输入错误，则脚本将立即终止，并且不会提示原因。|blockquote|3734534|3734535|entityMap|0|LINK|mutability|MUTABLE|url|http://www.php.net/manual/en/language.operators.errorcontrol.php^0|8|1|0|0|R|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Scan your source files to find <code>@</code>.

<a href="http://www.php.net/manual/en/language.operators.errorcontrol.php" rel="noreferrer">From php documentation site</a>

<blockquote>
 Currently the "@" error-control operator prefix will even disable
 error reporting for critical errors that will terminate script
 execution. Among other things, this means that if you use "@" to
 suppress errors from a certain function and either it isn't available
 or has been mistyped, the script will die right there with no
 indication as to why.
</blockquote>

blocks|key|4019630|text|在过去，我在两种情况下没有错误日志：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4019631|4019632|运行Apache的用户没有修改php_error_log文件的权限。由于.htaccess配置错误，例如重写模块设置错误，出现|ordered-list-item|offset|length|style|CODE|4019633|错误500。在这种情况下，错误会记录到Apache+error_log文件中。|4019634|4019635|entityMap^0|0|0|F|D|10|9|0|Q|9|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@$F|R|G|S|H|I]|$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|N|$]]

In the past, I had no error logs in two cases:

<ol>
<li>The user under which Apache was running had no permissions to modify <code>php_error_log</code> file.</li>
<li>Error 500 occurred because of bad configuration of <code>.htaccess</code>, for example wrong rewrite module settings. In this situation errors are logged to Apache <code>error_log</code> file.</li>
</ol>

blocks|key|292424|text|这是错误可能不可见的另一个原因：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|292425|我也有同样的问题。在我的例子中，我从生产环境中复制了源代码。因此，在index.php中定义的ENVIRONMENT变量被设置为'production'。这导致error_reporting被设置为0(无日志记录)。只需将其设置为'development'，您就会开始在apache日志中看到错误消息。|offset|length|style|CODE|292426|原来500是由于数据库配置中缺少分号:-)|292427|entityMap^0|0|Y|9|1B|B|1S|C|28|F|37|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]|$D|T|E|U|F|G]|$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$]]

Here is another reason why errors might not be visible:

I had the same issue. In my case, I had copied the source from a production environment. Hence the <code>ENVIRONMENT</code> variable defined in <code>index.php</code> was set to <code>'production'</code>. This caused <code>error_reporting</code> to be set to 0 (no logging). Just set it to <code>'development'</code> and you should start seeing error messages in apache log.

Turned out the 500 was due to a semi colon missing in database config :-)

blocks|key|4019731|text|另一个发生在我身上的情况是，我对我的一些页面进行了卷曲，得到了内部服务器错误，apache日志中什么都没有，即使我启用了所有错误报告。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4019732|我的问题是我在卷发中设置了curl_setopt($CR,+CURLOPT_FAILONERROR,+true);|offset|length|style|CODE|4019733|它没有显示我的错误，尽管有一个错误，这是因为错误发生在框架级别，而不是PHP级别，所以它没有出现在日志中。|4019734|entityMap^0|0|D|18|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Another case which happened to me, is I did a CURL to some of my pages, and got internal server error and nothing was in the apache logs, even when I enabled all error reporting.

My problem was that in the CURL I set 
<code>curl_setopt($CR, CURLOPT_FAILONERROR, true);</code>

Which then didn't show me my error, though there was one, this happened because the error was on a framework level and not a PHP one, so it didn't appear in the logs.

blocks|key|3734652|text|对于Symfony项目，请确保检查项目的app/logs中的文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3734653|更多细节可以在这篇文章中找到：|3734654|How+to+debug+500+Error+in+Symfony+2|offset|length|3734655|顺便说一句，其他框架或内容管理系统也有这种行为。|3734656|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/18577003/how-to-debug-500-error-in-symfony-2^0|0|0|0|Z|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

For Symfony projects, be sure to check files in the project'es app/logs

More details available on this post : 
<a href="https://stackoverflow.com/questions/18577003/how-to-debug-500-error-in-symfony-2">How to debug 500 Error in Symfony 2</a>

Btw, other frameworks or CMS share this kind of behaviour.

blocks|key|3734695|text|请确保您的文件权限正确。如果apache没有读取该文件的权限，那么它就不能写入日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3734696|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Be sure your file permissions are correct. If apache doesn't have permission to read the file then it can't write to the log.

blocks|key|3734744|text|将以下内容复制并粘贴到新的.htaccess文件中，并将其放置在网站的根文件夹中：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3734745|php_flag++display_errors++++++++++++++++++on
php_flag++display_startup_errors++++++++++on|code-block|syntax|javascript|3734746|错误将直接显示在您的页面中。|3734747|这是快速调试的最好方法，但是，不要长时间使用它，因为它可能会破坏安全性。|BOLD|3734748|entityMap^0|D|9|0|0|0|F|L|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|U|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|V|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|W|8|@$9|X|A|Y|B|O]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|Q|$]]

Copy and paste the following into a new <code>.htaccess</code> file and place it on your website's root folder :

<pre><code>php_flag display_errors on
php_flag display_startup_errors on
</code></pre>

Errors will be shown directly in your page. 

That's the best way to debug quickly but don't use it for long time because it could be a security breach.

blocks|key|2121214|text|如果您仍然有500个错误并且没有日志，您可以尝试从命令行执行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2121215|php+-f+file.php|code-block|syntax|javascript|2121216|它不会像在浏览器中那样工作(从服务器)，但如果代码中存在语法错误，您将在控制台中看到错误消息。|2121217|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you still have 500 error and no logs you can try to execute from command line:

<pre><code>php -f file.php
</code></pre>

it will not work exactly like in a browser (from server) but if there is syntax error in your code, you will see error message in console.

blocks|key|4019937|text|当这是一个问题时，对我来说发生了什么，是网站使用了太多的内存，所以我猜它无法写入错误日志或显示错误。为了清楚起见，这是一个Wordpress网站做的。提高服务器上的内存限制再次显示该站点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4019938|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

What happened for me when this was an issue, was that the site had used too much memory, so I'm guessing that it couldn't write to an error log or displayed the error. For clarity, it was a Wordpress site that did this. Upping the memory limit on the server showed the site again.

blocks|key|3734874|text|解决了我为此而苦苦挣扎，后来，我意识到我正在使用PHP5.6，所以我升级到了PHP7.0，然后我发布了git对冲突代码的评论。我在我的代码<<<<<<<<中发现了类似这样的东西，但是解决了它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3734875|entityMap^0|0|3|O|6|12|6|1F|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

SOLVED
I struggled with this and later on, I realized that I was working on PHP 5.6, so I upgraded to PHP 7.0, then I released there were comments placed by git for conflicting codes. I found something like this in my code &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt; But solved it.

I am having an issue when I have a php application that is returning an internal server error (500) however nothing is showing up in the error log.

Now I know there are error with what I am trying to run, I know I have missing some files and what not but something should show in the apache error log (otherwise how are I supposed to know exactly what I am missing).

I created a test script is errors it in under the same vhost configuration and those error show up fine so everything seems configured right as far as php/apache. Are there certain php errors that does show up in the error log (php is configure to display any type of notice, warning, , error, fatal error, etc...)?

This is running on ubunut 10.04 with the standard apache and php from the ubuntu repo with apt-get.

php return 500 error but no error log

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个问题，当我有一个php应用程序，返回一个内部服务器错误(500)，但没有在错误日志中显示。现在我知道我正在尝试运行的程序有错误，我知道我丢失了一些文件，但是apache错误日志中应该显示一些东西(否则我如何知道我到底缺少了什么)。我创建了一个测试脚本，它在相同的vhost配置下是错误的，这些错误显示得很好，所以...

问php返回500错误，但没有错误日志
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问php返回500错误，但没有错误日志EN