Yes, I had to write a shell script to make the config file-generation faster and less troublesome, but after I got that part done, I really started to see a great system.  Nagios sends emails to me when it has an issue, like being unable to access a given server for a test or if the web server is down.  All of this went up in a relatively simple way.  Not as easy as Pandora FMS but still pretty simple, if you consider command-line configuration files simple to edit.

A little while ago, I got back from a weekend, during which Nagios had not sent any alerts or notices, and discovered two web-servers in my test network were locked up.  They both were running a particular application that filled their hard drives with 4GB files.  Nagios should have been able to sort this out.

What Happened?!?

What I discovered is that Nagios though t they both had 15GB free and were neither in alert status. It appeared that the service-checker I had set to check the drives was checking only the Nagios server’s drive. It was about 15GB free, thanks. I dug into the details of the issue and discovered that the service-checker I had chosen was never intended to read a remote drive. I got a slight clue, when one of my colleagues asked if I was launching the checker with Samba (Windows sharing protocol) or with SSH (Secure Shell, the workhorse network communications protocol of the UNIX world and by extension – the internet.

My Solution

I had been resistant to having to load anything on the remote servers related to Nagios, as I had the fo0nd illusion that Nagios was a clientless network-management application. I knew this wasn’t entirely true. There had to be a username and password supplied for reading the health of the Postgresql service. In this case, there needed to be a small shell-script on the client that Nagios’s plugin could access.
The plugin was called check_diskfree
check_diskfree needed to have another service plug-in, check_by_ssh, to work.

Configuration Steps

Open the file /usr/local/nagios/etc/objects/commands.cfg and add the following block of code:

define command{
command_name check_by_ssh
command_line $USER1$/check_by_ssh -H $HOSTADDRESS$ -p $ARG1$ -C "$ARG2$ $ARG3$ $ARG4$ $ARG5$ $ARG6$"
}
# The example at Nagios extensions showed it as $HOSTNAME$ but that looked for the machine name in my network. Apparently it is designed to work with Fully-Qualifies-Domain-Names (FQDN). On my network, it just showed the error"Invalid HOSTNAME/IP ADDRESS." "HOSTADDRESS will work in any network.
# Below is the command definition that read only the local Nagios-Server disk.
define command{
command_name check_disk
command_line $USER1$/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
}


Service Definition Madness

I have a script, as I mentioned that makes putting together a server-monitoring config much easier. It makes a separate file for each server with the servers HOSTNAME (machine name) and the extension .cfg. I found this far simpler than running through a 4000-line config file, which was what it looked like before I wrote the script. I am going to presume for now that you have some way of associating services with machines. If anybody asks, I might show that script to you, someday.
Thus I open a 80-line HOSTNAME.cfg file and under the services header add the following service definition.


define service{
use local-service
host_name HOSTNAME
service_description Remote Root Partition
check_command check_by_ssh!22!/nagios/check_diskfree.sh!sda2!75!90
notifications_enabled 1
max_check_attempts 3
check_interval 5
retry_interval 3
check_period 24x7
notification_interval 15
notification_period 24x7
notification_options w,c,r
contact_groups admins
register 1
}

# The following is the service-definition that was not working

define service{
use local-service
host_name HOSTNAME
service_description Root Partition
check_command check_disk!20%!5%!/
notifications_enabled 1
max_check_attempts 3
check_interval 5
retry_interval 3
check_period 24x7
notification_interval 15
notification_period 24x7
notification_options w,c,r
contact_groups admins
register 0
}

Sanity-Checking your Configuration

To check your configurations without starting up the nagios service, you want to run the following helpful command.

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

This will check all of your config files and even tell you what line is bad in which file is wrong. This is far quicker than restarting, or attempting to restart, the nagios service

# /etc/init.d/nagios restart

Failures are extremely terse, and unhelpfull, while the sanity-checking command is extremely helpful.

Setting up Communications with the Remote server

You will need to get the public key from your Nagios server’s nagios user and put it in the file of authorized ssh keys on the remote machine somehow. There are a couple of ways but this is how I usually do this thing, because I usually have one or two terminal windows open on my desktop. That lets me use the copy buffer to do this configuration. I also use Debian servers, so the commands might not work exactly like this on your flavour of Linux.
In the terminal (or one of the many) shell into the remote server as its root user.

ssh root@192.168.0.230

Add a user called ‘nagios.’ This is the user name that nagios will attempt to contact the remote server under, so rather than pushing the river, you just have to have that user to receive the request.

adduser nagios

Add a directory called /nagios

mkdir /nagios

Switch users to that nagios user and make another directory – this directory will be in your nagios user’s home folder.

su - nagios
mkdir .ssh

shell back into your Nagios server’s nagios user’s home folder

ssh nagios@NAGIOSSERVER # Change NAGIOSSERVER TO it's actual IP address or domain name

Make a public key (if you don’t already have one created). Leave the pass-phrases blank.

ssh-keygen

Copy your Nagios server’s nagios user’s public key

less .ssh/id_rsa.pub

Here I just highlight and copy the entire block from “ssh-rsa” to the end. (it may have the user name at the end, and you can include that too, i.e., nagios@nagiosserver
Click “q” to quit the less application and type “exit” to close the secure shell session
now your prompt will show you to be “nagios@remoteserver:~$” so you need to paste the key in.

vi .ssh/authorized_keys

Type “i” for “insert” and either with the mouse or keyboard shortcuts paste the key into the file. Make sure there is a blank line at the end of the file. Because you just made this user, this file did not exist before you invoked it with vi.
Save the file and quit vi

:wq

Now type “exit” until you are again looking at a prompt showing you to be nagios@nagiosserver:~$
To check the set-up, shell back into the remote server. You should not need to have a password this time.
now to finish the set-up on the remote server, you need to copy the check_diskfree.sh file into the nagios directory you just created at root level.

scp /usr/local/nagios/libexec/check_diskfree.sh 192.168.0.230:/nagios/

This drops the file where nagios will be looking for it.

Looking at the Nagios Front-End

go to your web browser and look at the services page. Your remote server should have a new service called “Remote Root Partition”
If there is an error or no useful info, click on that service name and then the link to reschedule the next check of that service. When you go back to the services page you should see something like this

--------------------------------------------------------------------------------------------------------
| Remote Root Partition | OK | 03-19-2012 17:52:18 | 0d 1h 26m 33s | 1/3 | OK. | Free Space: 24GB, 95% |
--------------------------------------------------------------------------------------------------------


Created by Lyrasis, a 501c(3) library association based in Atlanta GA, this site was created specifically for libraries but it is useful for other organizations when trying to understand whether opensource software will work for them. http://foss4lib.org.

Since the acquisition of certain data is many times critical, the grep utility is a valuable tool for the Linux user. It allows you to search through one or more files to see whether any contain a specified string of characters. This utility does not change the file it searches but simply displays each line that contains the string.

Originally, the name grep was a play on an ed— an original UNIX editor, available on Fedora/RHEL— command: g/re/p. In this command g stands for global, re is a regular expression delimited by slashes, and p means print.

The following is an example of the proper syntax.

grep ‘string you want to search for’ file (name of file you want to search)

So, let’s say you were looking for the name of a person in a memo so you could replace that name with another without retyping the entire memo or document, a simple example could be:

grep ‘Halton’ thankyou.txt

This would return the specified name which could then be changed to the next name on the list of professors you wanted to thank for their contribution and influence on your education.

Options available for this command are extensive here are a few:

-H print the filename for each match

-I Ignore case

-l print only names of FILEs containing matches

-n print line number with output lines

-o only matching; show only the part of the line matching PATTERN

-w match only whole words

-x force PATTERN to match only whole lines

To see a complete listing of the options and a more complete detailed explanation of this utility it can be obtained by typing the following in the command prompt in Linux terminal.

$ man grep

(Mike Brooks)

Peter Dietz.

The goal of this guide is to provide a simple path that will get a user up-and-running as quickly as possible. Peter Dietz did a great job with this, however there are issues about setting up DSpace on an Ubuntu 10.04LTS server that I didn’t think were covered well. This is not entirely surprising because there have been two Ubuntu releases since April of 2010, and it is at least because my company doesn’t set up servers on the bleeding edge of Ubuntu development. There may be a switch to Debian at some point. Debian Stable is even more stable than Ubuntu LTS, I must admit, but we are more comfortable with Ubuntu.

Installing DSpace is almost as simple as changing between DSpace versions (eg between 1.6 and 1.7). It can be done in only a few minutes. The installation and configuration of the prerequisites is the step that takes all the time. Within the world of the Ubuntu server, this is standard stuff. Ubuntu has an application to help with setting up the web application stack. The following is steps that are performed from Terminal, the command line interface in Ubuntu. These steps can also be done through a ssh secure shell from any machine with a ssh client, or from runlevel 3 command-line with networking.

This how-to was originally written for Ubuntu 10.10 (Maverick Meerkat) and has been tested with Ubuntu 11.04 (Natty Narwhal). The current write-up is developed for Ubuntu Lucid Lynx 10.04LTS for use at Lyrasis, where I work as a Linux Systems Administrator. We have a policy of using LTS versions of the OS in my department, so we will not be updating our servers until the next Long-Term-Support version appears, next year. Here is the original wiki link, so you can see what I added. https://wiki.duraspace.org/display/DSPACE/Installing+DSpace+1.7+on+Ubuntu ..modified by Wolf Halton 8/18/2011

Acting as Root where You will be Doing Dozens of Commands as Root

Rather than repeat “sudo” over and over, one can use sudo -i to act as if one had logged in to a root session. The root session is a larger security risk than typing sudo over and over, however if you are planning to leave your computer you can easily type “exit” to leave the root session or lock your screen if you must leave the machine.

Install Prerequisites

Install the server stack of Tomcat (web server) and PostgreSQL (database)

• Select the following packages

Install the Compile / Build tools

Configure the Prerequisite Software

Create the database user (dspace)

Allow the database user (dspace) to connect to the database

Set the PostgreSQL Listening Port Wide

Create the dspace database

As the postgres user

Configure Tomcat to know about the DSpace webapps.

As root user

Download and Install DSpace

Create the [dspace] directory.

The [dspace] directory is where the running dspace code will reside. As the root user:

Download the Source Release

The source release allows you to customize every aspect of DSpace. This step downloads the compressed archive from SourceForge, and unpacks it in your current directory. The dspace-1.x.x-src-release directory is typically referred to

as [dspace-src].

You may have noticed there is not a unix system user called “dspace.” At this point you might want to “su: to your standard user – in my case that user would be “wolf” so I would type:

Compile and Build DSpace

The source release that has been obtained is human readable source code, and must be compiled to machine code for the server to run it. “mvn package” compiles the source code, and “ant” will do all the work necessary to initialize the database with the DSpace schema, and copy all of the compiled machine code to a location where the web server can serve it.

As the root user perform the following steps”

Fix Tomcat permissions, and restart the Tomcat server

This guide follows the convention where the tomcat user will own all of the files in [dspace], so we have to change the owner of the files to tomcat6. Restarting tomcat will deploy the dspace webapps that are now ready to be viewed.

XMLUI Display Issues

When any change is done to anything that changes the content of the static xmlui pages, one good solution which comes from http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg14441.html is that the cocoon cache has to be emptied. I have spent 2 days searching for a way to update a change in web-admin email address that appears on the contacts page. In our setup, the file we need to get rid of is /var/cache/tomcat6/Catalina/localhost/xmlui/cache-dir/cocoon-ehcache.data

To be on the safe side I just moved the file to cocoon-ehcache.data.old, restarted tomcat6, and “Bang!” the contacts page displays properly.

Test it out in your browser

That is all that is required to install DSpace on Ubuntu. There are two main webapps that provide a similar turn-key repository interface

http://localhost:8080/xmlui

http://localhost:8080/jspui

Setting an Admin Account

To add an admin account for administering Dspace, go to [dspace]/bin/ and run the command

./dspace create-administrator

The following lines are an

(almost) exact display of how that application works.

root@DSPACE-TEST-01:/dspace/bin#

./dspace create-administrator
Creating an initial administrator account

E-mail address:

wolf.halton@lyrasis.org

First name: Wolf

Last name: Halton

WARNING: Password will appear on-screen.

Password: your-admin’s-secret-password

Again to confirm: your-admin’s-secret-password

Is the above data correct?

(y or n):y

Administrator account created

root@DSPACE-TEST-01:/dspace/bin#

Check for proper connections in dspace.cfg

vi /dspace/config/dspace.cfg

You can

also keep your changes in dspace.cfg in [dspace-source]/dspace/config/. Whenever you edit dspace.cfg in [dspace-source]/dspace/config/, you should then run 'ant init_configs' in the directory [dspace-source]/dspace/target/dspace-1.5.2-build.dir so that any

changes you may have made are reflected in the configuration files of other applications, for example Apache. You may then need to restart those applications, depending on what you changed.

In 1.5.2 the default behavior of the "update" will check the checksums/file sizes of the installation configuration files in

“[dspace]/config” and will put a new configuration file example in “<filename>.new” if there is any difference. The end of the update process will list all the configuration files for which this happened, you should review those configuration files and merge each of them by hand to make sure you do not miss any new configuration requirements. Its recommended that you take the new file, place any changes you had made in the old file into it, delete the old and rename the new.

== ^^^^ The suggestions above [didn't solve my issues] ^^^^ ==

== And further, the changes made to the structure of the site directories ==

== was not entirely as advertised in the documentation ==

Editing Site Details

This is not a complete dspace.cfg manual, but just a set of comments for the directives I changed.

1. edit /dspace/config/dspace.cfg

# Basic Information – Site globals

# These directives give the site details so the web apps can find their own installation.

dspace.dir = /dspace

# or whatever directory path your dspace install is in.

# never put comments like this on command lines like the “dspace.dir =” line above it will cause lots of problems, even though it is a comment and the system should not be able to read anything after a ‘#.’

dspace.hostname = example.com

# dspace is looking for your public IP address (which works) or a fully qualified domain name (FQDN)

dspace.baseUrl =

http://example.com:8080

# include the http:// and the port number “:8080.” It makes the next few parts make more sense.

dspace.url =

${dspace.baseUrl}/xmlui

# The ${whatever} structure is how this script uses the variable whose value you set in the previous command and adds the front-end app of your choice

dspace.oai.url =

${dspace.baseUrl}/oai

# This is for using the Open Archives Interface, the set-up of which is described here:

https://wiki.duraspace.org/display/DSPACE/Use+the+OAI-PMH+interface.

Currently not in use on the Lyrasis DSspace Demo

dspace.name = “DSpace Demo at Lyrasis”

# Any string of characters can be used here. This should be a human-readable string.

# Database settings

db.name = postgres

# The other choice here is “oracle.”

db.url =

jdbc:postgresql://192.168.10.22:5432/dspace

• Special Cygwin instructions may allow you to run versions of Windows older than Windows 20001.
• On Linux, such as Ubuntu, there are some minimum software version numbers and minimum hard drive sizes
• The minimum required version is Python 2.2. This came out in December 21, 20012
• You will need about 100 MB for the source tree during compilation and about 20 MB for the installation directory. An empty database cluster takes about 35 MB; databases take about five times the amount of space that a flat text file with the same data would take. If you are going to run the regression tests you will temporarily need up to an extra 150 MB.3

Pgtune will help you set up PostgreSQL 9.0 to work well with your current hardware.

Install PGTune

# aptitude install pgtune

Run PGTune

# pgtune -i /etc/postgresql/9.0/main/postgresql.conf -o psql.conf
This puts the file, psql.conf, with the tuning suggestions in root’s home folder

I like using the screen command to move from one command-line page to new command-line page
# aptitude install screen

Using the Screen Command

Since we are doing a lot as root, I am using the “#” sign rather than saying “sudo” over and over. If you want to stay root for a while, you can enter:
$ sudo -i
You will be permanently root until you type “exit”
# screen

Very Basic Screen Commands

Note “^” is shorthand for the Control key, and “#” either means you are acting as the root user or it shows a comment. Let me know where this is confusing in the following How-to, and I will expand the how-to.
^A # <Ctrl>A tells screen that you want to send it a command (“^A” alone does nothing)
^A c #tells screen to make a new screen
^A n # go to next screen
^A 3 # go to screen number 3
– all numbers to be the equivalent of the screens you have running. I put one root session for restarting postgresql on one screen, and another root session for editing postgresql.conf on a second screen within screen.

,
1. since screen is open
   ^A c
   If you ^A n first, screen will tell you there are no other screens.
2. Using the VI editor, open the pgtune file you just made.
   # vi /root/psql.conf
   1. <shift>G to go to bottom of the file
   2. position your cursor at the top of the block marked
      “CUSTOMIZED OPTIONS”
      
   3. type “v” for “visual.”
   4. use your down-cursor arrow and the right-cursor  to highlight all of the customizations.
   5. Hit “y” to copy the text to a buffer. The highlighting will vanish.
      
3. ^A n takes you to your other screen.
4. Make a backup of your config file
   # cp /etc/postgresql/9.0/main/postgresql.conf /etc/postgresql/9.0/main/postgresql.conf.bak
   You will thank yourself for taking this step
5. In a second ‘screen’ open your active Postgresql configuration file for editing
   # vi /etc/postgresql/9.0/main/postgresql.conf
   opens the file for editing.
   <Shift>G takes you to the bottom of the file
6. I like to organize the end of the file a little.
   1. Hit the “I” key for “Insert Mode”
   2. Move the cursor to the end of the last visible line with the <End> key (above the cursor arrows block, usually) or just use the right cursor key to get there
   3. Hit enter to add a blank line at the bottom of the page
   4. Mash <Esc> to go to “command mode”
   5. <Shift>P inserts the lines you saved from the other file.
   6. Mash <I> and put a pound sign and a space,“# “, in front of each of the lines you copied over. This keeps them inert until you are ready to use them. It also means that you do not have to delete the block when you are done, if you don’t choose to do so.
      
7. To put the line items in the same places as the defaults, you need to visually highlight and then yank one line (or part of one line) at a time (just like you did to get the lines here).
8. While staying in command mode, type a forward slash and the first couple of words of the line you are searching for
   /max_connections
   vi will move you to the top of the file and search for the string you entered.
9. Position your cursor on the line underneath the existing line and
   <Shift>P to “put” the line in right there.
10. If the line you are replacing has a pound sign “#” at the beginning, it means that it was not a live directive. If it doesn’t have a “#” sign at the front,
    1. Mash <i> to go into insert mode
    2. Position the cursor at the left end of the line and put in the “#” sign
       
11. <Esc> to go back to command mode, and
12. <Shift>G to get back to the bottom of the document
13. Mash “:w” to save the change. “:wq” dumps you out of vi, and that can be confusing.
14. ^A to go back to the first screen
15. If, when you get back to the first screen, vi is still open and showing you the pgtune file, Hit :wq to exit the file.
    
16. # /etc/init.d/postgresql restart
    If there is an error, it will probably be about shmmax. In that case, jump to the section about setting the kernel.shmmax to a larger size
17. If there is no problem starting PostgreSQL, Go back to Direction 3 above and repeat until done.
18. If there is an error, it will probably be about shmmax. In that case, jump to the section about setting the kernel.shmmax to a larger size.

Shmmax!

To adjust the shmmax – to at least what the system says you need after tuning the database.

# sysctl -w kernel.shmmax=<something bigger than the number the postgresql.conf error shows>
For instance
# sysctl -w kernel.shmmax=1102069760

If the error shows up again, look at the number it is looking for and reset kernel.shmmax to that number.
# sysctl -w kernel.shmmax=1110401024 (happened when increasing wal_buffers)

Close out screen

1. The screen you were on, at the end is the one where you were restarting the PostgreSQL server. If you are still on your open vi session, mash “:wq!” to force a save and a quit to get you out of vi.
2. Type exit on the command line. The screen you are on will close.
3. Type exit again. Screen will tell you it is terminating
4. Type exit again, to end the root session
5. Type exit again, and (probably)
   1. the ssh session will end, if you are shelled into the server from a remote host.
   2. the system will log you out, if you are logged into the command line locally (runlevel 3)
   3. or the terminal window will close, if you are using the terminal application on the server’s graphic user interface

One interesting note about screen: If you are used to being able to use your up-cursor to scroll back through your commands, you will discover that what you do in screen remains in screen. That history will be unavailable once you end your screen session.

Wolf Halton 8/17/2011

This is something I was working on, on our Ubuntu 10.4LTS servers.  Since I had several to do, I thought it would be fun to add it to the Evergreen-ILS wiki and also to put it here with a little more detail.  The project wikis are likely to be places where the readers are more used to working with the project.  This is less a place for the experienced and more for those who are thinking about doing something with Evergreen-ILS.  Since there is a lot from the wiki page, from before I started updating it, I am including that page link here.

http://evergreen-ils.org/dokuwiki/doku.php?id=upgrading_postgresql_8-4_to_postgresql_9.0_on_ubuntu_10.04

This is not a thing that you will have to do forever, but when you update your PostgreSQL 8.4 databases to PostgreSQL 9.0 You can’t just
sudo aptitude install postgresql-9.0
as your database will be hosed during the process of upgrading to a major revision like this. You will probably not have to go through all this drama when moving from 8.3 to 8.4, or from 9.0 to 9.6 (when there is a Postgresql-9.6) but it probably comes down to how lucky you feel. I find backing up databases always is worth the effort.

Systems Administration

1. Generally when I am going to be bouncing in and out of a lot of system-user accounts, I start by becoming root:sudo -i # This command makes you the root user (because no user is specified in the command) and logs you in as if you were that user logging into a runlevel 3 session.  This is roughly equivalent tosudo su - # which switches the user to root and adds root’s environmental $PATH.  What’s good about it is that since root’s path includes directories that are not in an average user’s path, it is easier to use some tools and commands.  In some cases, missing the environment variable means 3rd-party scripts just won’t work.  I use sudo -i because the "-" in "sudo su -” is easy to forget.When the instructions say to act as user postgres, since you are already root (who can become any user without knowing their password) you just typesu - postgresWhen you are done “being” that user, just type

   exit

   and you will be root again.

2. Stop Evergreen and disconnect clients from database. When you stop Evergreen, the clients will be disconnected automatically, in an abrupt way. It might be better to disconnect the clients first, and then after the users are properly cleared off and their changes saved, stop Evergreen.As postgres user:postgres=# SELECT procpid, (SELECT pg_terminate_backend(procpid)) as killed from pg_stat_activity

3. Add python-software-propertiessudo apt-get install python-software-properties
4. Add the backport repository to your repository sources list:

   sudo add-apt-repository ppa:pitti/postgresql

5. Update the sources list on your server.

    
   apt-get update

6. Check that you are getting all your databases
   psqlpostgres # \l+#that is a lower-case L, and the plus sign gives you extended information about the databases you are running.
7. As the postgres user, backup your PostgreSQL databases.

    
   pg_dumpall > data.sql # This is the simplest way to get everything # or individually.. pg_dump -U username -W database_name > db.sql # for instance.. pg_dump -U evergreen -W evergreen > evergreen.sql pg_dump -U rsyslog -W Syslog > Syslog.sql #and so on

8. As root, remove PostgreSQL 8.4 and install 9.0.

    
   aptitude purge postgresql-8.4
   aptitude install postgresql-9.0 postgresql-client-9.0 postgresql-contrib-9.0 postgresql-plperl-9.0

9. as the postgres user, recreate empty evergreen databases with required language supports.If you do not have Evergreen-ils on the system yet, you can skip this step and go on to step 9.

   dropdb evergreen
   createdb -T template0 --lc-ctype=C --lc-collate=C -E UNICODE evergreen
   createlang plperl evergreen
   createlang plperlu evergreen
   createlang plpgsql evergreen
   psql -f /usr/share/postgresql/9.0/contrib/tablefunc.sql evergreen
   psql -f /usr/share/postgresql/9.0/contrib/tsearch2.sql evergreen
   psql -f /usr/share/postgresql/9.0/contrib/pgxml.sql evergreen

10. Update the 8.4 cluster (with evergreen database) to 9.0. For this to work properly, and not get the error “Target already exists 9.0 main,” you will need to move(rename) or delete the following directory:

    /var/lib/postgresql/9.0/main

    and

    /etc/postgresql/9.0/main

    The rationale for moving(renaming) rather than straight-out delete is you may well discover that your pg_hba.conf file is empty of all your changes when you complete the pg_updatecluster.

    As the root user:

    sudo mv /var/lib/postgresql/9.0/main /var/lib/postgresql/9.0/oldmain

    sudo mv /etc/postgresql/9.0/main /etc/postgresql/oldmain

    You may need to do the following command as root, as it is required to write into /etc/postgresql which is owned by root

     
    pg_upgradecluster 8.4 main

11. as the postgres user, load data from backup into PostgreSQL 9.0.

     
    psql < data.sql # If you are updating specific databases... psql -U username -W database < db.sql 

12. Restart Evergreen and Apache.
13. Test by logging into psql, checking the postgreSQL version and running a simple SELECT query.

     
    psql -U evergreen 
    evergreen=# select version();
    evergreen=# select count(*) from biblio.record_entry;

14. Check pg_hba.conf and to make sure your configurations are right and the database is allowing connections from the machines, IP addresses or IP ranges you expect, and If everything is working properly, and postgresql.conf to make sure your postgresql server is listening on the right ports. If everything is communicating properly, delete
/var/lib/postgresql/8.4/main, /etc/postgresql/8.4/main
and
/var/lib/postgresql/9.0/oldmain, and /etc/postgresql/9.0/oldmain


Thanks again to the great people at the Evergreen-ILS project

The Evergreen Project develops an open source ILS (integrated library system) used by approximately 800 libraries.  The software, also called Evergreen, is used by libraries to provide their public catalog interface as well as to manage back-of-house operations such as circulation (checkouts and checkins), acquisition of library materials, and (particularly in the case of Evergreen) sharing resources among groups of libraries.

The Evergreen Project was initiated by the Georgia Public Library System in 2006 to serve their need for a scalable catalog shared by (as of now) approximately 250 public libraries in the state of Georgia.  After Evergreen was released, it has since been adopted by a number of library consortia in the US and Canada as well as various individual libraries, and has started being adopted by libraries outside of North America.

This is a work in progress, but here is the saga so far:

Notes: Where I am using passwords, I will instead use the convention of <secret>, so instead of saying “My password is T^T87uugf7h,” I will say “My password is <secret>.”  Things behind a “#” sign are comments – either comments in the files themselves or notes to my readers

#########
# openSRF
#########
Evergreen install
As the root user, add the opensrf user. We set the default shell for the new user to /bin/bash to inherit a reasonable environment:
useradd -m -s /bin/bash opensrf       #

passwd opensrf
<secret>
As the opensrf user, download and extract the source files for OpenSRF 2.0.0:
wget http://evergreen-ils.org/downloads/opensrf-2.0.0.tar.gz
tar xzf opensrf-2.0.0.tar.gz
A new directory opensrf-2.0.0 is created.
As the root user, install the software prerequisites using the automatic prerequisite installer. Replace <distribution> below with the following value for your distribution:
debian-lenny for Debian Lenny (5.0)
debian-squeeze for Debian Squeeze (6.0)
fedora13 for Fedora 13
ubuntu-hardy for Ubuntu Hardy Heron (8.04)
ubuntu-lucid for Ubuntu Lucid Lynx (10.04)
centos for CentOS 5
rhel for Red Hat Enterprise Linux 5
aptitude install make
cd /path/to/OpenSRF
make -f src/extras/Makefile.install <distribution>

# This didn’t work for me, so I went on without it.  “They probably don’t have a config for Natty,” I thought.
check dependencies by going to openSRF directory, and:
$ ./configure
it said I was missing APXS and this was availiable in apache-prefork or apache-threaded
I chose threaded
# missing XMLADDID
can’t find with a search of packages
to add python support, which seemed useful
$ ./configure –prefix=/openils –sysconfdir=/openils/conf
#still missing xmlAddId
sudo aptitude install xml2
after some hunting around…
wolf@tangle-rock:~/opensrf-2.0.0$ sudo aptitude install libxml2-dev
This got me to the next deficiency..
libmemcached>= 0.8.0
which is not in the repos under that name

wolf@tangle-rock:~/opensrf-2.0.0$ sudo aptitude install memcached
not enough.. found a version at https://launchpad.net/libmemcached/+download
cd to libmemchached directory
./configure
Configuration summary for libmemcached version 0.50

* Installation prefix:       /usr/local
* System type:               pc-linux-gnu
* Host CPU:                  i686
* C Compiler:                gcc (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2
* Assertions enabled:        yes
* Debug enabled:             no
* Warnings as failure:       no

—
success!!
now to make and make install
Well, there were no apparent errors.. so we move on back to openSVF and try the configure step again.

By the way,
cd  -
takes you back to the last directory you were in

# oops, I have to config as opensrf user…
# and opensrf has no rights in my home directory

wolf@tangle-rock:~/opensrf-2.0.0$ sudo chown -Rv opensrf *.*
now when I run the configure comand it should work…

./configure –prefix=/openils –sysconfdir=/openils/conf –enable-python

# ok – this failed, so I copied the content of the opensrf install folder to opensrf’s home, and changed the ownership of all to opensrf.

####
opensrf@tangle-rock:/home/wolf/opensrf-2.0.0$ exit
exit
root@tangle-rock:~/opensrf-2.0.0# cd ..
root@tangle-rock:~# cp -R opensrf-2.0.0/ /home/opensrf/

root@tangle-rock:~# su – opensrf
opensrf@tangle-rock:~$ ls
examples.desktop  opensrf-2.0.0

opensrf@tangle-rock:~$ exit
logout

root@tangle-rock:~# cd /home/opensrf/
root@tangle-rock:/home/opensrf# chown -R opensrf:opensrf opensrf-2.0.0/
root@tangle-rock:/home/opensrf# ls -lR opensrf-2.0.0/  # (shows everything is changed)

# I am using
sudo bash -i
# because then I don’t have to hunt all the users’ passwords to suwitch to that user.

root@tangle-rock:/home/opensrf# su – opensrf
opensrf@tangle-rock:~$ cd opensrf-2.0.0/
opensrf@tangle-rock:~/opensrf-2.0.0$ ./configure –prefix=/openils –sysconfdir=/openils/conf –enable-python

# it failed to find python setuptoold module

opensrf@tangle-rock:~/opensrf-2.0.0$ exit
logout
root@tangle-rock:/home/opensrf# aptitude install python-setuptools
The following NEW packages will be installed:
python-setuptools # and so on…

root@tangle-rock:/home/opensrf# su – opensrf
opensrf@tangle-rock:~$ cd opensrf-2.0.0/
opensrf@tangle-rock:~/opensrf-2.0.0$ ./configure –prefix=/openils –sysconfdir=/openils/conf –enable-python

——————— Configuration options:  ———————–
OSRF install Java support?       no
OSRF install Python support?     yes
OSRF install chopchop?           no
Installation directory prefix:   /openils
Temporary directory:             /tmp
APXS2 location:                  /usr/bin/apxs2
Apache headers location:         /usr/include/apache2
APR headers location:            /usr/include/apr-1.0
libxml2 headers location:        /usr/include/libxml2/
———————————————————————-

opensrf@tangle-rock:~/opensrf-2.0.0$ make
# Seems to have succeeded.  At least no errors noted at the end

root@tangle-rock:/home/opensrf# cd opensrf-2.0.0/
root@tangle-rock:/home/opensrf/opensrf-2.0.0# make install
# Cross your fingers.  We are almost halfway home.

ext/xmlextra.c:1:20: fatal error: Python.h: No such file or directory
compilation terminated.
# oops/  What now!
# where is Python.h??

# http://phpnub.blogspot.com/2011/04/resolving-python-error-pythonh-no-such.html
# suggests the error can be cleared by installing python2.x-dev – so in my case it would be
root@tangle-rock:/home/opensrf/opensrf-2.0.0# aptitude install python2.7-dev

# from the wiki..
# As the root user, add /openils/lib to the system dynamic library path and make your system recognize the newly installed libraries. For example, on Ubuntu or Debian you would perform the following steps:
Create a file named /etc/ld.so.conf.d/osrf.conf containing the following line:
/openils/lib
/usr/local/lib

root@tangle-rock:/home/opensrf/opensrf-2.0.0# vi /etc/ld.so.conf.d/osrf.conf

# I just copied the internal lines into the file [esc] :wq

root@tangle-rock:/home/opensrf/opensrf-2.0.0# ldconfig

# ldconfig(8)                                                        ldconfig(8)
#
# NAME
#        ldconfig – configure dynamic linker run-time bindings
#
# SYNOPSIS
#        ldconfig [OPTION...]
#
# DESCRIPTION
#        ldconfig  creates,  updates,  and removes the necessary links and cache (for use by the run-time linker,  ld.so)  to  the  most  recent  shared libraries  found  in  the directories specified on the command line, in the file /etc/ld.so.conf, and in the trusted directories (/usr/lib  and /lib).   ldconfig  checks the header and file names of the libraries it encounters when determining which  versions  should  have  their  links updated.  ldconfig ignores symbolic links when scanning for libraries.

#==============================
# Define your public and private OpenSRF domains. For security purposes, OpenSRF uses Jabber domains to separate services into public and private realms.

# Gee! I wonder if there is a jabber server on this box..
root@tangle-rock:/home/opensrf/opensrf-2.0.0# aptitude install jabberd
Couldn’t find package “jabberd”.  However, the following
packages contain “jabberd” in their name:
ejabberd jabberd2 libjabberd2-dev ejabberd-mod-shared-roster-ldap
libjabberd2 jabberd14
Couldn’t find package “jabberd”.  However, the following
packages contain “jabberd” in their name:
ejabberd jabberd2 libjabberd2-dev ejabberd-mod-shared-roster-ldap
libjabberd2 jabberd14
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

root@tangle-rock:/home/opensrf/opensrf-2.0.0# aptitude install ejabberd
The following NEW packages will be installed:
ejabberd erlang-asn1{a} erlang-odbc{a}
# and so on…

Here are the entries to add as root to a stock /etc/hosts file for our example domains:
127.0.1.2    public.localhost    public
127.0.1.3    private.localhost    private

root@tangle-rock:/home/opensrf/opensrf-2.0.0# vi /etc/hosts

127.0.0.1       tangle-rock     localhost.localdomain   localhost
::1              tangle-rock     localhost6.localdomain6 localhost6
127.0.1.1       tangle-rock
127.0.1.2       public.localhost        public          #added 20110714
127.0.1.3       private.localhost       private         #added 20110714

As the root user, change the ownership of the installed files to the opensrf user:
chown -R opensrf:opensrf /openils

root@tangle-rock:/home/opensrf/opensrf-2.0.0# chown -R opensrf:opensrf /openils

As the root user, stop the ejabberd service:
/etc/init.d/ejabberd stop
root@tangle-rock:/home/opensrf/opensrf-2.0.0# service ejabberd stop
Stopping jabber server: ejabberd.

As the root user, edit /etc/ejabberd/ejabberd.cfg to increase the default limits (meant for a small instant messaging server) to something reasonable for our use of XMPP as a message bus:
Change
{hosts, ["localhost"]}.
to
{hosts, ["localhost", "private.localhost", "public.localhost"]}.

Increase the maximum number of times a user can log in concurrently:
Newer versions of ejabberd: {access, max_user_sessions, [{10, all}]}., then change it to {access, max_user_sessions, [{10000, all}]}. # This was what I found
Older versions of ejabberd: change {max_user_sessions, 10}. to {max_user_sessions, 10000}.
Change all three occurrences of max_stanza_size to 2000000.
Change both occurrences of maxrate to 500000.
Comment out the {mod_offline line by placing two % signs in front. # It was easier to find these occurrences in gedit than vi…

# Still as root, restart ejabberd
root@tangle-rock:/home/opensrf/opensrf-2.0.0# service ejabberd start
Starting jabber server: ejabberd.
root@tangle-rock:/home/opensrf/opensrf-2.0.0#

As the root user, register your “router” and “opensrf” ejabber users for the OpenSRF router service on each domain. The users should have different passwords on each domain. These users will correspond to your configuration in opensrf_core.xml:
# Syntax for registering a user with ejabberdctl
# ejabberdctl register <user> <domain> <password>
ejabberdctl register router private.localhost <secret>
ejabberdctl register opensrf private.localhost <secret>
ejabberdctl register router public.localhost <secret>
ejabberdctl register opensrf public.localhost <secret>

# As the opensrf user, create the /openils/conf/opensrf_core.xml and /openils/conf/opensrf.xml configuration files from the example templates:
cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml
cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml
# Edit /openils/conf/opensrf_core.xml to change the Jabber usernames and passwords as follows. I’m using XPath syntax on the left-hand side to indicate the position in the XML file:
/config/opensrf/username = opensrf
/config/opensrf/passwd = password for private.localhost opensrf user
/config/gateway/username = opensrf
/config/gateway/passwd = password for public.localhost opensrf user
/config/routers/router/transport – first entry, where transport/server == public.localhost :
username = router
password = password for public.localhost router user
/config/routers/router/transport – second entry, where transport/server == private.localhost :
username = router
password = password for private.localhost router user
Copy /openils/conf/srfsh.xml.example to .srfsh.xml in the home directory of each user you want to use to run the srfsh command line client for testing OpenSRF, and edit .srfsh.xml as follows:
domain is the router hostname (following our domain examples, private.localhost will give your srfsh access to all OpenSRF services, while public.localhost will only give you access to those OpenSRF services that are publicly exposed)
username and password must match your opensrf ejabber user for the chosen domain
logfile is the full path for a log file to which that user has write access
<?xml version=”1.0″?>
<!– This file follows the standard bootstrap config file layout found in opensrf_core.xml –>
<srfsh>
<router_name>router</router_name>
<domain>private.localhost</domain>
<username>opensrf</username>
<passwd>privsrf</passwd>
<port>5222</port>
<logfile>/tmp/srfsh.log</logfile>
<loglevel>3</loglevel>
</srfsh>

As the opensrf user, set the path of the opensrf user’s .bashrc file:
echo “export PATH=/openils/bin:\$PATH” >> ~/.bashrc
exit

opensrf@tangle-rock:~$ echo “export PATH=/openils/bin:\$PATH” >> ~/.bashrc

Before starting OpenSRF, ensure that your Jabber and memcached daemons are running. As the root user:
/etc/init.d/ejabberd start
/etc/init.d/memcached start

root@tangle-rock:/home/opensrf/opensrf-2.0.0# /etc/init.d/ejabberd restart
Restarting jabber server: ejabberd.
root@tangle-rock:/home/opensrf/opensrf-2.0.0# /etc/init.d/memcached restart
Restarting memcached: memcached.
# Restart has less potential to damage anything, though it will drop active connections just like running start on a running service.

Starting OpenSRF with the start_all option starts the OpenSRF router, Perl services, and C services. As the opensrf user, start OpenSRF (NOTE: use the -l flag only if you wish to force the hostname for the <hosts> section in opensrf.xml to be localhost):
osrf_ctl.sh -l -a start_all

osrf_ctl.sh -a start_all

# Failed to start
opensrf@tangle-rock:~/opensrf-2.0.0$ osrf_ctl.sh -a start_all
Starting OpenSRF Router
Starting OpenSRF Perl
Can’t locate Unix/Syslog.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/local/share/perl/5.10.1/OpenSRF/Utils/Logger.pm line 6.
BEGIN failed–compilation aborted at /usr/local/share/perl/5.10.1/OpenSRF/Utils/Logger.pm line 6.
Compilation failed in require at /openils/bin/opensrf-perl.pl line 20.
BEGIN failed–compilation aborted at /openils/bin/opensrf-perl.pl line 20.

# Suggestion at http://lists.clug.org.za/pipermail/clug-tech/2007-December/039222.html to handle failed Perl issue

opensrf@tangle-rock:~/opensrf-2.0.0$ apt-cache search syslog | grep perl
libnet-server-perl – An extensible, general perl server engine
libunix-syslog-perl – Perl interface to the UNIX syslog(3) calls
libgetargs-long-perl – Perl module to parse long function arguments
liblog-dispatchouli-perl – simple wrapper around Log::Dispatch
liblogger-syslog-perl – Logger::Syslog — an simple wrapper over Sys::Syslog for Perl
libparse-syslog-perl – Perl module for parsing syslog entries
libsys-syslog-perl – Perl interface to the UNIX syslog(3) calls
perl – Larry Wall’s Practical Extraction and Report Language
opensrf@tangle-rock:~/opensrf-2.0.0$

root@tangle-rock:/home/opensrf/opensrf-2.0.0# aptitude install perl libnet-server-perl libunix-syslog-perl libgetargs-long-perl liblog-dispatchouli-perl liblogger-syslog-perl libparse-syslog-perl libsys-syslog-perl
The following NEW packages will be installed:
libcommon-sense-perl{a} libdata-optlist-perl{a} libgetargs-long-perl
libio-multiplex-perl{a} libjson-perl{a} libjson-xs-perl{a}
liblog-agent-perl{a} liblog-dispatch-array-perl{a}
liblog-dispatch-perl{a} liblog-dispatchouli-perl liblogger-syslog-perl
libnet-cidr-perl{a} libnet-server-perl libparams-util-perl{a}
libparams-validate-perl{a} libparse-syslog-perl libstring-flogger-perl{a}
libsub-exporter-perl{a} libsub-install-perl{a} libsys-syslog-perl
libtest-deep-perl{a} libtry-tiny-perl{a} libunix-syslog-perl
0 packages upgraded, 23 newly installed, 0 to remove and 0 not upgraded.
Need to get 933 kB of archives. After unpacking 3,826 kB will be used.
Do you want to continue? [Y/n/?]
# install follows.

# Now the failure is
Can’t locate UNIVERSAL/require.pm in @INC ….
suggestion from

http://comments.gmane.org/gmane.education.libraries.open-ils.general/4009

“See if UNIVERSAL is present
perl -MUNIVERSAL::require -e 1

# This has same error
so
apt-get install libuniversal-require-perl

# Now we can all wonder why something called “universal” is not installed with the big perl install I just did.
# error: Can’t locate DateTime.pm in @INC
# Help from http://ubuntuforums.org/archive/index.php/t-1279901.html
/usr/bin/perl install-module.pl List::MoreUtils  # Failed
apt-get install libpq-dev        # already newest version
# Since I couldn’t exactly find the right datatime modulre, I just went to synaptic and searched for all perl-related stuff, and then filtered that by “date’  I am installing about 123 packages, but I am tired of hunting one at a time.

# Finally, it started right up – automagically

opensrf@tangle-rock:~/opensrf-2.0.0$ osrf_ctl.sh -a start_allOpenSRF Router already started : 9608 9609
Starting OpenSRF Perl
* starting all services for tangle-rock.TLC
Starting OpenSRF C (host=tangle-rock.TLC)

# Testing openSRF
# Once you have installed and started OpenSRF, test your connection to OpenSRF via srfsh:
Start srfsh and try calling the add method on the OpenSRF math service:
/openils/bin/srfsh
srfsh#  request opensrf.math add 2 2
# Fails!
opensrf@tangle-rock:~/opensrf-2.0.0$ /openils/bin/srfsh
srfsh# request opensrf.math add 2 2

Received no data from server

————————————
Request Time in seconds: 0.003072
————————————

srfsh# exit
opensrf@tangle-rock:~/opensrf-2.0.0$

# The evergreen folks say “Don’t Panic! gather log files and such from /openils/var/log and the configuration files and send them to the support lists.

#  That is where this is all going now.

The Evergreen Project develops an open source ILS (integrated library system) used by approximately 800 libraries.  The software, also called Evergreen, is used by libraries to provide their public catalog interface as well as to manage back-of-house operations such as circulation (checkouts and checkins), acquisition of library materials, and (particularly in the case of Evergreen) sharing resources among groups of libraries.

The Evergreen Project was initiated by the Georgia Public Library System in 2006 to serve their need for a scalable catalog shared by (as of now) approximately 250 public libraries in the state of Georgia.  After Evergreen was released, it has since been adopted by a number of library consortia in the US and Canada as well as various individual libraries, and has started being adopted by libraries outside of North America.

http://open-ils.org/about.php

To get Evergreen Running, I have to do a lot of work on my server.  Since I am taking notes as I go, here is the transcript of those notes.  Where I am using passwords, I will instead use the convention of <secret>, so instead of saying “My password is T^T87uugf7h,” I will say “My password is <secret>.”  Things behind a “#” sign are comments – either comments in the files themselves or notes to my readers

The first thing I had to do is set up postgreSQL.  I had it set up a while ago, but I couldn’t remember any of the configurations I had done or the passwords or the users, so it seemed like the best solution was to completely remove it and start again.

——————-

######################
# Configure PostgreSQL
######################
With help from:

http://socrateos.blogspot.com/2011/07/installing-postgresql-90-on-ubuntu-1104.html

Completely remove Postgresql

Install postgresql8.4
Postgresql-client
Postgresql-contrib

==============
wolf@tangle-rock:~$ psql -V
psql (PostgreSQL) 8.4.8
contains support for command-line editing

wolf@tangle-rock:~$ finger postgresql
Login: postgres                   Name: PostgreSQL administrator
Directory: /var/lib/postgresql          Shell: /bin/bash
Never logged in.
No mail.
No Plan.

wolf@tangle-rock:~$ su postgres
Password:
su: Authentication failure
wolf@tangle-rock:~$ sudo passwd postgres
Enter new UNIX password:  <secret>
Retype new UNIX password:
passwd: password updated successfully

postgres@tangle-rock:/home/wolf$ psql
psql (8.4.8)
Type “help” for help.

postgres=# select version();
# opens a less-like interface… (q to exit)

version
——————————————————————————————————————
PostgreSQL 8.4.8 on i686-pc-linux-gnu, compiled by GCC gcc-4.5.real (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2, 32-bit
(1 row)

postgres=# alter user postgres with password ‘<secret>’;
ALTER ROLE
postgres=# \q   # quit psql
postgres@tangle-rock:/home/wolf$ exit
exit
wolf@tangle-rock:~$

6.Configure PostgreSQL Server
wolf@tangle-rock:~$ cd /etc/postgresql/8.4/main/
wolf@tangle-rock:/etc/postgresql/8.4/main$ ls -al
total 48
drwxr-xr-x 2 postgres postgres  4096 2010-12-01 17:59 .
drwxr-xr-x 3 postgres postgres  4096 2010-12-01 17:59 ..
-rw-r–r– 1 postgres postgres   316 2010-12-01 17:59 environment
-rw-r–r– 1 postgres postgres   143 2010-12-01 17:59 pg_ctl.conf
-rw-r—– 1 postgres postgres  3822 2010-12-01 17:59 pg_hba.conf
-rw-r—– 1 postgres postgres  1631 2010-12-01 17:59 pg_ident.conf
-rw-r–r– 1 postgres postgres 16975 2010-12-01 17:59 postgresql.conf
-rw-r–r– 1 postgres postgres   378 2010-12-01 17:59 start.conf

wolf@tangle-rock:/etc/postgresql/8.4/main$ su postgres
Password: <secret>
postgres@tangle-rock:/etc/postgresql/8.4/main$ mkdir bak20110713
postgres@tangle-rock:/etc/postgresql/8.4/main$ cp *.conf bak20110713/
postgres@tangle-rock:/etc/postgresql/8.4/main$ ls bak20110713/
pg_ctl.conf  pg_hba.conf  pg_ident.conf  postgresql.conf  start.conf

postgres@tangle-rock:/etc/postgresql/8.4/main$ vi pg_hba.conf
=============
# IPv4 local connections:
#host    all         all         127.0.0.1/32          md5
host    all         all         127.0.0.1/32          trust
# IPv6 local connections:
:wq

postgres@tangle-rock:/etc/postgresql/8.4/main$ vi postgresql.conf
=============
# Enabled 20110714

#——————————————————————————
# ERROR REPORTING AND LOGGING
#——————————————————————————
log_destination = ‘stderr’

logging_collector = on

log_directory = ‘pg_log’
log_filename = ‘postgresql-%Y-%m-%d_%H%M%S.log’

log_truncate_on_rotation = off

log_rotation_age = 1d

log_rotation_size = 10MB

postgres@tangle-rock:/etc/postgresql/8.4/main$ mkdir pg_log
postgres@tangle-rock:/etc/postgresql/8.4/main$ # Made log directory