 |
 |
Hi Jeff, This bug was found and fixed recently. Could you please set RELEASE=qserv-dev and then run: # loadLSST.bash must have been sourced before running this (see above) eups distrib install --tag $RELEASE qserv_distrib setup qserv_distrib -t $RELEASE This will upgrade and setup cutting-edge Qserv version. qserv-configure should then work fine. Please let me know if it works. Cheers On 02/18/2016 09:19 AM, Jeff Tseng wrote: > > Hi Fabrice, > > I was trying again to clean up my server and install the latest qserv, > but qserv-configure.py refused to work, reporting a failure in > mysql_install_db. > > When I look at the mysql.sh script in the run directory, it appears to > me MYSQL_DIR (or, more specifically, --basedir) is pointing to the > build directory of mariadbclient rather than mariadb. The failure > seems to come from the fact that mysqld can't be found in > mariadbclient (which makes sense). > > I can run a stand-alone mysql_install_db command with a corrected > --basedir option, pointing to the mariadb directory, but of course > when trying to run this as part of the suite of setup scripts, > mysql.sh will be created afresh from the template. I can trace the > template back to admin/templates/installation/qserv-meta.conf, but at > that point I lost the trail and can't figure out where MYSQL_DIR (or > the corresponding config element) is set. Possibly because it's done > by scons or eups (can't figure out which right now) in the build or > install step. > > So I guess I have two questions: > > 1. where is MYSQL_DIR set in the build process? > 2. should it really be pointing to mariadbclient rather than mariadb? > > Cheers, > > Jeff > > ######################################################################## 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