Bug 621496 - Crash in rhts-test-runner.sh causes task hung-ups leading to External Watchdog
Summary: Crash in rhts-test-runner.sh causes task hung-ups leading to External Watchdog
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Community
Component: beah (Show other bugs)
(Show other bugs)
Version: 0.5
Hardware: All Linux
medium
medium vote
Target Milestone: ---
Assignee: Marian Csontos
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-05 09:55 UTC by Marian Csontos
Modified: 2011-09-28 15:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-02 05:40:08 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Marian Csontos 2010-08-05 09:55:03 UTC
Description of problem:
Following task got stuck: https://beaker.engineering.redhat.com/recipes/19237#task237349

/var/log/messages saying:

> Aug  5 03:13:01 dell-pesc430-01 logrotate: ALERT exited abnormally with [1]

And following segfaults were found on stderr:

> /usr/bin/rhts-test-runner.sh: line 187: 11210 Segmentation fault      ps -p "$pid"
     11211                       | grep -q "$pid"
> /usr/bin/rhts_environment.sh: line 64: 11216 Segmentation fault      rhts-report-result $1 $2 $OUTPUTFILE $3
> /usr/bin/rhts-test-runner.sh: line 4: 11217 Segmentation fault      logger -s "$0 report_finish start..."
> /usr/bin/rhts-test-runner.sh: line 4: 11218 Segmentation fault      rhts-submit-log -l /tmp/TESTOUT.log
> /usr/bin/rhts-test-runner.sh: line 4: 11219 Segmentation fault      cat $OUTPUTFILE
> /usr/bin/rhts-test-runner.sh: line 4: 11221 Segmentation fault      rhts-sync-set -s DONE
> /usr/bin/rhts-test-runner.sh: line 4: 11222 Segmentation fault      rhts-sync-block -s DONE $SERVERS $CLIENTS $DRIVER
> /usr/bin/rhts-test-runner.sh: line 4: 11223 Segmentation fault      rhts-test-update $RESULT_SERVER $TESTID finish
> /usr/bin/rhts-test-runner.sh: line 4: 11225 Segmentation fault      rhts-restore
> /usr/bin/rhts-test-runner.sh: line 4: 11226 Segmentation fault      logger -s "$0 report_finish stop..."

Seeing them in so many places it might be a faulty memory, but harness should handle that, instead of hanging what seems without reason.

Comment 1 Marian Csontos 2010-08-25 07:13:12 UTC
Note: The segfault problem is related to F12-i386 distro only, it does not happen on other distros. Shall look at that too.

Comment 2 Marian Csontos 2010-08-31 12:03:00 UTC
Fix tested in a VM. Brewing RPMs to test on stage.


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