ERROR: could not open file "../log/rollout_gen_data.log" for reading: No such file or directory about tpc-ds HOT 10 CLOSED

This benchmark works with GP6.

Does this file exist?
/pivotalguru/TPC-DS/06_single_user_reports/../log/rollout_gen_data.log

What operating system version are you using?

from tpc-ds.

cat /etc/redhat-release
CentOS Linux release 7.7.1908 (Core)

no, this file (rollout_gen_data.log) is not created
...and after debugging today I'm starting to suspect that somehow "printf >> logfile" doesn't work in functions.sh at the end of log() function. It just quietly does not execute. Sounds crazy, I know

from tpc-ds.

Does this output "foo bar"?
printf "foo bar\n"

from tpc-ds.

Surely it does.
I even tried to create some stripped down bash construct similar to your code, consisting of a few .sh files in different dirs starting each other. And inside were only PWD variables(BASH_SOURCE[0] magic), printf statements outputting some debug info and one simple function in a func.sh sourced within each of those little bash-scripts using "$PWD/func.sh", "$PWD/../func.sh", etc. The function in its turn "logged" a couple of messages to a file for me with printf "sometext\n" >> somefile. It mimics all the parts of your code I thought could potentially cause trouble on my system and yet it works like a charm!

I started execution with "sudo nohup ... &", gave same permissions to files, kept similar directory structure to make sure everything is exactly the same. It works as it should.

I'm still missing something... rollout_* logs are not created for some another reason.

from tpc-ds.

Try becoming root. The easiest way is:

sudo bash
nohup ./tpcds.sh > tpcds.log 2>&1 < tpcds.log &

Or you can use this command to become root:

sudo su -
nohup ./tpcds.sh > tpcds.log 2>&1 < tpcds.log &

Don't forget to add the "-" after "su".

from tpc-ds.

The first thing I checked was file permissions and user privileges, so we had already tried that last week. "Sudo bash" -- exactly this way...
Unfortunately it makes no difference. I wish it was that easy.

from tpc-ds.

What timezone are you in? I can host a zoom meeting to debug this issue if you like.

from tpc-ds.

Well, I think I found something finally!
Your function is simply named log() and called log in the rollout.sh scripts.
But typing log in the terminal on this particular system outputs this:
...
Yeah, that's right, three dots )

Now let's look at this portion of the tpcds.log:

139.tpcds.39.sql
myfilename: /pivotalguru/TPC-DS/01_gen_data/../05_sql/139.tpcds.39.sql
pos: 28
COMPLETE: dsqgen scale 1
...
/pivotalguru/TPC-DS/02_init/rollout.sh
check optimizer
check analyze_root_partition
check gp_autostats_mode

See those three dots? That's exactly where it calls log() function but instead bumps into that "log" thing from the shell.

And this is the root of all my problems:

# type log
log is a function
log ()
{
    printf "%s...\n" "$*"
}

A function for adding "..." at the end of anything. Extremely useful

Those CentOS's were deployed from cloud template images... who could've guessed they contain such interesting modification

from tpc-ds.

Sounds like an easy fix for you then. Do you need anything else before I close this issue?

from tpc-ds.

No, let's consider this resolved. Many thanks for your willingness to help!

from tpc-ds.