OICR-Configuring the development machine
Contents
- 1 Address
- 2 Hardware
- 3 Server Configuration
- 3.1 Preparing directories and users
- 3.2 User and group accounts
- 3.3 Directories
- 3.4 Configure the FTP/Mirroring directory THIS IS NOT DONE YET
- 3.5 Install Perl modules
- 3.6 Build ePCR NOT DONE
- 3.7 Installing Acedb
- 3.8 Installing Ace.pm (Classic WormBase site)
- 3.9 Installing BioPerl NOT DONE
- 3.10 Installing and configuring MySQL
- 3.11 Installing Apache and mod_perl
- 3.12 Installing the Generic Genome Browser
- 3.13 Installing BLAT
- 3.14 Installing BLAST
- 3.15 Installing Analog and Report Magic (optional)
- 4 Configuring the WormBase installation
- 5 Troubleshooting
- 5.1 Is the acedb socket server starting?
- 5.2 Is the acedb socket server crashing?
- 5.3 "Internal Server Error"
- 5.4 The banner displays but the decorative worm images are broken
- 5.5 Installing scripts to verify that the servers are running
- 5.6 INSTALL libgd and GD.pm (if installation of GD.pm failed)
- 5.7 Install XML libraries and modules
- 6 AUTHOR
Address
wb-dev.oicr.on.ca
Hardware
The WormBase development server at OICR is a virtual server with the following stats:
- Debian Linux
- 500 GB disk space (mounted at /dev/hda1)
- 4 GB RAM
Server Configuration
All WormBase components are collected under a single directory: /usr/local/wormbase
$ ls /usr/local/wormbase acedb/ // The Acedb database (including bin directory) util/ // Utility components such as e-pcr and wublast extlib/ // Third party Perl libraries website-classic // The classic WormBase website website // The new-and-improved website!
Preparing directories and users
WormBase uses several user accounts for directory and server permissions. You will need to create these users and several preliminary directories. Creating a new user and group varies among Unix flavors. On most Linux systems, the following commands will create the new groups. You should have sudo privilege to execute these commands.
User and group accounts
These users should not have a login password. They are to establish privileges only.
- acedb group
This is the group that will have write privileges to the acedb directory tree. Acedb administrators should be added to this group.
$ /usr/sbin/groupadd acedb
- acedb user
This is the user that the acedb server will run as. It should be a member of the acedb group.
$ /usr/sbin/useradd -g acedb -d /usr/local/wormbase/acedb acedb
This useradd command also adds the new acedb user to the acedb group. Note that the acedb user's home directory was set to /usr/local/acedb, a directory which will be created in the next step.
- wormbase group
This is a group that will have write privileges to the wormbase directory tree. WormBase administrators and authors should be added to this group.
$ /usr/sbin/groupadd wormbase
This would be a good time to add yourself to the acedb and wormbase groups.
$ /usr/sbin/usermod -a -G acedb,wormbase [your_login_name]
[The '-a' argument keeps this command from deleting other, preexisting group memberships.]
You may need to re-login for these changes to take effect. Use the groups command to check which groups you are a member of:
% groups
Directories
The root container for all things WormBase:
- /usr/local/wormbase, owner=root group=wormbase mode=drwxrwsr-x
$ mkdir /usr/local/wormbase $ chgrp wormbase /usr/local/wormbase $ chmod 2775 /usr/local/wormbase
- External Perl libraries: /usr/local/wormbase/extlib, owner=tharris group=wormbase mode=drwxrwsr-x
$ mkdir /usr/local/wormbase/extlib $ chgrp wormbase /usr/local/wormbase/extlib $ chmod 2775 /usr/local/wormbase/extlib
- The "classic" website: /usr/local/wormbase/website-classic, owner=root group=wormbase mode=drwxrwsr-x
$ mkdir /usr/local/wormbase/website-classic $ chgrp wormbase /usr/local/wormbase/website-classic $ chmod 2775 /usr/local/wormbase/website-classic
- /usr/local/wormbase/website-classic/logs, owner=root group=wormbase mode=drwxrwsr-x
$ mkdir /usr/local/wormbase/website-classic/logs $ chgrp wormbase /usr/local/wormbase/website-classic/logs $ chmod 2775 /usr/local/wormbase/website-classic/logs
- /usr/local/wormbase/website-classic/cache, owner=nobody group=nobody mode=drwxrwsr-x
$ mkdir /usr/local/wormbase/website-classic/cache $ chown nobody:nobody /usr/local/wormbase/website-classic/cache $ chmod 2775 /usr/local/wormbase/website-classic/cache
- The "util" directory contains components that apply to both the classic and updated site, like wublast and e-pcr.
- /usr/local/wormbase/util/wublast, owner=root group=wormbase mode=drwxrwsr-x
$ mkdir /usr/local/wormbase/util/wublast $ chgrp wormbase /usr/local/wormbase/util/wublast $ chmod 2775 /usr/local/wormbase/util/wublast
- /usr/local/wormbase/acedb, owner=acedb group=acedb,mode=drwxrwsr-x
$ mkdir /usr/local/wormbase/acedb $ chown acedb:acedb /usr/local/wormbase/acedb $ chmod 2775 /usr/local/wormbase/acedb
Configure the FTP/Mirroring directory THIS IS NOT DONE YET
- ~ftp/pub/wormbase, owner=root group=wormbase mode=drwxrwsr-x
$ mkdir ~ftp/pub/wormbase $ chgrp wormbase ~ftp/pub/wormbase $ chmod 2775 ~ftp/pub/wormbase
You may ignore this step if you do not plan to mirror the WormBase FTP site. In the examples below, the -p option is used to create the intermediate parents of directories if they don't already exist. If your mkdir doesn't support this option, you will need to create the intermediate directories manually.
Install Perl modules
NOTE: It might be preferable to set up TWO seperate extlib directories, one for each site. To do this, maybe I could set up multiple CPAN configuration files.
(Note: It might by necessary to install gcc, curl, wget, unzip, bzip2, etc via apt-get before beginning)
Set up CPAN to build modules in the local library path (/usr/local/wormbase/extlib):
perl -MCPAN -e shell // Note that you DO NOT need to be sudo... cpan> o conf init (only necessary if not prompted)
For the Makefile.PL arguments, enter
INSTALL_BASE=/usr/local/wormbase/extlib \
And for Build.PL enter
--install_base /usr/local/wormbase/extlib
Prepare/update your CPAN:
cpan> install CPAN cpan> reload CPAN
Before installing modules, you may need to set your PERL5LIB environment variable to point to include the extlib directory.
emacs ~/.bash_profile export PERL5LIB /usr/local/wormbase/extlib:/usr/local/wormbase/extlib/lib:/usr/local/wormbase/extlib/lib/perl5
Install the following Perl modules via CPAN. Note that you DO NOT AND SHOULD NOT be sudo..
perl -I/usr/local/wormbase/extlib/lib -MCPAN -e shell
YAML LWP ExtUtils::MakeMaker Bundle::CPAN Cache::Cache Cache::FileCache CGI CGI::Session // CPAN installation fails in local dirs; tries to install man3 in system path. CGI::Cache Date::Calc Date::Manip // CPAN installation fails in local dirs; tries to install man3 in system path. --> Build and install Berkeley DB wget http://download.oracle.com/berkeley-db/db-4.7.25.tar.gz tar xzf db* cd db* cd build_unix ../dist/configure make sudo make install DB_File DBI DBD::mysql (mysql must be installed first) Digest::MD5 GD // 'sudo apt-get install libgd2-xpm-dev libgd2-xpm' first GD::SVG GD::Graph HTML::TokeParser IO::Scalar IO::String Image::GD::Thumbnail MIME::Lite Net::FTP Proc::Simple readline Search::Indexer SOAP::Lite Statistics::OLS Storable SVG SVG::Graph Test::Pod Text::Shellwords Time::Format WeakRef XML::SAX XML::Parser XML::DOM XML::Writer XML::Twig XML::Simple
Installing additional Perl modules
NOTE: To install any additional Perl modules later make sure that:
1. Your CPAN is configured to install to /usr/local/wormbase/extlib
You can set this in ~/.cpan/CPAN/MyConfig.pm
'makepl_arg' => q[INSTALL_BASE=/usr/local/wormbase/extlib],
OR
2. If building by hand, you call Makefile.PL as:
perl Make.PL INSTALL_BASE=/usr/local/wormbase/extlib
Build ePCR NOT DONE
- e-PCR (modified version, required for e-PCR search page)
This is located in the directory /usr/local/wormbase/e-PCR, which will come into existence after the WormBase site update program wb_update_wormbase.pl has been successfully run (see below for details). Once the directory has been generated, run:
$ cd /usr/local/wormbase/e-PCR # Edit 'makefile' to run install rather than ginstall, which doesn't exist on Fedora Linux $ make $ make install # or just run 'install e-PCR /usr/local/bin'
The file /usr/local/wormbase/e-PCR/README-Wormbase describes the changes that were made to the original e-PCR distribution.
Installing Acedb
... from a binary package
$ cd /usr/local/wormbase/acedb/src $ curl -O ftp://ftp.sanger.ac.uk/pub/acedb/SUPPORTED/ACEDB-binaryLINUX_4.4.9.39.tar.gz $ curl -O ftp://ftp.sanger.ac.uk/pub/acedb/SUPPORTED/ACEDB-serverLINUX_4.4.9.39.tar.gz $ cd ../ ; mkdir bin-4.9.39 $ ln -s bin-4.9.39 bin ; cd bin $ tar xzf ../src/ACEDB*
Make sure that these files are executable and owned by root:
$ chown root:root ~acedb/bin/* # This sets both owner and group to 'root'.
... from source
$ tar xzf ACEDB-source* // CAUTION: Tarbomb. // Install a whole bunch of things: libgtk2.0-0 libgtk2.0-dev libglib, byacc, etc, etc // Modify the makefile: create a target for server programs (xace tace saceserver sgifacerver) // This is all I care about: SERVERS = xace tace saceserver sgifaceserver saceclient servers: $(SERVERS) $ export ACEDB_MACHINE=LINUX_4 $ make servers $ cp tace xace sgifaceserver saceserver saceclient ~acedb/bin/.
Testing AceDB
At this point, you can test whether the socket server runs correctly. Provided that you have added yourself to the acedb group, you can run the following command:
% ~acedb/bin/sgifaceserver ~acedb/wormbase // Database directory: /usr/local/wormbase/acedb/wormbase // Shared files: /usr/local/acedb // #### Server started at 2001-07-23_16:42:31 // #### host=mondseer.cshl.org listening port=23100 // #### Database dir=/usr/local/acedb/elegans // #### Working dir=/usr/local/acedb/elegans // #### clientTimeout=600 serverTimeout=600 maxKbytes=0 autoSaveInterval=600
// Server listening socket 28 created
The line "listening port=23100" indicates that the server is listening to port 23100. Open a new terminal window and use saceclient to confirm that you can communicate with the server:
% ~acedb/bin/saceclient localhost -port 23100 Please enter userid: anonymous Please enter passwd: acedb@localhost> find Sequence // Response: 65 bytes.
// Found 236493 objects in this class // 236493 Active Objects acedb@localhost> quit // Closing connection to server. // Client sent termination signal by server. // Response: 13 bytes. // A bientot // Please report problems to acedb@sanger.ac.uk // Bye
Installing Ace.pm (Classic WormBase site)
Ace.pm provides programmatic access to Acedb. You can install it via CPAN:
cpan> install Ace
During configuration, choose option (3), then set the remaining variables as follows:
Site-specific configuration files: /usr/local/wormbase/website-classic/conf CGI path: /usr/local/wormbase/website-classic/cgi-bin HTML path: /usr/local/wormbase/website-classic/html
Installing BioPerl NOT DONE
You may install BioPerl either using anonymous CVS or by downloading and installing the most recent stable core.
To install BioPerl from the current stable release (which was once recommended):
% wget http://bioperl.org/DIST/current_core_stable.tar.gz % gunzip -c cur* | tar xvf - % cd bioperl-1.4 % perl Build.PL % ./Build test % sudo ./Build install
However, in March 2006 this stable release did not work with GBrowse-1.64. So the default choice is currently to install BioPerl from CVS. Installing from CVS will give you the latest version of BioPerl, but may also include unresolved bugs and experimental code.
% cvs -d :pserver:cvs@cvs.open-bio.org:/home/repository/bioperl login when prompted for the password, type 'cvs' % cvs -d:pserver:cvs:cvs@cvs.open-bio.org:/home/repository/bioperl co bioperl-live % cd bioperl-live % perl Build.PL % ./Build test % sudo ./Build install
(Note that BioPerl once used the old system of "perl Makefile.PL; make; make test; sudo make install", but that this has been superceded by the brave new world of Build.pm.)
This will create a directory named bioperl-live. In the future, when you wish to update to the most recent version, simply type "cvs update" in the bioperl-live directory.
Install BioPerl in the usual way, by running "perl Makefile.PL", "make", "make test" and "make install".
Finally, go into CPAN again and run:
cpan> install Bio::Das
Installing and configuring MySQL
Installing MySQL
If working on a computer without pre-existing MySQL in its distribution, one can install from a binary distribution (without using a package manager). The commands are as follows (assuming an unpacked mysql distrbution!):
$ wget http://mirror.trouble-free.net/mysql_mirror/Downloads/MySQL-5.1/mysql-5.1.35-linux-x86_64-glibc23.tar.gz $ groupadd mysql $ useradd -g mysql mysql $ cd /usr/local $ sudo gunzip < /PATH/TO/MYSQL-VERSION-OS.tar.gz | tar xvf - $ sudo ln -s FULL-PATH-TO-MYSQL-VERSION-OS mysql $ cd mysql $ sudo scripts/mysql_install_db --user=mysql $ sudo chown -R root . $ sudo chown -R mysql data $ chgrp -R mysql . $ bin/mysqld_safe --user=mysql &
# So the server starts up automatically, do: $ sudo cp support-files/mysql.server /etc/rc.d/init.d/mysql $ cd /etc/rc3.d $ sudo ln -s ../init.d/mysqld S99mysqld $ cd ../rc5.d $ sudo ln -s ../init.d/mysqld S99mysqld
# Start the server by: $ sudo /etc/rc.d/init.d/mysql start # Set up a root password $ mysqladmin -uroot password PASSWORD
Set up mysql permissions
# mysql -u root -pPASSWORD mysql> grant select on elegans.* to nobody@localhost;
Repeat for: c_briggsae, c_japonica, c_remanei, c_brenneri, p_pacificus, b_malayi, c_elegans_gmap, c_elegans_pmap, autocomplete
Installing Apache and mod_perl
sudo apt-get install apache2 sudo apt-get install libapache2-mod-perl2
Installing the Generic Genome Browser
This is a CGI script and some Perl modules that use Bio::DB::GFF and Bio::Graphics to create the main WormBase genome display. It lives at www.gmod.org. Like BioPerl, GBrowse can be installed via anonymous CVS or from the current stable release. As of June 2006, the current stable release (1.64) is the only one that actually works.
Via the latest stable release: $ wget http://easynews.dl.sourceforge.net/sourceforge/gmod/Generic-Genome-Browser-1.64.tar.gz $ gunzip -c Gene* | tar xvf -
CVS doesn't work yet (as of June 2006), but:
Via CVS: $ cvs -d:pserver:anonymous@gmod.cvs.sourceforge.net:/cvsroot/gmod login (When prompted for a password for anonymous, simply press the Enter key.) $ cvs -d:pserver:anonymous@gmod.cvs.sourceforge.net:/cvsroot/gmod co Generic-Genome-Browser
Note that: (1) version 1.64 is the latest stable release as of June 2006, but later versions will probably exist; (2) the clumsy "wget-longURL" command is a way of getting around Sourceforge's lack of easy, reliable URLs available to users for source-code packages.
On a Linux distribution using SELinux security (such as Fedora Core 4), compilation will fail until SELinux is in some way circumvented. One way to do this is:
$ setsebool -P httpd_disable_trans 1 $ /usr/local/apache/bin/httpd restart
Then enter the unpacked directory or that fetched by CVS and run the following incantation to install it in the proper place for WormBase:
$ perl Makefile.PL HTDOCS=/usr/local/wormbase/html \ CGIBIN=/usr/local/wormbase/cgi-perl/seq \ CONF=/usr/local/wormbase/conf \ --SELINUX=1 # disables SELinux $ make $ make install
The long Makefile.PL incantation can be cut-and-pasted from this document into the command line. The last argument of Makefile.PL is only needed if SELinux exists on the system.
Installing BLAT
Jim Kent's BLAT (blast-like alignment tool) is a fast nucleotide aligner used by the blast search page. If you do not plan to support blast searches, you may safely skip this step.
# mkdir -p /usr/local/blat/bin ; cd /usr/local/blat/bin % wget http://www.soe.ucsc.edu/~kent/exe/linux/blatSuite.33.zip (for Intel Linux) % unzip blatSuite.33.zip % rm blatSuite.33.zip version.doc 11.ooc
Note that this choice gives precompiled binaries for an Intel-based Linux distribution as of March 2006. It would probably be worth checking http://www.soe.ucsc.edu/~kent/exe/linux to see if there is a more up-to-date version than 33. Also, other operating systems will need other binaries. E.g., for Mac OS X, instead run:
% wget http://www.soe.ucsc.edu/~kent/exe/osX/blatSuite.33.zip
For other types of operating systems (e.g., Linux on Opteron-based machines), see http://www.soe.ucsc.edu/~kent/exe/ for the available choices.
The blat server will be started automatically by the update script. For reference, the blat server is launched using the following command.
% /usr/local/blat/bin/gfServer start localhost 2003 \ /usr/local/wormbase/blat/*.nib & > /dev/null 2>&1
Installing BLAST
The Blast page requires WU-BLAST. This is a closed-source derivative of NCBI's BLAST. However, WU-BLAST is free to academic users (with licensing) and is thought to have performance advantages over NCBI-BLAST; it can be downloaded from http://blast.wustl.edu/. A typical choice of WU-BLAST for Linux is blast2.linux26-i686.tar.gz.
Conversely, the Blast page can be deactivated if you don't want to provide BLAST searches at your site.
By default, WormBase expects WU-BLAST to be installed in /usr/local/wublast. This is the directory structure used by WormBase:
% ls -l /usr/local/wublast ls -l /usr/local/wublast total 72 lrwxrwxrwx 1 root root 18 May 7 12:26 BLOSUM62 -> matrix/aa/BLOSUM62 -rw-r--r-- 1 root root 46789 Feb 5 1998 HISTORY -rw-r--r-- 1 root root 6648 Mar 4 1997 README drwxr-xr-x 2 root root 4096 May 7 12:46 bin/ lrwxrwxrwx 1 root root 25 Jul 24 08:20 databases -> /usr/local/wormbase/blast/ drwxr-xr-x 2 root root 4096 Jan 27 2000 filter/ drwxr-xr-x 4 root root 4096 Oct 4 1998 matrix/
which can be set up in this manner (adapt to your system):
$ cd /usr/local/wublast $ zcat /usr/local/TGZ/blast2.linux26-i686.tar.gz | tar xf - $ chown -R root:root * $ mkdir bin $ mv *fasta tblast* blast* *db xd* memfile pam wu-blastall bin $ ln -s /usr/local/wormbase/blast databases
The important thing to note is that the databases directory is a symbolic link to /usr/local/wormbase/blast. This is where the update_wormbase.pl script (described in the next section) dumps its BLAST databases.
Installing Analog and Report Magic (optional)
If you are running an offical mirror site or would like to analyze accesses to your server, you should also install Analog and ReportMagic. These software packages will be used to automatically analyze the access logs on a running basis.
Fetch analog:
% wget http://www.analog.cx/analog-6.0.tar.gz % tar xzf analog-6.0.tar.gz % cd analog-6.0 % make % cd ../
(Note: sometimes wget of analog-6.0.tar.gz will hang. In that case, just use your Web browser to get the package onto your desktop computer, then scp it to your WormBase mirror computer.)
Copy analog to the primary WormBase root:
% cp -r analog-6.0 /usr/local/wormbase/util/log_analysis/.
Install Report Magic
% wget http://www.reportmagic.org/rmagic-2.21.tar.gz % tar xzf rmagic-2.21.tar.gz
Edit Install.PL to place the report magic files in /usr/local/wormbase. Replace:
$DEST = '/usr/local/bin/rmagic-${VERSION}/'; with $DEST = '/usr/local/wormbase/util/log_analysis/rmagic/';
# And install... % sudo perl Install.PL
Configuring the WormBase installation
Although most files are delivered through the update mechanism, you will need to customize several files. Templates for each file are provided.
Apache configuration - ~/wormbase/conf/httpd.conf vs. ~/apache/conf/httpd.conf
There are two httpd.conf files to contend with: one in the main directory for the Apache server (/usr/local/apache) and one in the site software for WormBase (/usr/local/wormbase). Getting the Apache configuration right entails getting various directives in these two files to properly mesh. Generally speaking, you want to set things up so any request specific for the WormBase site goes to /usr/local/wormbase/conf/httpd.conf, but also that any HTTP request meant for general purposes can still be handled by the main software and configurations at /usr/local/apache/conf/httpd.conf.
In the prototype file /usr/local/wormbase/conf/httpd.conf.template, you will find an Apache configuration file containing WormBase-specific definitions. These definitions will include:
CustomLog /usr/local/wormbase/logs/access_log combined_format <Directory /usr/local/wormbase/html> ... </Directory> DocumentRoot /usr/local/wormbase/html ErrorLog /usr/local/wormbase/logs/error_log LogFormat [various...] ServerAdmin webmaster@wormbase.org # change to your preferred e-mail address
These and other directives in /usr/local/wormbase/conf/httpd.conf will do the following:
- Set /usr/local/wormbase/html to be the document root for static HTML files.
- Set /usr/local/wormbase/db to be a script directory under the control of mod_perl's Apache::Registry.
- Create transfer and error logs in /usr/local/wormbase/logs
- Create an ordinary cgi-bin directory in /usr/local/wormbase/cgi-bin
- Put all static .html files under the control of Apache::AddWormbaseBanner, a module that appends the standard WormBase header and footer on all HTML files.
The simplest approach would be to cut-and-paste this file into the main configuration file (/usr/local/apache/conf/httpd.conf), replacing the directives already there. The approach recommended here, though, is to set up a WormBase-specific httpd.conf file:
$ cp /usr/local/wormbase/conf/httpd.conf.template /usr/local/wormbase/conf/httpd.conf
Then use an Include directive in /usr/local/apache/conf/httpd.conf to import the WormBase-specific directives as needed. For instance, if WormBase is going to be the only website hosted by this server, then comment out all DocumentRoot and <Directory> sections, e.g.:
#DocumentRoot "/usr/local/apache/htdocs"
from the main configuration file /usr/local/apache/conf/httpd.conf. Also, check that the Port directive in /usr/local/apache/conf/httpd.conf is "Port 80" (it should already be). Then, insert the following at the bottom of /usr/local/apache/conf/httpd.conf:
Include /usr/local/wormbase/conf/httpd.conf
Conversely, if WormBase is going to be a virtual host (one of several web sites hosted by the server), then create an appropriate <VirtualHost> section in /usr/local/apache/conf/httpd.conf. Here is a template to follow:
<VirtualHost *:80> ServerName wormbase.hostname.org # e.g., caltech.wormbase.org UseCanonicalName on Include /usr/local/wormbase/conf/httpd.conf </VirtualHost>
<VirtualHost *:80> ServerName your-non-wormbase.hostname.org UseCanonicalName on Include /usr/local/apache/conf/local_httpd.conf # copy base configuration information to here </VirtualHost>
For more details see the Apache documentation on virtual hosts. The IP address in the <VirtualHost> tag must be replaced by the correct IP address for the server. Likewise, the ServerName must be replaced by a DNS name that will correctly resolve to this IP address. N.B.: do not use "www.wormbase.org"! This name is already taken.
You must also set up a file for perl definitions:
$ cp -p /usr/local/wormbase/conf/perl.startup.template /usr/local/wormbase/conf/perl.startup
However you end up applying it, /usr/local/wormbase/conf/httpd.conf needs a few small adjustments before use. First, change the filler name "your.machine.org" to the actual hostname of your server (or to an appropriate alias, such as "caltech.wormbase.org"); do this both for ServerName and at all other sites throughout the file. Likewise, change ServerAdmin to the e-mail address of whoever will actually be responsible for administering the mirror.
Also, update the location of the staging directory for dynamically-generated images to one suitable for your installation. This involves the following directive:
Alias /ace_images /var/tmp/ace_images
The ace_images directory will be created automatically the first time WormBase needs it, but the directory that it contains, in this case /var/tmp, must be writable by the Apache user (usually "nobody"). The images will eventually occupy approximately 10 megs. If /var/tmp is not appropriate for your system, change the second argument to some location that is more suitable.
WormBase configuration - wormbase/conf/elegans.pm and localdefs.pm
elegans.pm
WormBase uses two main configuratation files, elegans.pm and localdefs.pm, located at /usr/local/wormbase/conf.
The first, elegans.pm, contains a variety of Perl definitions that are used by the various WormBase mod_perl scripts. You will want to look through this file, but you probably will not need to make any changes. The sole item you might wish to change controls the location of temporary files:
@PICTURES
This is the location of a temporary staging directory for dynamically-generated images as indicated in conf/httpd.conf. Its value is a list in which the first item is where the images will appear on the Web server (in URL space) and the second item is where they will appear on the filesystem:
@PICTURES = ('/ace_images' => '/var/tmp/ace_images');
If you changed the location of the staging directory in httpd.conf, you must make the corresponding change here.
localsdef.pm
The second file, localdefs.pm, contains site-specific hostnames, ports, and passwords. You will find a template for this file at /usr/local/wormbase/conf/localdefs.pm.template. Copy this file to localdefs.pm and edit the following options as appropriate for your site.
- $HOST
This is the name of the host where the socket server runs. It is set to "localhost" by default.
- $PORT
This is the port on which the socket server runs, 2005 by default.
- $ACEPASS, $USERNAME, $PASSWORD
These three items define the acedb username and password.
- $MYSQL_HOST, $MYSQL_USER, $MYSQL_PASS
These three items define the mysql host, username, and password.
- $MASTER
This is used only for the WormBase master site. Should be set to 0.
- $MIRROR
Whether or not the site is a mirror. Should be set to the name of the mirror.
- $DEVELOPMENT
Whether or not the site is a development site. Internally, this controls the nature of caching on the site. Should be set to 0.
- $BLAST2WORMBASE, $WORMBASE2BLAST
These two options control where the blast script directs queries, and where those queries are returned. This is provided in the event that a second standalone blast server is provided. If not, these two options should point to:
$WORMBASE2BLAST=http://your.hostname.org/
Configuring Servers To Start Automatically
The final step is to arrange for Acedb to start automatically and for MySQL to restart if necessary.
Installing MySQL and BLAT monitoring scripts
Run:
$ cp -i /usr/local/wormbase/util/admin/blat_server.initd /etc/rc.d/init.d/blat_server
Then run:
$ crontab -u root -e
to add the following entries to root's crontab:
0 * * * * /usr/local/wormbase/util/admin/restart_mysqld.pl 0 * * * * /usr/local/wormbase/util/admin/restart_blat.pl
Acedb log rotation
Acedb generates massive log files. To keep these from growing too large, add the following entry to root's crontab (or that of another privileged user):
10 1 * * * /usr/local/wormbase/bin/rotatelogs.pl
Configuring ACeDB to start automatically under inetd
Some, but not all, UNIX and Unix-like operating systems use inetd to automatically start background processes; in such a system, inetd must be configured to launch the acedb server. (Other systems such as Fedora Linux will use xinetd.)
Where inetd is used, locate the file /etc/inetd.conf, and add the following line to the end:
2005 stream tcp wait acedb /usr/local/acedb/bin/sgifaceserver sock.acedb /usr/local/acedb/elegans 1200:1200:0
Note that this line may be wrapped into two or more lines when being viewed; but, in the real configuration file, this must be a single unbroken, unwrapped line. The first column indicates the port number to listen to. 2005 is the default used by the WormBase configuration files.
Tell inetd to reload its configuration file by sending it a HUP signal.
% ps -elf | grep inetd 140 S root 500 1 0 60 0 - 329 do_sel Jul17 ? inetd % killall -HUP 140
You should now be able to talk to the database using saceclient (as a anonymous user):
% ~acedb/bin/saceclient localhost -port 2005
Configuring Acedb to start automatically under xinetd
First, make sure that xinetd is actually installed (look for the presence of /usr/sbin/xinetd). If not, use the RPM manager (gnorpm or equivalent) to install the xinetd package.
Modern versions of xinetd (e.g., xinetd-2.3.13-6) distributed with Fedora Core 4 should work well. If for some reason you are using an old version (<2.3.7), though, you must upgrade to at least xinetd-2.3.7-4.7x.
Once xinetd is installed, you will now need to create an xinetd configuration file for Acedb. Create a new file named /etc/xinetd.d/acedb with the following contents:
# file: /etc/xinetd.d/acedb # default: on # description: wormbase acedb database service acedb { protocol = tcp socket_type = stream port = 2005 flags = REUSE wait = yes user = acedb group = acedb log_on_success += USERID DURATION log_on_failure += USERID HOST server = /usr/local/acedb/bin/sgifaceserver server_args = /usr/local/acedb/elegans 1200:1200:0 }
Edit /etc/services. Although xinetd is not supposed to use /etc/services, the following line must be added:
acedb 2005/tcp
Restart xinetd with the following command:
# /etc/rc.d/init.d/xinetd reload (or restart)
To kill xinetd, first find the process id and then:
# kill -SIGUSR2 process#
You should now be able to talk to the database using saceclient:
% ~acedb/bin/saceclient localhost -port 2005
Note: to know if the server is listening at port 2005, run the following command:
# netstat -ant | grep LISTEN or, for more readable output, # netstat -vatp | grep LISTEN
If an error occurs, check /var/log/messages, and the serverlog.worm and log.wrm files in the current database directory. Common errors include insufficient disk space and inapprorpriate permissions for the latter two log files. Remember, the acedb server must be able to write to these files.
Testing The Site
At this point, all components of a WormBase installation have been installed. You can test your installation by restarting the various server components of WormBase.
Restarting AceDB
# Via xinetd: $ /etc/rc.d/init.d/xinetd reload (or restart)
# Or to kill xinetd, first find the process id and then: $ kill -SIGUSR2 process#
# ...or using saceclient % saceclient localhost -port 2005 acedb> password: acedb> shutdown now
MySQL
# Via mysqladmin... % mysqladmin -uroot -pPASSWORD shutdown # or using init.d $ /etc/rc.d/init.d/mysql restart
Apache
When the configuration files have been checked and adjusted, restart Apache with the following command:
$ /usr/local/apache/bin/apachectl restart
Look in /usr/local/wormbase/logs/error_log (Wormbase-specific errors) and /usr/local/apache/logs/error_log (general errors) for any error messages. If there are none, try fetching the main page. You should see a WormBase banner and footer. The various database searches should also work.
BLAT
% /usr/local/blat/bin/gfServer start localhost 2003 \ /usr/local/wormbase/blat/*.nib & > /dev/null 2>&1
Blocking robots
It can be useful to block search engines (such as Google) from crawling over one's mirror. To do this, go to /usr/local/wormbase/html, and make a file called "robots.txt" with the following contents:
User-agent: * Disallow: /
Troubleshooting
There are a number of common problems to check:
Is the acedb socket server starting?
Run "ps" to determine whether the server is indeed starting. If not, go back to the acedb configuration section and confirm that everything is where it should be. Make sure that the /usr/local/acedb/elegans/database directory is writable by the acedb user.
The two acedb logs to check for error messages are both in /usr/local/acedb/elegans/database. Examine log.wrm and serverlog.wrm.
Is the acedb socket server crashing?
It is possible that the server is crashing soon after it starts. The symptom of this is that the system gets very busy for a while, and "top" or "ps" shows the server restarting repeatedly. Eventually inetd (or xinetd) will disable the server and issue a syslog message to the effect that it is disabling a "looping" service.
Again, check that acedb is installed properly and that the database directory is writable. Check log.wrm and serverlog.wrm.
"Internal Server Error"
This is typically a symptom that mod_perl isn't installed correctly, a required Perl library is missing, or something is wrong with the configuration. Check the two error_log files (in /usr/local/apache/log and /usr/local/wormbase/log) for clues.
The banner displays but the decorative worm images are broken
On some versions of Linux running the libc 2.2 library there is a bug in readdir(), which is the function called to read the contents of a directory. You can check what version of glibc you have by looking at the contents of /lib:
% ls -l /libc-* -rwxr-xr-x 1 root root 4101324 Feb 29 2000 /lib/libc-2.1.3.so*
Versions that are at risk will show libc-2.2.so installed. The solution is to upgrade to a more recent version of libc. libc 2.2.3 is known to work correctly.
If you are stuck, send copies of the error logs and anything else you think might be useful to lstein@cshl.org and I'll try to help.
Installing scripts to verify that the servers are running
Two scripts in the WormBase directory can be used to ensure that the mysql and blat servers are running. To install, them:
% sudo cp /usr/localwormbase/util/admin/blat_server.initd \ /etc/rc.d/init.d/blat_server
Place the restart scripts under cron control of a privileged user. These commands will check every hour to see that the servers are running.
% sudo crontab -u root -e
0 * * * * /usr/local/wormbase/util/admin/restart_mysqld.pl 0 * * * * /usr/local/wormbase/util/admin/restart_blat.pl
At the same time, you might also wish to automate the rotatation of logs to prevent them from growing to an unwieldy size. You'll find an appropriate log rotation configuration stanza in util/rotate_wormbase_logs and a log rotate script in /usr/local/wormbase/bin/rotatelogs.pl. You will need both.
# Rotate httpd logs 10 1 * * * /usr/local/wormbase/bin/rotatelogs.pl # Rotate acedb logs 10 1 * * * logrotate /usr/local/wormbase/util/rotate_wormbase_logs
This stanza will check that the acedb server logs do not grow larger than 100 MB.
INSTALL libgd and GD.pm (if installation of GD.pm failed)
libgd
Try first to install it with the default package management system of yout distro/UNIX. If that fails you might want to resort to manual installation from source:
Fetch and install libgd:
# curl -O http://www.boutell.com/gd/http/gd-2.0.33.tar.gz # tar xzf gd-2.0.33.tar.gz # cd gd-2.0.33 # ./configure # make # sudo make install
GD.pm
try the usual cpan way, or:
# curl -O http://stein.cshl.org/WWW/software/GD/GD.pm.tar.gz # tar xzf GD.pm.tar.gz # perl Makefile.PL -L/usr/local // or export LD_LIBRARY_PATH=/usr/local # make # sudo make install
If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf'
DO I NEED TO REMOVE OLD VERSIONS OF GD FIRST?
Finally reverted to 1.19! Yikes! cpan> install LDS/GD-1.19.tar.gz
Install XML libraries and modules
The XML parsing libraries faciliate XML dumps from WormBase. They are not strictly required for a Wormbase installation.
expat
As with libgd, try to use your package manager, or:
% curl -O http://umn.dl.sourceforge.net/sourceforge/expat/expat-1.95.6.tar.gz % gnutar -zxf expat-1.95.6.tar.gz % pushd expat-1.95.6/ % ./configure % make % sudo make install % popd
AUTHOR
Todd Harris (toddwharris@gmail.com)