blocks|key|2084396|text|请检查运行PHP+CLI的用户帐户是否具有对/var/log/php_errors.log的写入权限。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2084397|此外，您可以验证是否使用了正确的php.ini文件，如下所示：|2084398|php+-a+-c+/etc/php5/cli/php.ini|code-block|syntax|javascript|2084399|entityMap^0|M|N|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Please check that the user account running PHP CLI has write access to <code>/var/log/php_errors.log</code>.

Additionally, you can verify that you are using the correct php.ini file like this:

<pre><code>php -a -c /etc/php5/cli/php.ini
</code></pre>

blocks|key|2084406|text|作为诊断，您可以尝试以这种方式强制写入错误日志：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2084407|php+-c+/etc/php5/cli/php.ini+-r+"+error_log('test+123');+"|code-block|syntax|javascript|2084408|现在，您应该在日志中看到测试123：|2084409|tail+/var/log/php_errors.log|2084410|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

As a diagnostic, you can attempt to force a write to the error log this way:
<pre><code>php -c /etc/php5/cli/php.ini -r &quot; error_log('test 123'); &quot;
</code></pre>
You should now see test 123 in your log:
<pre><code>tail /var/log/php_errors.log
</code></pre>

blocks|key|2084417|text|PHP的日志记录/报告行为也依赖于error_reporting。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2084418|一些PHP框架(例如，CodeIgniter)在生产模式下执行error_reporting(E_STRICT)语句或等效语句，这将大大减少记录的错误的数量/种类。|offset|length|style|CODE|2084419|如果你想调试一些东西，那么你可以把下面的语句放在你的代码之前：|2084420|error_reporting(E_ALL);|code-block|syntax|javascript|2084421|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/CodeIgniter^0|0|V|P|B|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@$D|10|E|11|1|12]]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|14|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

The logging/reporting behaviour of PHP is dependent on error_reporting too.
Some PHP frameworks (for example, <a href="https://en.wikipedia.org/wiki/CodeIgniter" rel="nofollow noreferrer">CodeIgniter</a>) execute an <code>error_reporting(E_STRICT)</code> statement or equivalent, when in production mode, which will severely reduce the number/kind of logged errors.
If you want to debug something, then you can just put the following statement right before your code:
<pre><code>error_reporting(E_ALL);
</code></pre>

blocks|key|1870546|text|如果您找不出原因，或者可能没有对文件php.ini的用户权限，调试无信息解析错误的另一种方法是将您的PHP源文件包装在另一个PHP源文件中，主体类似于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1870547|ini_set('display_errors',+1);
error_reporting(E_ALL);

include+"mybustedfile.php";|code-block|syntax|javascript|1870548|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you can't figure out what why or perhaps don't have user permissions on file php.ini, another way to debug a no-information parse error is to wrap your PHP source in another PHP source file with a body something like:
<pre><code>ini_set('display_errors', 1);
error_reporting(E_ALL);

include &quot;mybustedfile.php&quot;;
</code></pre>

