[
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
