Index: openacs-4/packages/acs-core-docs/www/aolserver.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/aolserver.html,v diff -u -r1.52.2.12 -r1.52.2.13 --- openacs-4/packages/acs-core-docs/www/aolserver.html 19 Nov 2016 09:21:52 -0000 1.52.2.12 +++ openacs-4/packages/acs-core-docs/www/aolserver.html 6 Jan 2017 09:18:41 -0000 1.52.2.13 @@ -7,7 +7,7 @@ Aolserver or Postgres. Several people have reported problems while trying to install using apt-get instead of from source. If you have the time to debug these - and submit what you did, that's great, but if not, you + and submit what you did, that's great, but if not, you should stick to installing from source.

  1. Unpack the Aolserver tarball. Download the aolserver tarball and unpack it.

    [root root]# cd /usr/local/src
 [root src]# wget --passive http://uptime.openacs.org/aolserver-openacs/aolserver3.3oacs1.tar.gz
@@ -43,7 +43,7 @@
           the environment variables properly.
         
    conf-inst should contain the
           location where AOLserver is to be installed.  Overwrite the
-          tarball's default value with our default value, /usr/local/aolserver:
    [root aolserver]# echo "/usr/local/aolserver" > conf-inst
+          tarball's default value with our default value, /usr/local/aolserver:
    [root aolserver]# echo "/usr/local/aolserver" > conf-inst
 [root aolserver]#
    conf-make should contain the
           name of the GNU Make command on your system. It defaults to
           gmake.  Debian users: ln -s /usr/bin/make /usr/bin/gmake.
    Set an environment variable that the nspostgres driver
@@ -81,7 +81,7 @@
 	  sets database environment variables before starting
 	  AOLserver; this allows the AOLserver instance can
 	  communicate with the database.  There is one script each for
-	  Oracle and PostgreSQL.  They don't conflict, so if you plan
+	  Oracle and PostgreSQL.  They don't conflict, so if you plan
 	  to use both databases, install both.
    • Oracle
      [root aolserver]# cd /usr/local/aolserver/bin
 [root bin]# cp /var/tmp/openacs-5.9.0/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle
 [root bin]# chmod 750 nsd-oracle
@@ -145,7 +145,7 @@
 cp libtdom0.7.8.so /usr/local/aolserver/bin/
 cd /usr/local/aolserver/bin
 ln -s libtdom0.7.8.so libtdom.so
    • Install nsopenssl
-      (OPTIONAL)
    • Install Full Text Search with OpenFTS (OPTIONAL)
    • Install nspam (OPTIONAL)
    • Test AOLserver. In order to test AOLserver, we'll run it using the
+      (OPTIONAL)
    • Install Full Text Search with OpenFTS (OPTIONAL)
    • Install nspam (OPTIONAL)
    • Test AOLserver. In order to test AOLserver, we'll run it using the
       sample-config.tcl file provided in the AOLserver distribution,
       under the nobody user and web
       group.  The sample-config.tcl configuration writes to the
@@ -172,8 +172,8 @@
 chmod -R g+w log servers
 ls -l
    Note: AOLserver4.x does not include a default start page, so we create one for this test. Type 
         echo "Welcome to AOLserver" > /usr/local/aolserver40r8/servers/server1/pages/index.html
-      
    Now, we'll run a quick test to ensure AOLserver is running
-          correctly. We'll use the sample config file provided with
+      
    Now, we'll run a quick test to ensure AOLserver is running
+          correctly. We'll use the sample config file provided with
           AOLserver. This file will attempt to guess your IP address and
           hostname. It will then start up the server at port 8000 of that
           IP address.
    [root aolserver]# ./bin/nsd -t sample-config.tcl -u nobody -g web
@@ -182,22 +182,22 @@
 [08/Mar/2003:15:07:18][31175.8192][-main-] Warning: config.tcl: nscp not loaded
 -- user/password is not set.
 [08/Mar/2003:15:07:18][31175.8192][-main-] Notice: config.tcl: finished reading
-config file.
    The first warning, about nsssl, can be ignored.  We won't be using nsssl; we'll be using nsopenssl instead, and we haven't fully configured it yet.  The nscp warning refers to the fact that, without a user and password in the config file, the administrative panel of AOLserver won't load.  We don't plan to use it and can ignore that error as well.  Any other warning or error is unexpected and probably a problem.
    
+config file.

    The first warning, about nsssl, can be ignored. We won't be using nsssl; we'll be using nsopenssl instead, and we haven't fully configured it yet. The nscp warning refers to the fact that, without a user and password in the config file, the administrative panel of AOLserver won't load. We don't plan to use it and can ignore that error as well. Any other warning or error is unexpected and probably a problem.

    Test to see if AOLserver is working by starting Mozilla or Lynx on the same computer and surfing over to your web page. If you browse from another computer and the sample config file - didn't guess your hostname or ip correctly, you'll get a + didn't guess your hostname or ip correctly, you'll get a false negative test. 

    [root aolserver]# lynx localhost:8000

    You should see a "Welcome to AOLserver" page. If this - doesn't work, try going to + doesn't work, try going to http://127.0.0.1:8000/. If this - still doesn't work, check out the Troubleshooting AOLserver section below. Note that you will not be able to browse to the web page from another machine, because AOLserver is only listening to the local address. + still doesn't work, check out the Troubleshooting AOLserver section below. Note that you will not be able to browse to the web page from another machine, because AOLserver is only listening to the local address.

    Shutdown the test server:

    [root aolserver]# killall nsd
 [root aolserver]#

    @@ -207,7 +207,7 @@ but clearly this is not a good tool to use for managing your services in general. We cover this topic in the Keep AOLserver alive section. -

  2. Troubleshooting. If you can't view the welcome page, it's likely there's a +

  3. Troubleshooting. If you can't view the welcome page, it's likely there's a problem with your server configuration. Start by viewing your AOLserver log, which is in /usr/local/aolserver/log/server.log. @@ -231,10 +231,10 @@ set hostname [ns_info hostname] set address [ns_info address]

    - If you get an error that nssock can't get the requested address, you + If you get an error that nssock can't get the requested address, you can set these manually. If you type 0.0.0.0, AOLserver will try to listen on all available addresses. Note: - ns_info address doesn't appear + ns_info address doesn't appear to be supported in current versions of AOLserver.