blocks|key|2084528|text|当在Ubuntu+12.04+(精确穿山甲)环境中设置PHP+CLI日志时，这个问答线程对我非常有帮助，所以我想发布一个提炼我所学知识的答案。除了大量的信息provided+by+David+Chan以及as+George+Cummins之外，我还创建了一个logrotate.d脚本来确保PHP错误日志不会失控，并对其进行了设置，以便多个用户能够将错误记录到公共的PHP错误日志中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2084529|首先，PHP+CLI的默认行为是将错误消息记录到标准输出；记录到文件不是默认行为。这通常意味着登录到运行PHP+CLI命令的同一命令行终端会话。虽然PHP文件确实有针对指定error_log的调整，但需要进行额外的调整才能真正使其正常工作。|2084530|首先，我必须创建一个初始的php_errors.log文件：|2084531|sudo+touch+/var/log/php_errors.log|code-block|syntax|javascript|2084532|由于有问题的服务器是由从事各种项目的web开发人员使用的，因此我为他们建立了一个名为www-users的公共组。在本例中，我希望www-users可以读写php_errors.log，我像这样更改了文件的所有权：|2084533|sudo+chown+root:www-users+/var/log/php_errors.log|2084534|然后将该文件的权限更改为：|2084535|sudo+chmod+664+/var/log/php_errors.log|2084536|是的，从安全的角度来看，在www-users中拥有一个任何人都可以读写的日志文件并不是很好。但这是一个受控的共享工作环境。所以我相信用户会尊重这样的东西。此外，当PHP从CLI运行时，任何可以执行此操作的用户都将需要对日志进行写访问，甚至需要写入日志。|2084537|接下来，进入/etc/php5/cli/php.ini来调整默认的Ubuntu12.04设置，以匹配这个新的日志文件：|2084538|sudo+nano+/etc/php5/cli/php.ini|2084539|幸运的是，log_errors在Ubuntu12.04中是默认启用的：|2084540|log_errors+=+On|2084541|但是，为了允许记录到文件，我们需要更改error_log以匹配新文件，如下所示：|2084542|error_log+=+/var/log/php_errors.log|2084543|设置logrotate.d脚本。|2084544|现在应该就是这样了，但是因为我不想让日志失控，所以我为php_errors.log设置了一个logrotate.d。在/etc/logrotate.d/中创建一个名为php-cli的文件，如下所示：|2084545|sudo+nano+/etc/logrotate.d/php-cli|2084546|并将此日志旋转守护程序脚本的内容放在其中：|2084547|/var/log/php_errors.log+{
++++++++weekly
++++++++missingok
++++++++rotate+13
++++++++compress
++++++++delaycompress
++++++++copytruncate
++++++++notifempty
++++++++create+664+root+www-users
++++++++sharedscripts
}|2084548|测试设置。|2084549|完成后，让我们使用David+Chan’s+tip测试设置|2084550|php+-r+"error_log('This+is+an+error+test+that+we+hope+works.');"|2084551|如果运行正确，您应该会返回到一个空的命令提示符，因为PHP+CLI错误不再发送到标准输出。因此，请检查测试错误消息的实际php_errors.log，如下所示：|2084552|tail+-n+10+/var/log/php_errors.log|2084553|其中应该有一个带时间戳的错误行，如下所示：|2084554|[23-Jul-2014+16:04:56+UTC]+This+is+an+error+test+that+we+hope+works.|2084555|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Ubuntu_version_history#Ubuntu_12.04_LTS_.28Precise_Pangolin.29|1|https://stackoverflow.com/a/19867274/117259|2|https://stackoverflow.com/a/6387561/117259|3^0|3L|B|2|C|0|26|M|1|2U|H|2|0|2E|9|0|D|E|0|0|16|9|1S|9|25|E|0|0|0|0|D|9|0|6|L|0|0|5|A|0|0|J|9|0|0|2|B|0|R|E|1A|B|1N|H|2B|7|0|0|0|0|0|9|G|3|0|0|1O|E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2B|8|@$9|2C|A|2D|B|C]]|D|@$9|2E|A|2F|1|2G]|$9|2H|A|2I|1|2J]|$9|2K|A|2L|1|2M]]|E|$]]|$1|F|3|G|5|6|7|2N|8|@$9|2O|A|2P|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|2Q|8|@$9|2R|A|2S|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|2T|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|2U|8|@$9|2V|A|2W|B|C]|$9|2X|A|2Y|B|C]|$9|2Z|A|30|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|L|7|31|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|32|8|@]|D|@]|E|$]]|$1|U|3|V|5|L|7|33|8|@]|D|@]|E|$M|N]]|$1|W|3|X|5|6|7|34|8|@$9|35|A|36|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|37|8|@$9|38|A|39|B|C]]|D|@]|E|$]]|$1|10|3|11|5|L|7|3A|8|@]|D|@]|E|$M|N]]|$1|12|3|13|5|6|7|3B|8|@$9|3C|A|3D|B|C]]|D|@]|E|$]]|$1|14|3|15|5|L|7|3E|8|@]|D|@]|E|$M|N]]|$1|16|3|17|5|6|7|3F|8|@$9|3G|A|3H|B|C]]|D|@]|E|$]]|$1|18|3|19|5|L|7|3I|8|@]|D|@]|E|$M|N]]|$1|1A|3|1B|5|6|7|3J|8|@$9|3K|A|3L|B|C]]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|3M|8|@$9|3N|A|3O|B|C]|$9|3P|A|3Q|B|C]|$9|3R|A|3S|B|C]|$9|3T|A|3U|B|C]]|D|@]|E|$]]|$1|1E|3|1F|5|L|7|3V|8|@]|D|@]|E|$M|N]]|$1|1G|3|1H|5|6|7|3W|8|@]|D|@]|E|$]]|$1|1I|3|1J|5|L|7|3X|8|@]|D|@]|E|$M|N]]|$1|1K|3|1L|5|6|7|3Y|8|@]|D|@]|E|$]]|$1|1M|3|1N|5|6|7|3Z|8|@]|D|@$9|40|A|41|1|42]]|E|$]]|$1|1O|3|1P|5|L|7|43|8|@]|D|@]|E|$M|N]]|$1|1Q|3|1R|5|6|7|44|8|@$9|45|A|46|B|C]]|D|@]|E|$]]|$1|1S|3|1T|5|L|7|47|8|@]|D|@]|E|$M|N]]|$1|1U|3|1V|5|6|7|48|8|@]|D|@]|E|$]]|$1|1W|3|1X|5|L|7|49|8|@]|D|@]|E|$M|N]]|$1|1Y|3|-4|5|6|7|4A|8|@]|D|@]|E|$]]]|1Z|$20|$5|21|22|23|E|$24|25]]|26|$5|21|22|23|E|$24|27]]|28|$5|21|22|23|E|$24|29]]|2A|$5|21|22|23|E|$24|27]]]]

This question and answer thread was very helpful to me while setting up PHP CLI logging on an <a href="https://en.wikipedia.org/wiki/Ubuntu_version_history#Ubuntu_12.04_LTS_.28Precise_Pangolin.29" rel="nofollow noreferrer">Ubuntu 12.04</a> (Precise Pangolin) environment, so I wanted to post an answer that distills what I learned. In addition to the great information <a href="https://stackoverflow.com/a/19867274/117259">provided by David Chan</a> as well <a href="https://stackoverflow.com/a/6387561/117259">as George Cummins</a>, I have created a <code>logrotate.d</code> script to ensure the PHP CLI error log doesn’t grow out of control as well as set this up so multiple users will be able to log errors to the common PHP CLI error log.
First, the default behavior of the PHP CLI is to log error messages to standard output; logging to a file is not default behavior. Which usually means logging to the same command line terminal session that is running the PHP CLI command. While the PHP ini file does have accommodations for a specified <code>error_log</code> additional accommodations need to be made to truly make it work.
First, I had to create an initial <code>php_errors.log</code> file:
<pre><code>sudo touch /var/log/php_errors.log
</code></pre>
Since the server in question is used by web developers working on various projects, I have set up a common group for them called <code>www-users</code>. And in this case, I want the <code>php_errors.log</code> to be readable and writable by <code>www-users</code> I change the ownership of the file like this:
<pre><code>sudo chown root:www-users /var/log/php_errors.log
</code></pre>
And then change the permissions of the file to this:
<pre><code>sudo chmod 664 /var/log/php_errors.log
</code></pre>
Yes, from a security standpoint having a log file readable and writable by anyone in <code>www-users</code> is not so great. But this is a controlled shared work environment. So I trust the users to respect things like this. And besides, when PHP is run from the CLI, any user who can do that will need write access to the logs anyway to even get a log written.
Next, go into <code>/etc/php5/cli/php.ini</code> to adjust the default Ubuntu 12.04 settings to match this new log file:
<pre><code>sudo nano /etc/php5/cli/php.ini
</code></pre>
Happily <code>log_errors</code> is enabled by default in Ubuntu 12.04:
<pre><code>log_errors = On
</code></pre>
But to allow logging to a file we need to change the <code>error_log</code> to match the new file like this:
<pre><code>error_log = /var/log/php_errors.log
</code></pre>
<h3>Setup a <code>logrotate.d</code> script.</h3>
Now that should be it, but since I don’t want logs to run out of control I set a <code>logrotate.d</code> for the <code>php_errors.log</code>. Create a file called <code>php-cli</code> in <code>/etc/logrotate.d/</code> like this:
<pre><code>sudo nano /etc/logrotate.d/php-cli
</code></pre>
And place the contents of this log rotate daemon script in there:
<pre><code>/var/log/php_errors.log {
 weekly
 missingok
 rotate 13
 compress
 delaycompress
 copytruncate
 notifempty
 create 664 root www-users
 sharedscripts
}
</code></pre>
<h3>Testing the setup.</h3>
With that done, let’s test the setup using <a href="https://stackoverflow.com/a/19867274/117259">David Chan’s tip</a>:
<pre><code>php -r &quot;error_log('This is an error test that we hope works.');&quot;
</code></pre>
If that ran correctly, you should just be bounced back to an empty command prompt since PHP CLI errors are no longer being sent to standard output. So check the actual <code>php_errors.log</code> for the test error message like this:
<pre><code>tail -n 10 /var/log/php_errors.log
</code></pre>
And there should be a timestamped error line in there that looks something like this:
<pre><code>[23-Jul-2014 16:04:56 UTC] This is an error test that we hope works.
</code></pre>

PHP currently will not log errors produced from the command line.
I have:
<pre class="lang-none prettyprint-override"><code>log_errors = On
error_log = /var/log/php_errors.log
</code></pre>
in file /etc/php5/cli/php.ini.
Am I missing a further setting to get this working?

PHP CLI won't log errors

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

PHP目前不会记录从命令行产生的错误。我有：log_errors = Onerror_log = /var/log/php_errors.log在文件/etc/php5/cli/php.ini中。我是否遗漏了进一步的设置来使其正常工作？

问PHP CLI不会记录错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP CLI不会记录错误EN