Bug 138879 - pulse: segmentation fault with empty lvs.conf file.
pulse: segmentation fault with empty lvs.conf file.
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: piranha (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2004-11-11 14:33 EST by Derek Anderson
Modified: 2009-04-16 16:15 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-12 14:04:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:470 normal SHIPPED_LIVE Updated piranha package 2004-12-20 00:00:00 EST

  None (edit)
Description Derek Anderson 2004-11-11 14:33:47 EST
Description of problem:
This is relevant only to the x86_64 architecture so far.

Install piranha, set piranha-passwd, and start piranha-gui service
(this is probably not relevant, but it is the procedure I used).  Then
run 'pulse'.

[root@link-01 root]# pulse --verbose
Segmentation fault
[root@link-01 root]# echo $?

The lvs.cf file is empty, so I would expect to see a parse error (as
happens on i386) but not a seg fault.

[root@bench-01 piranha]# pulse --verbose
pulse: error parsing /etc/sysconfig/ha/lvs.cf at line 0: Empty

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

How reproducible:

Steps to Reproduce:
1. Install piranha
2. Start 'pulse' before doing any configuration to lvs.cf
Actual results:
Segmentation fault

Expected results:
Parse error on lvs.cf.

Additional info:
Comment 1 Lon Hohberger 2004-11-11 15:43:45 EST
fixed in .7.10-1
Comment 2 Derek Anderson 2004-11-12 14:04:16 EST
Verified in piranha-0.7.10-2.
Comment 3 John Flanagan 2004-12-20 20:26:17 EST
An advisory has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.


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