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.