Hi Jacek,

MYSQLD_SOCK but QSW_DBSOCK are set in qserv_run_dir/etc/init.d/xrootd, 
so they shouldn't be in your environment.
If you want to launch xrootd by hand (i.e. not using init.d/xrootd) you 
need to create them in your environment:
source ~/qserv-run-dir/etc/sysconfig/qserv
and then:
export all environment variables which are on top of 
qserv_run_dir/etc/init.d/xrootd
I agree taht this operation is a bit complex for now and I think it 
could be quite easily simplified if needed.

Cheers,

Fabrice



On 07/10/2015 08:29 PM, Jacek Becla wrote:
> Hi Fabrice,
>
> I had MYSQLD_SOCK but QSW_DBSOCK was not set. I guess running
> qserv-configure would have solved it. Now I am on a new stack
> and it is working fine.
>
> Interestingly, neither QSW_DBSOCK nor MYSQLD_SOCK are present
> in my environment (where I have new working stack)
>
> thanks
> Jacek
>
>
> On 07/10/2015 12:15 AM, Fabrice Jammes wrote:
>> Hi Jacek,
>>
>> The socket parameter should be in qserv-run-dir (i.e.
>> /home/qserv/qserv-run/git below), not in /var/lib/mysql/mysql.sock as
>> printed in your log.
>>
>> xrootd deduce this value from this env variable:
>> QSW_DBSOCK (=/home/qserv/qserv-run/git/var/lib/mysql/mysql.sock)
>>
>> This env variable is set in ~/qserv-run/git/etc/sysconfig/qserv (see
>> MYSQLD_SOCK)
>> this file is read by ~/qserv-run/git/etc/init.d/xrootd
>>
>> maybe you can print/debug value of QSW_DBSOCK in
>> ~/qserv-run/git/etc/init.d/xrootd above to see what happen.
>>
>> Cheers,
>>
>> Fabrice
>>
>> On 07/10/2015 12:27 AM, Jacek Becla wrote:
>>> I am puzzled by a problem with restarting xrootd that just popped up:
>>>
>>> 0 [0x7f669d392720] INFO root null - SsiService starting...
>>> 1 [0x7f669d392720] FATAL root null - Configuration invalid: Unable to
>>> connect to MySQL with config:[host=invalidhostname_unresolved,
>>> port=9999, usr=qsmaster, pass=, dbName=qservScratch,
>>> socket=/var/lib/mysql/mysql.sock]
>>>
>>>
>>> Maybe I need to switch to the new stack, or things got confused
>>> because of new xrootd ssi or multi-node testing code? Anyway, if
>>> anyone has a quick suggestions or knows what the problem is, let
>>> me know while I am switching to 2015_06 stack
>>>
>>> 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

########################################################################
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