You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Min Chen (JIRA)" <ji...@apache.org> on 2013/06/24 18:58:20 UTC
[jira] [Commented] (CLOUDSTACK-3137) systemvms start fails on
latest master (4591f94)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692140#comment-13692140 ]
Min Chen commented on CLOUDSTACK-3137:
--------------------------------------
Prasanna, those two lines are not exactly exception, it is a way to use exception for racing condition, that is why log level is INFO.
> systemvms start fails on latest master (4591f94)
> ------------------------------------------------
>
> Key: CLOUDSTACK-3137
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3137
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Prasanna Santhanam
> Priority: Blocker
> Attachments: mslog.tar.bz2
>
>
> SystemVMs fail to start on latest master (4591f94a0bb69875dca769c9738998d3b5b96106)
> Only following exception is seen:
> Jun 22 10:13:18 cloudstack-centos63 local0: 2013-06-22 17:13:18,962 INFO [storage.volume.VolumeServiceImpl] (secstorage-1:null) Got exception in case of multi-thread
> Jun 22 10:13:19 cloudstack-centos63 local0: 2013-06-22 17:13:19,112 INFO [storage.volume.VolumeServiceImpl] (consoleproxy-1:null) Got exception in case of multi-thread
> Full logs attached.
--
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