使用vagrant的lamp stack localhost - 没有在var / log中获取system.log或exception.log的任何错误消息

时间:2016-03-12 01:02:50

标签: php magento exception logging

它是一个magento 12 ee构建...我进入了一些核心代码并故意改变了一个用于日志异常目的的方法,看看我是否会抛出错误。它打破了我的商店(就像我怀疑的那样)并且我在前端收到了错误消息,但它没有写入我的日志。

System => Linux precise64 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64
Build Date => Apr 17 2015 15:09:58
Server API => Command Line Interface
Virtual Directory Support => disabled
Configuration File (php.ini) Path => /etc/php5/cli
Loaded Configuration File => /etc/php5/cli/php.ini
Scan this dir for additional .ini files => /etc/php5/cli/conf.d
Additional .ini files parsed => /etc/php5/cli/conf.d/00-ioncube.ini,

我刚刚检查了日志文件夹的权限,并将其设置为755.

在管理面板的系统偏好设置中,它已启用= yes。

public static function getVersionInfo()
    {
        return array(
            'major'     => '1',
            'minor'     => '12',
            'revision'  => '0',
            'patch'     => '2',

有什么想法吗?

File: `log/'
  Size: 238         Blocks: 8          IO Block: 8192   directory
Device: 14h/20d Inode: 13844008    Links: 7
Access: (0755/drwxr-xr-x)  Uid: (  502/ UNKNOWN)   Gid: (   20/ dialout)
Access: 2016-03-12 00:55:11.000000000 +0000
Modify: 2016-02-17 22:01:01.000000000 +0000
Change: 2016-03-12 00:48:17.000000000 +0000
 Birth: -



vagrant@precise64:/vagrant/var$ echo $UID
1000
vagrant@precise64:/vagrant/var$ id -u <username>
-bash: syntax error near unexpected token `newline'
vagrant@precise64:/vagrant/var$ id -u
1000
vagrant@precise64:/vagrant/var$ 

0 个答案:

没有答案