Bug 1460765 - Segmentation faults
Summary: Segmentation faults
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-12 16:24 UTC by Bill Helgeson
Modified: 2023-09-14 03:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 18:06:29 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
EVM log (7.54 MB, application/x-gzip)
2017-06-12 16:24 UTC, Bill Helgeson
no flags Details
evm.log after running appliance for 2days+ (1.21 MB, application/x-gzip)
2017-06-19 13:52 UTC, Kedar Kulkarni
no flags Details

Description Bill Helgeson 2017-06-12 16:24:18 UTC
Created attachment 1287073 [details]
EVM log

Description of problem: Appliance running on vmware 6.5 constant segmentation faults


Version-Release number of selected component (if applicable):
5.8

How reproducible: just let the appliance run and it will fault and stop running.


Steps to Reproduce:
1.install, raise memory for vm to 16GB, add disk for DB
2.register
3.enable roles including ansible, no c&U
4.Add vmware provider

Actual results:

Fault and go out of memory after a while


Expected results: should just run


Additional info: I am suspecting the cause in the garbage collection routine.

Comment 2 Kedar Kulkarni 2017-06-19 13:47:54 UTC
I tried to reproduce this scenario by letting an appliance run over the weekend but I could not see it throw a "Segmentation Fault". It is still running.

Comment 3 Kedar Kulkarni 2017-06-19 13:52:39 UTC
Created attachment 1289112 [details]
evm.log after running appliance for 2days+

Comment 7 Red Hat Bugzilla 2023-09-14 03:59:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.