Hi Jiri, can I have access to sosreport file?

Hi Jiri,

I tried to reproduce several times but still not able, I can see the HTML report  generated all time. Which version of engine-db-query are you using?

# su postgres
bash-4.2$ cd /tmp/
bash-4.2$ rhv-log-collector-analyzer sosreport-LogCollector-20180725114347.tar.xz
Preparing environment:
======================
Temporary working directory is /tmp/tmp.ieb7ixCiB5
Unpacking postgres data. This can take up to several minutes.
sos-report extracted into: /tmp/tmp.ieb7ixCiB5/unpacked_sosreport
pgdump extracted into: /tmp/tmp.ieb7ixCiB5/pg_dump_dir
Welcome to unpackHostsSosReports script!
Extracting sosreport from hypervisor slot-1.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-1.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-5a.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-5a.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-5c.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-5c.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-5d.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-5d.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-6a.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-6a.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-6b.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-6b.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-6c.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-6c.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-6d.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-6d.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-7a.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-7a.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-7b.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-7b.rhev.lab.eng.brq.redhat.com

Extracting sosreport from hypervisor slot-7c.rhev.lab.eng.brq.redhat.com in /tmp/ovirt-log-collector-analyzer-hosts/slot-7c.rhev.lab.eng.brq.redhat.com

Creating a temporary database in /tmp/tmp.ieb7ixCiB5/postgresDb/pgdata. Log of initdb is in /tmp/tmp.ieb7ixCiB5/initdb.log

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
LOG:  redirecting log output to logging collector process
HINT:  Future log output will appear in directory "pg_log".
Importing the dump into a temporary database. Log of the restore process is in /tmp/tmp.ieb7ixCiB5/db-restore.log

Generating reports:
===================
Generated analyzer_report.html

Cleaning up:
============
Stopping temporary database
Removing temporary directory /tmp/tmp.ieb7ixCiB5

$ du -sh analyzer_report.html 
232K	analyzer_report.html

$ elinks analyzer_report.html

$ rpm -qa | grep rhv-log-collector-analyzer
rhv-log-collector-analyzer-0.1.2-0.el7ev.noarch

$ rpm -qa | grep engine-db-query
engine-db-query-1.1.0-0.el7ev.noarch

Looks like I have reproduced the issue.

Basically, if users run **in sequence**:

# rhv-log-collector-analyzer --live
(generated as root:root /tmp/engine-db-query.log)

and later:

# su postgres
$ rhv-log-collector-analyzer sosreport-file.tar.xz

(will fail to write into /tmp/engine-db-query.log) and will stop
the script as our bash script contain -e.  

Jiri, a simple test is:

Remove the -e from /usr/share/rhv-log-collector-analyzer/analyzer/produceReport/produceReport.sh and execute above, you will see errors like:

"""
IOError: [Errno 13] Permission denied: '/tmp/engine-db-query.log'
"""

I am already working in this enhancement for engine-db-query/rhv-log-collector-analyzer but please let me know if this is the same issue.

Thanks!

(In reply to Douglas Schilling Landgraf from comment #4)
> Looks like I have reproduced the issue.
> 
> Basically, if users run **in sequence**:
> 
> # rhv-log-collector-analyzer --live
> (generated as root:root /tmp/engine-db-query.log)
> 
> and later:
> 
> # su postgres
> $ rhv-log-collector-analyzer sosreport-file.tar.xz
> 
> (will fail to write into /tmp/engine-db-query.log) and will stop
> the script as our bash script contain -e.  
> 
> Jiri, a simple test is:
> 
> Remove the -e from
> /usr/share/rhv-log-collector-analyzer/analyzer/produceReport/produceReport.
> sh and execute above, you will see errors like:
> 
> """
> IOError: [Errno 13] Permission denied: '/tmp/engine-db-query.log'
> """
> 
> I am already working in this enhancement for
> engine-db-query/rhv-log-collector-analyzer but please let me know if this is
> the same issue.
> 
> Thanks!

There's no point to test this - /tmp is world writtable, you _must_ use unique filename and not to assume your filename won't be there. An assumption is always wrong.

ok, rhv-log-collector-analyzer-0.1.5-0.el7ev.noarch

# elinks -dump 1 /var/lib/pgsql/analyzer_report.html | sed -n '/Approximate version of initially installed engine/,+2p'
   Approximate version of initially installed engine

   3.1

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2640