Forum OpenACS Q&A: AOLServer Troubleshooting Tree (stuck at loading ACS pages)

I am bringing up the ACS system 3.2.2.b3 and also installing AOLServer
3.0 from the tar file sources. The host machine is RedHat 6.1

Thanks to Ben Adida, Robert Mello and Phil Greenspun and others for
this fabulous system.

The frustruation level increases as the power of the number of things
wrong at the same time, and as the reciprocal of your knowledge. Well
sort of! Depending on your sense of humor!

I have been trying to come up with a troublesooting tree ( tests and
results ) to speed the ACS installation process.

Here is a troubleshooting tree for getting AOLServer configured. And I
am stuck down at the bottom. There are many ways to do this, but I am
trying to phrase all this for a new user.

Starting from AOLServer 3.0 "make install" that copies files to
/tmp/aolserver

Following www/doc/acspg/INSTALL (March 2000 version) section 4.1
"Configuring AOLserver"

Did the task of creating a /tmp/aolserver/nsd.ini file with all the
parameters suggested

Used /tmp/aolserver/bin/translate-ini shell script to convert nsd.ini
to the required *.tcl initialization file format. Roughly like this
      ./bin/translate-ini < ./nsd.ini > convertedfromnsd.ini

And then append that file to the nsd.tcl file:

cp nsd.tcl nsd.tcl.original          # save a copy of original

cat convertedfromnsd.ini >> nsd.tcl  #

The first test:
Open a window or open another session and watch the log file:

tail -f /tmp/aolserver/log/server.log

Start up AOLserver:

./bin/nsd -k -u nsadmin -t ./nsd.tcl  # must be in /tmp/aolserver dir

Switch to the tail window and examine the output.

Acceptance test: look for
"Notice: nssock: listening on http://anita.specialparents.com:;8000
(192.168.1.3:8000)          # Your URL will appear instead

Here is a series of grep commands to scan the server log file:

grep -i error log/server.log | more  # Caseless search of server log
                                      # for problems parsing nsd.tcl

Note  : Error could not load "/tmp/aolserver/bin/nscp.so"
Meaning: The file exists. Something is wrong.
Action : Mentioned elsewhere in these discussions.

grep -i postgres.so log/server.log    # Is postgres driver loading?

Note  :    Result:comes up blank.
Meaning: The postgres driver isn't loading, I think
Action : Answer is in these Discussion pages, RTFD

grep pageroot log/server.log          # Where is starting web page?

Note    :  pageroot = /tmp/aolserver/servers/server1/pages
Meaning :  Seems to be where root of web site is located.
        :  Compare to page you see with lynx access below.

-----  Now to the ACS system SMOKE TEST!

Functional test for AOLServer

connect to the server using lynx, going to the connection point
announced above:

lynx http://anita.specialparents.com:8000  # Your URL may differ

Result    : Welcome to AOLserver 3 (html web page)
Meaning    : AOLserver is answering incoming requests on port 8000
            But I am seeing the AOLServer html file named as
            pageroot (see above grep).
            The problem now is to make AOLserver deliver
            an ACS starting page.

Thanks for adding to this troubleshooting tree and pointing out the
path.

Hi Lee,

I think the best you can do is download the latest version of OpenACS (3.2.2 final). It has many bug fixes and improvements. The documentation provides a much more 'concrete' Installation Guide and comes with Simples install guides for AOLserver and PostgreSQL to help you get jump started as fast as possible.

Also, download the security patches and install them (available at the homepage for openacs.org). A new version of OpenACS (that will have the security patches applied and some other fixes) will be release very soon (this week or next).