You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Michal Fojtik (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/05 13:09:22 UTC
[jira] [Resolved] (DTACLOUD-186) no such file to load -- syslog in
Windows when starting deltacloudd
[ https://issues.apache.org/jira/browse/DTACLOUD-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik resolved DTACLOUD-186.
------------------------------------
Resolution: Fixed
Assignee: Michal Fojtik (was: David Lutterkort)
This issue should be fixed in
Subject: [PATCH core] Core: Fixed missing syslog library under Windows environment (DTACLOUD-186)
Waiting for review to close this issue.
> no such file to load -- syslog in Windows when starting deltacloudd
> -------------------------------------------------------------------
>
> Key: DTACLOUD-186
> URL: https://issues.apache.org/jira/browse/DTACLOUD-186
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: Windows 7, Ruby187
> Reporter: Dies Koper
> Assignee: Michal Fojtik
>
> deltacloudd won't start:
> D:\sources\OSS\cloud\deltacloud\server>ruby bin\deltacloudd -i mock
> Starting Deltacloud API :: mock :: http://localhost:3001/api
> D:/programs/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- syslog (Loa
> dError)
> from D:/programs/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
> from D:/sources/OSS/cloud/deltacloud/server/lib/sinatra/rack_syslog.rb:1
> from D:/programs/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
> from D:/programs/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
> from D:/sources/OSS/cloud/deltacloud/server/lib/deltacloud/server.rb:32
> This is using the latest workspace. On CentOS 5, with exactly the same DeltaCloud artifacts (I've mounted the same directory), it works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira