Bug 1310065 - core has crashed [NEEDINFO]
Summary: core has crashed
Keywords:
Status: CLOSED DUPLICATE of bug 1305891
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: core
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 2
Assignee: Nishanth Thomas
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 11:20 UTC by Martin Kudlej
Modified: 2016-03-07 09:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-07 09:39:13 UTC
Target Upstream Version:
mbukatov: needinfo? (nthomas)

Attachments (Terms of Use)
skyring logs (1.63 MB, application/x-gzip)
2016-02-19 11:20 UTC, Martin Kudlej 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1305891 0 unspecified CLOSED skyring crashed with long traceback 2021-02-22 00:41:40 UTC

Internal Links: 1305891

Description Martin Kudlej 2016-02-19 11:20:43 UTC 
Created attachment 1128515 [details]
skyring logs

Description of problem:
I've tried accept nodes, create cluster, create pool and then left it for a while. When I've came back core didn't run.
You can find log files in attachment.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.8-4.el7.x86_64
rhscon-ceph-0.0.6-4.el7.x86_64
rhscon-ui-0.0.14-1.el7.noarch

How reproducible:
?

Actual results:
It has crashed.

Expected results:
It should not crash.
Comment 1 Daniel Horák 2016-02-19 12:06:59 UTC 
It is maybe duplicate of Bug 1305891 (at least the traceback with "Too many open files (signaler.cpp:234)" seems similar).
Comment 2 Martin Bukatovic 2016-02-24 09:45:32 UTC 
Could you check if this BZ is a duplicate of BZ 1305891?
Comment 4 Martin Kudlej 2016-03-07 09:39:13 UTC 
Yes, it seems that this is duplicate of BZ 1305891.

*** This bug has been marked as a duplicate of bug 1305891 ***
Note You need to log in before you can comment on or make changes to this bug.