Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    No OPAC after move to production server: "503 Service Temporarily Unavailable"

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    This morning we completed the transfer to our new production server: libprddb1. We get "503 Service Temporarily Unavailable" trying to access the OPAC.

    Our two web servers are libprdw1 and libprdw1. We use netscaler (libweb) as a load balancer; currently, it is only pointing at libprdw2. I know that there has to be a configuration error somewhere, but I don't see it.

    I don't know if this has any bearing on the situation, but I'm not able to stop and start services through the util-w menu.

    Resolution:
    I changed the reference in www_server.conf on both web servers to point to libweb instead of libprddb1. I ran aleph_shutdown and aleph_startup, and apachectl stop and apachectl_auto on both web servers. I had to kill the existing www servers on libprddb1 (located using ps -ef), then was able to restart them.
    The OPAC is now running from libprdw1. I can go to http://libprdw1.lib.abc.edu/F?, enter a query and the URL switches correctly to libweb.lib.abc.edu.

    Preceding analysis:

    Connected to libprddb1, when I do util w/1/3, I see this:
    | 4991 | 5259 | WWW Server | Nov 26 04:48:42 | Free
    | 4991 | 5429 | WWW Server c | Nov 26 04:48:42 | Free
    | 4991 | 5430 | WWW Server c | Nov 26 04:48:42 | Free
    | 4991 | 5431 | WWW Server c | Nov 26 04:48:42 | Free
    | 4991 | 5433 | WWW Server c | Nov 26 04:48:42 | Free

    But ps -ef shows this:
    libprddb1>> ps -ef | grep www
    aleph 9204 8898 0 08:55 pts/3 00:00:00 grep www
    aleph 28571 1 0 04:40 ? 00:00:00 csh -f /exlibris/aleph/a18_1/aleph/proc/www_server 4991 80 5
    aleph 28619 28571 0 04:40 ? 00:00:00 /exlibris/aleph/a18_1/aleph/exe/www_server_main -p 4991 -v
    aleph 28854 28619 0 04:40 ? 00:00:05 /exlibris/aleph/a18_1/aleph/exe/www_server_main -p 4991 -v
    aleph 28855 28619 0 04:40 ? 00:00:00 /exlibris/aleph/a18_1/aleph/exe/www_server_main -p 4991 -v
    aleph 28856 28619 0 04:40 ? 00:00:00 /exlibris/aleph/a18_1/aleph/exe/www_server_main -p 4991 -v
    aleph 28857 28619 0 04:40 ? 00:00:00 /exlibris/aleph/a18_1/aleph/exe/www_server_main -p 4991 -v
    aleph 28858 28619 0 04:40 ? 00:00:00 /exlibris/aleph/a18_1/aleph/exe/www_server_main -p 4991 -v

    I assume that these processes (28619, etc.) are actually running on libprddb1 -- though not being used, since aleph_start has:
    setenv WWW_HOST libweb.lib.abc.edu

    so one question is where the processes we see in the util w/1/3 (5259, etc.) are running?

    I suppose util w/1/3 is going to look for them on libweb.lib.abc.edu, but when I try to connect there, there is no response.

    I can connect to libprdw1, but I don't see these processes running there.

    Also, the $LOGDIR www_server logs show that, though the new www_server_4991.log, started at 5:27, has not been written to, the (old) www_server_4991.log.2611.0523 log is continuing to be written to! :

    libprddb1.lib.abc.edu-18(1) ABC01-ALEPH>>ls -lrt *www*
    -rw-rw-r-- 1 aleph exlibris 439 Nov 3 16:24 www_server_4991.log.1011.123724
    -rw-rw-r-- 1 aleph exlibris 393 Nov 10 12:37 www_server_4991.log.1011.123838
    -rw-rw-r-- 1 aleph exlibris 1086193 Nov 20 11:08 www_server_4991.log.2011.1111
    -rw-r--r-- 1 aleph exlibris 449 Nov 20 11:18 www_server_4991.log.2611.0440
    -rw-rw-r-- 1 aleph exlibris 388 Nov 26 05:23 www_server_4991.log.2611.0527
    -rw-rw-r-- 1 aleph exlibris 388 Nov 26 05:27 www_server_4991.log
    -rw-r--r-- 1 aleph exlibris 448391 Nov 26 09:14 www_server_4991.log.2611.0523

    Note: KB 16384-27826 has a different cause of this same message.

    • Article last edited: 10/8/2013