Jacek,
The run directory is on lsst-db1:~danielw/t4/run
I did setup qserv_testdata, but apparently the version I had was bad.
I've just now realized that there are at least *three* possible eups
repositories to try, and that eups sometimes wants --repository and
elsewhere it wants -S (because --repository is deprecated). I think the
third repo was what I failed to realize. It's all very confusing to me.
-Daniel
On 09/18/2014 07:27 PM, Jacek Becla wrote:
> It is puzzling, yes I use the same version of the code as you.
>
> Where do you have your qserv-run dir?
>
> Jacek
>
>
>
>
>
> On 09/18/2014 05:01 PM, Daniel L. Wang wrote:
>> Jacek,
>>
>> I didn't encounter your error, but do you have qserv_testdata setup?
>>
>> For some reason, I'm having a different problem. qserv-configure.py
>> bails out during the installation of scisql. This looks related to the
>> use of eups-distributed scisql.
>> -----------
>> -- Installing and configuring sciSQL
>> --
>> INFO: stderr :
>> --
>> /usr/local/home/danielw/t4/run/tmp/configure/scisql.sh: line 21:
>> ./configure: No such file or directory
>> --
>> CRITICAL: Error code returned by command :
>> /usr/local/home/danielw/t4/run/tmp/configure/scisql.sh
>> -------------
>>
>> At this point, I dug into scisql.sh, and noticed that it does cd
>> $SCISQL_DIR and then ./configure..., which fails because SCISQL_DIR
>> (/usr/local/home/danielw/t4/Linux64/scisql/0.3+5) seems to contain
>> (almost) nothing of value for qserv. That is, the eups-installed scisql
>> seems useless for qserv. I have a feeling that there is another scisql
>> version in eups that isn't useless, but I don't know where it is.
>>
>> But if there isn't another eups scisql, I don't see how scisql.sh could
>> work. DM-602 introduced a change to rely on an eups-installed scisql,
>> and I do see in JIRA that someone tested DM-602 in a disconnected
>> environment, but did it get tested on a fresh install over the network?
>> The scisql.sh template hasn't changed since DM-602, so I don't see how
>> it worked back then.
>>
>> For the record, I'm testing the current tip of master: e4f80b629 , which
>> gives the mangled eups version: master-ge4f80b629f
>>
>> What am I missing?
>>
>> -Daniel
>>
>>
>> On 09/18/2014 09:52 AM, Jacek Becla wrote:
>>> Fabrice,
>>>
>>> What am I missing? I tried to test the latest master,
>>> here is what I am getting:
>>>
>>>
>>> setup -r .
>>> setup xrootd 4.0.0rc3-qsClient2
>>> setup qserv_testdata
>>> eupspkg -er build
>>> eupspkg -er install
>>> eupspkg -er decl
>>> setup qserv master-ge4f80b629f
>>>
>>> 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
>>>
>>>
>>> ---
>>>
>>>
>>> qserv-configure.py
>>> INFO: Qserv configuration tool
>>> =======================================================================
>>> INFO: Reading meta-configuration file
>>> CRITICAL: qserv configuration file not found :
>>> /usr/local/home/becla/qserv-run/2014_09.0/qserv.conf
>>>
>>>
>>> You have been changing this code ~Sept 5. Does it work for you?
>>>
>>> Jacek
>>>
>>> ########################################################################
>>>
>>> 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
|