178eda0f816c2044f1e5f4a87aa890c4c2c115d9 kent Tue Oct 1 20:08:43 2024 -0700 Seperating out the user initialization into a script and adding groups to it too. diff --git src/hg/cirm/cdw/install/README src/hg/cirm/cdw/install/README index 5fbcadf..353c660 100644 --- src/hg/cirm/cdw/install/README +++ src/hg/cirm/cdw/install/README @@ -49,37 +49,35 @@ to make it private 9) Create a cdw user for the mariaSql database and also a cdw database that the cdw user has full authorities for. 10) Copy over the validation data from hgwdev cd /data/cirm scp -rp hgwdev:/data/cirm/valData . 11) Create the table structure for the cdw database by logging into mysql, doing hgsqladmin create cdw hgsql cdw < ~/kent/src/hg/cirm/cdw/lib/cdw.sql; 12) Populate the settings table by doing insert into cdwSettings set name='prefix',val='SSPG'; insert into cdwSettings set name='schema',val='/data/cirm/valData/tags.schema'; Note these lines control the prefix to the accession numbers for the files, and the tagStorm schema respectively. -13) Set up users for cdw system, people who can submit files: - cdwCreateUser kent@soe.ucsc.edu - hgsql -e "update cdwUser set isAdmin=1 where email='kent@soe.ucsc.edu'" cdw - cdwCreateUser mhaeussl@ucsc.edu - cdwCreateUser wisulliv@ucsc.edu -14) Run script to load up validations: - ~/kent/src/hg/cirm/cdw/initQa +13) Set up users and groups for cdw system, people who can submit files and groups they + belong to. You'll need to edit this script for different installations. + ~/kent/src/hg/cirm/cdw/install/initUsersGroups +14) Run script to load up validation and quality assurance files + ~/kent/src/hg/cirm/cdw/install/initQa 15) Find the following bioinformatics programs and make them accessible to the cdw user. tabix (version 0.2.5 is what we use) bgzip (part of Heng Li's tabix kit) bowtie (we use version 1.3.1) 16) Set up the bowtie indexes in ramdisk. (redo on reboot) rsync -apv /data/cirm/valData/ramdisk/ /dev/shm/btData/ 17) Start up the daemons (redo on reboot) cd /data/cirm/cdw cdwRunDaemon cdw cdwJob 30 -log=cdwQa.log Sometimes the daemons will crash out. Usually it's on a new data type. Do a ps -u cdw to see if this has happened. If so then do killall cdwRunDaemon have a look at the cdwJob.log, and possibly the latest entries in the cdwJob database table, and then do cdwRunDaemon again as above to restart.