You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Martin Povolny (JIRA)" <ji...@apache.org> on 2012/10/04 11:29:07 UTC
[jira] [Created] (DTACLOUD-333) inconvenient logging to
/var/log/messages
Martin Povolny created DTACLOUD-333:
---------------------------------------
Summary: inconvenient logging to /var/log/messages
Key: DTACLOUD-333
URL: https://issues.apache.org/jira/browse/DTACLOUD-333
Project: DeltaCloud
Issue Type: Improvement
Components: Server
Environment: fedora 17
Reporter: Martin Povolny
Priority: Minor
While I expect /var/log/messages to contain short log messages from critical system components, when using aoelus i find my messages filled up with hundreds of log messages from deltacloud including:
* access-log-like entries:
Oct 4 11:11:44 test1 deltacloudd[537]: 127.0.0.1 - - [04/Oct/2012 11:11:44] "GET /api HTTP/1.1" 200 1114 0.0218
* stacktraces:
Oct 4 11:11:44 test1 deltacloudd[537]: OVIRT::OvirtException:No route to host - connect(2)
Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:131:in `handle_fault'
Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:69:in `rescue in http_get'
Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:66:in `http_get'
Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/client/datacenter_api.rb:14:in `datace
nters'
...
I would expect these log messages to reside in appropriate files under /var/log/deltacloud or something like that
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-333) inconvenient logging to
/var/log/messages
Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469298#comment-13469298 ]
Michal Fojtik commented on DTACLOUD-333:
----------------------------------------
Fix for long exceptions:
http://tracker.deltacloud.org/set/84
It also use ExceptionHandler.logger method that can be set to the Logger class and with right configuration you can achieve that Deltacloud will log wherever you want :)
> inconvenient logging to /var/log/messages
> -----------------------------------------
>
> Key: DTACLOUD-333
> URL: https://issues.apache.org/jira/browse/DTACLOUD-333
> Project: DeltaCloud
> Issue Type: Improvement
> Components: Server
> Environment: fedora 17
> Reporter: Martin Povolny
> Assignee: Michal Fojtik
> Priority: Minor
>
> While I expect /var/log/messages to contain short log messages from critical system components, when using aoelus i find my messages filled up with hundreds of log messages from deltacloud including:
> * access-log-like entries:
> Oct 4 11:11:44 test1 deltacloudd[537]: 127.0.0.1 - - [04/Oct/2012 11:11:44] "GET /api HTTP/1.1" 200 1114 0.0218
> * stacktraces:
> Oct 4 11:11:44 test1 deltacloudd[537]: OVIRT::OvirtException:No route to host - connect(2)
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:131:in `handle_fault'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:69:in `rescue in http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:66:in `http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/client/datacenter_api.rb:14:in `datace
> nters'
> ...
> I would expect these log messages to reside in appropriate files under /var/log/deltacloud or something like that
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-333) inconvenient logging to
/var/log/messages
Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469251#comment-13469251 ]
Michal Fojtik commented on DTACLOUD-333:
----------------------------------------
Hi Martin,
There are two 'bugs':
1. The stacktrace should definitely not be 100+ lines long. I need to play with Sinatra :show_errors/:dump_exceptions settings to make this more sane.
2. Under Fedora/RHEL we log into syslog, so you can configure syslog to forward DC logs wherever you want. The there should be also --log option for deltacloudd that we should make available in sysconfig/deltacloud-core.
> inconvenient logging to /var/log/messages
> -----------------------------------------
>
> Key: DTACLOUD-333
> URL: https://issues.apache.org/jira/browse/DTACLOUD-333
> Project: DeltaCloud
> Issue Type: Improvement
> Components: Server
> Environment: fedora 17
> Reporter: Martin Povolny
> Priority: Minor
>
> While I expect /var/log/messages to contain short log messages from critical system components, when using aoelus i find my messages filled up with hundreds of log messages from deltacloud including:
> * access-log-like entries:
> Oct 4 11:11:44 test1 deltacloudd[537]: 127.0.0.1 - - [04/Oct/2012 11:11:44] "GET /api HTTP/1.1" 200 1114 0.0218
> * stacktraces:
> Oct 4 11:11:44 test1 deltacloudd[537]: OVIRT::OvirtException:No route to host - connect(2)
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:131:in `handle_fault'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:69:in `rescue in http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:66:in `http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/client/datacenter_api.rb:14:in `datace
> nters'
> ...
> I would expect these log messages to reside in appropriate files under /var/log/deltacloud or something like that
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-333) inconvenient logging to
/var/log/messages
Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik reassigned DTACLOUD-333:
--------------------------------------
Assignee: Michal Fojtik
> inconvenient logging to /var/log/messages
> -----------------------------------------
>
> Key: DTACLOUD-333
> URL: https://issues.apache.org/jira/browse/DTACLOUD-333
> Project: DeltaCloud
> Issue Type: Improvement
> Components: Server
> Environment: fedora 17
> Reporter: Martin Povolny
> Assignee: Michal Fojtik
> Priority: Minor
>
> While I expect /var/log/messages to contain short log messages from critical system components, when using aoelus i find my messages filled up with hundreds of log messages from deltacloud including:
> * access-log-like entries:
> Oct 4 11:11:44 test1 deltacloudd[537]: 127.0.0.1 - - [04/Oct/2012 11:11:44] "GET /api HTTP/1.1" 200 1114 0.0218
> * stacktraces:
> Oct 4 11:11:44 test1 deltacloudd[537]: OVIRT::OvirtException:No route to host - connect(2)
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:131:in `handle_fault'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:69:in `rescue in http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:66:in `http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/client/datacenter_api.rb:14:in `datace
> nters'
> ...
> I would expect these log messages to reside in appropriate files under /var/log/deltacloud or something like that
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-333) inconvenient logging to
/var/log/messages
Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471578#comment-13471578 ]
Michal Fojtik commented on DTACLOUD-333:
----------------------------------------
For logging to file:
http://tracker.deltacloud.org/set/88
NOTE: Deltacloud need to be started with '-L' parameter with the full path for the file where it will log. Like: $ deltacloudd -i mock -L /var/log/deltacloud-core/api.log
The SystemD scripts in RPM need update too, to make this configurable.
> inconvenient logging to /var/log/messages
> -----------------------------------------
>
> Key: DTACLOUD-333
> URL: https://issues.apache.org/jira/browse/DTACLOUD-333
> Project: DeltaCloud
> Issue Type: Improvement
> Components: Server
> Environment: fedora 17
> Reporter: Martin Povolny
> Assignee: Michal Fojtik
> Priority: Minor
>
> While I expect /var/log/messages to contain short log messages from critical system components, when using aoelus i find my messages filled up with hundreds of log messages from deltacloud including:
> * access-log-like entries:
> Oct 4 11:11:44 test1 deltacloudd[537]: 127.0.0.1 - - [04/Oct/2012 11:11:44] "GET /api HTTP/1.1" 200 1114 0.0218
> * stacktraces:
> Oct 4 11:11:44 test1 deltacloudd[537]: OVIRT::OvirtException:No route to host - connect(2)
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:131:in `handle_fault'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:69:in `rescue in http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/rbovirt.rb:66:in `http_get'
> Oct 4 11:11:44 test1 deltacloudd[537]: /usr/share/gems/gems/rbovirt-0.0.12/lib/client/datacenter_api.rb:14:in `datace
> nters'
> ...
> I would expect these log messages to reside in appropriate files under /var/log/deltacloud or something like that
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira