Hi Daniel and Jacek,

If QSERV_RUN_DIR is an empty directory, you have then to run first :

qserv-configure -R ~/qservDev/qserv-run --prepare

This command will copy configuration templates in QSERV_RUN_DIR, and 
attach it to the current Qserv instance (i.e. the one providing 
qserv-configure.py)

Please note that :
qserv-configure --all
include this step.

I agree that I should write a better documentation for the configuration 
tool, but maybe we should use first your useful user feedbacks in order 
to define a more intuitive interface ?
(For now I let the tool open so that each configuration step can be 
called separately, but maybe it's too much.)

Thanks,

Fabrice

On 09/20/2014 12:55 AM, Daniel L. Wang wrote:
> On 09/18/2014 09:52 AM, Jacek Becla wrote:
>> What am I missing? I tried to test the latest master,
> ... snip...
>>
>> qserv-configure.py -R ~/qservDev/qserv-run
>> INFO: Qserv configuration tool
>> =======================================================================
>> INFO: Reading meta-configuration file
>> INFO: Defining main directory structure
>> INFO: Qserv directory structure creation succeeded
>> INFO: Qserv symlinks creation for externalized directories succeeded
>> INFO: Creating configuration files in 
>> /usr/local/home/becla/qservDev/qserv-run/etc and scripts in 
>> /usr/local/home/becla/qservDev/qserv-run/tmp
>> INFO: Creating configuration using templates files
>> CRITICAL: Template "QSERV_TESTDATA_DIR" in file 
>> /usr/local/home/becla/qservDev/qserv-run/templates/server/etc/qserv-client.conf 
>> is not defined in configuration tool
>>
> For the record, Jacek and I discovered that if we add the "--all" 
> option to qserv-configure.py, things seem to work. Neither of us are 
> really sure why it works, except that it was in the instructions. The 
> page says that "--all" specifies "Clean QSERV_RUN_DIR and fill it with 
> mono-node configuration data", which seems like you don't need it if 
> QSERV_RUN_DIR is an empty directory, but, well, you still do.
>
> So:
> qserv-configure.py -R ~/qservDev/qserv-run --all
> or
> qserv-configure.py -R ~/qservDev/qserv-run -a
> was the right approach.
>
> Hope this helps someone in the future,
> -Daniel
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the QSERV-L list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1