You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Johannes Skov Frandsen (JIRA)" <ji...@apache.org> on 2009/08/21 10:14:14 UTC
[jira] Created: (LOG4PHP-73) No output from logger af trunk update
No output from logger af trunk update
-------------------------------------
Key: LOG4PHP-73
URL: https://issues.apache.org/jira/browse/LOG4PHP-73
Project: Log4php
Issue Type: Bug
Components: Code
Affects Versions: 2.0
Environment: osx, php 5.3
osx, php 5.2.9
linux , 5.2.10
Reporter: Johannes Skov Frandsen
Fix For: 2.0
I updated from trunk this morning and now I get no output from my loggers.
require_once $_SERVER['DOCUMENT_ROOT'].'lib/log4php/src/main/php/Logger.php';
define('LOG4PHP_CONFIGURATION', $_SERVER['DOCUMENT_ROOT'].'/include/log4php.cron.properties');
$logger = Logger::getLogger('AutoScan');
This is my configuration:
log4php.debug = true
log4php.rootLogger = WARN, default
log4php.appender.default = LoggerAppenderDailyFile
log4php.appender.default.datePattern = Y-m-d
log4php.appender.default.file = ../logs/system_%s.log
log4php.appender.default.layout = LoggerLayoutTTCC
log4php.logger.Scan = DEBUG, Scan, Scan2
log4php.appender.Scan = LoggerAppenderDailyFile
log4php.appender.Scan.layout = LoggerLayoutHtml
log4php.appender.Scan.datePattern = Y-m-d
log4php.appender.Scan.file = ../logs/Scan_%s.log
log4php.appender.Scan2 = LoggerAppenderEcho
log4php.appender.Scan2.layout = LoggerLayoutHtml
log4php.logger.AutoScan = DEBUG, AutoScan
log4php.appender.AutoScan = LoggerAppenderEcho
log4php.appender.AutoScan.layout = LoggerLayoutHtml
Any idea what could be the cause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LOG4PHP-73) No output from logger after trunk
update
Posted by "Christian Grobmeier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745880#action_12745880 ]
Christian Grobmeier commented on LOG4PHP-73:
--------------------------------------------
Yes: http://ci.apache.org/projects/log4php/upgrading.html
This is deprecated:
define('LOG4PHP_CONFIGURATION', );
In favour to:
Logger::configure($_SERVER['DOCUMENT_ROOT'].'/include/log4php.cron.properties');
Please try the line I wrote. If that works for you, let me know.
I close the bug then.
Thanks
Christian
> No output from logger after trunk update
> ----------------------------------------
>
> Key: LOG4PHP-73
> URL: https://issues.apache.org/jira/browse/LOG4PHP-73
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.0
> Environment: osx, php 5.3
> osx, php 5.2.9
> linux , 5.2.10
> Reporter: Johannes Skov Frandsen
> Fix For: 2.0
>
>
> I updated from trunk this morning and now I get no output from my loggers.
> require_once $_SERVER['DOCUMENT_ROOT'].'lib/log4php/src/main/php/Logger.php';
> define('LOG4PHP_CONFIGURATION', $_SERVER['DOCUMENT_ROOT'].'/include/log4php.cron.properties');
> $logger = Logger::getLogger('AutoScan');
> This is my configuration:
> log4php.debug = true
> log4php.rootLogger = WARN, default
> log4php.appender.default = LoggerAppenderDailyFile
> log4php.appender.default.datePattern = Y-m-d
> log4php.appender.default.file = ../logs/system_%s.log
> log4php.appender.default.layout = LoggerLayoutTTCC
> log4php.logger.Scan = DEBUG, Scan, Scan2
> log4php.appender.Scan = LoggerAppenderDailyFile
> log4php.appender.Scan.layout = LoggerLayoutHtml
> log4php.appender.Scan.datePattern = Y-m-d
> log4php.appender.Scan.file = ../logs/Scan_%s.log
> log4php.appender.Scan2 = LoggerAppenderEcho
> log4php.appender.Scan2.layout = LoggerLayoutHtml
> log4php.logger.AutoScan = DEBUG, AutoScan
> log4php.appender.AutoScan = LoggerAppenderEcho
> log4php.appender.AutoScan.layout = LoggerLayoutHtml
> Any idea what could be the cause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LOG4PHP-73) No output from logger after trunk
update
Posted by "Johannes Skov Frandsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Skov Frandsen updated LOG4PHP-73:
------------------------------------------
Summary: No output from logger after trunk update (was: No output from logger af trunk update)
> No output from logger after trunk update
> ----------------------------------------
>
> Key: LOG4PHP-73
> URL: https://issues.apache.org/jira/browse/LOG4PHP-73
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.0
> Environment: osx, php 5.3
> osx, php 5.2.9
> linux , 5.2.10
> Reporter: Johannes Skov Frandsen
> Fix For: 2.0
>
>
> I updated from trunk this morning and now I get no output from my loggers.
> require_once $_SERVER['DOCUMENT_ROOT'].'lib/log4php/src/main/php/Logger.php';
> define('LOG4PHP_CONFIGURATION', $_SERVER['DOCUMENT_ROOT'].'/include/log4php.cron.properties');
> $logger = Logger::getLogger('AutoScan');
> This is my configuration:
> log4php.debug = true
> log4php.rootLogger = WARN, default
> log4php.appender.default = LoggerAppenderDailyFile
> log4php.appender.default.datePattern = Y-m-d
> log4php.appender.default.file = ../logs/system_%s.log
> log4php.appender.default.layout = LoggerLayoutTTCC
> log4php.logger.Scan = DEBUG, Scan, Scan2
> log4php.appender.Scan = LoggerAppenderDailyFile
> log4php.appender.Scan.layout = LoggerLayoutHtml
> log4php.appender.Scan.datePattern = Y-m-d
> log4php.appender.Scan.file = ../logs/Scan_%s.log
> log4php.appender.Scan2 = LoggerAppenderEcho
> log4php.appender.Scan2.layout = LoggerLayoutHtml
> log4php.logger.AutoScan = DEBUG, AutoScan
> log4php.appender.AutoScan = LoggerAppenderEcho
> log4php.appender.AutoScan.layout = LoggerLayoutHtml
> Any idea what could be the cause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LOG4PHP-73) No output from logger after trunk
update
Posted by "Johannes Skov Frandsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745883#action_12745883 ]
Johannes Skov Frandsen commented on LOG4PHP-73:
-----------------------------------------------
It worked.... thanks.
Maybe a update on the homepage would be a good idea.... the examples
are misleading on this issue.
> No output from logger after trunk update
> ----------------------------------------
>
> Key: LOG4PHP-73
> URL: https://issues.apache.org/jira/browse/LOG4PHP-73
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.0
> Environment: osx, php 5.3
> osx, php 5.2.9
> linux , 5.2.10
> Reporter: Johannes Skov Frandsen
> Fix For: 2.0
>
>
> I updated from trunk this morning and now I get no output from my loggers.
> require_once $_SERVER['DOCUMENT_ROOT'].'lib/log4php/src/main/php/Logger.php';
> define('LOG4PHP_CONFIGURATION', $_SERVER['DOCUMENT_ROOT'].'/include/log4php.cron.properties');
> $logger = Logger::getLogger('AutoScan');
> This is my configuration:
> log4php.debug = true
> log4php.rootLogger = WARN, default
> log4php.appender.default = LoggerAppenderDailyFile
> log4php.appender.default.datePattern = Y-m-d
> log4php.appender.default.file = ../logs/system_%s.log
> log4php.appender.default.layout = LoggerLayoutTTCC
> log4php.logger.Scan = DEBUG, Scan, Scan2
> log4php.appender.Scan = LoggerAppenderDailyFile
> log4php.appender.Scan.layout = LoggerLayoutHtml
> log4php.appender.Scan.datePattern = Y-m-d
> log4php.appender.Scan.file = ../logs/Scan_%s.log
> log4php.appender.Scan2 = LoggerAppenderEcho
> log4php.appender.Scan2.layout = LoggerLayoutHtml
> log4php.logger.AutoScan = DEBUG, AutoScan
> log4php.appender.AutoScan = LoggerAppenderEcho
> log4php.appender.AutoScan.layout = LoggerLayoutHtml
> Any idea what could be the cause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (LOG4PHP-73) No output from logger after trunk
update
Posted by "Christian Grobmeier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Grobmeier resolved LOG4PHP-73.
----------------------------------------
Resolution: Fixed
Yes, actually there is LOG4PHP-70 which describes that the homepage docs must be updated. The examples in the trunk are already updated.
Help is welcome! :-)
> No output from logger after trunk update
> ----------------------------------------
>
> Key: LOG4PHP-73
> URL: https://issues.apache.org/jira/browse/LOG4PHP-73
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.0
> Environment: osx, php 5.3
> osx, php 5.2.9
> linux , 5.2.10
> Reporter: Johannes Skov Frandsen
> Fix For: 2.0
>
>
> I updated from trunk this morning and now I get no output from my loggers.
> require_once $_SERVER['DOCUMENT_ROOT'].'lib/log4php/src/main/php/Logger.php';
> define('LOG4PHP_CONFIGURATION', $_SERVER['DOCUMENT_ROOT'].'/include/log4php.cron.properties');
> $logger = Logger::getLogger('AutoScan');
> This is my configuration:
> log4php.debug = true
> log4php.rootLogger = WARN, default
> log4php.appender.default = LoggerAppenderDailyFile
> log4php.appender.default.datePattern = Y-m-d
> log4php.appender.default.file = ../logs/system_%s.log
> log4php.appender.default.layout = LoggerLayoutTTCC
> log4php.logger.Scan = DEBUG, Scan, Scan2
> log4php.appender.Scan = LoggerAppenderDailyFile
> log4php.appender.Scan.layout = LoggerLayoutHtml
> log4php.appender.Scan.datePattern = Y-m-d
> log4php.appender.Scan.file = ../logs/Scan_%s.log
> log4php.appender.Scan2 = LoggerAppenderEcho
> log4php.appender.Scan2.layout = LoggerLayoutHtml
> log4php.logger.AutoScan = DEBUG, AutoScan
> log4php.appender.AutoScan = LoggerAppenderEcho
> log4php.appender.AutoScan.layout = LoggerLayoutHtml
> Any idea what could be the cause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.