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

    /etc/init.d/exlibris stop script: "TNS:no listener", etc.

    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    I tried to shutdown both our PROD and TEST servers before the time change.
    As root, /etc/init.d/exlibris stop

    aleph stop


    apache stop

    /exlibris/aleph/u20_2/alephe/apache/bin/apachectl stop: httpd stopped


    apache stop

    /exlibris/aleph/u20_2/alephe/apache/bin/apachectl stop: httpd (no pid file) not running
    rm: cannot remove `/exlibris/aleph/u20_2/alephe/apache/logs/httpd.pid': No such file or directory


    Oracle stop

    Processing Database instance "aleph20": log file /exlibris/app/oracle/product/11 /shutdown.log

    LSNRCTL for Linux: Version 11.1.0.7.0 - Production on 10-MAR-2012 23:50:11

    Copyright (c) 1991, 2008, Oracle. All rights reserved.

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=serfas)(PORT=1521)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    Linux Error: 111: Connection refused
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    Linux Error: 2: No such file or directory

    ------------------------------

    I believe the Apache issue is because we're using HTTPSD, and the shutdown script is attempting to shutdown HTTPD instead of HTTPSD.

    Not sure on the Oracle, as the server's names are valid in /etc/hosts I'm guessing that the Oracle init/shutdown scripts need a FQDN for the server?

    Apache did appear to shutdown, but Oracle is still running.

    As I'll need to restart at least the PROD server after the time change, I'll have to shutdown ORACLE some way, I guess by doing a server software restart. I'll see if you have a doc on manually shutting down Oracle first before I try that.

    Resolution:
    Please note that the startup/shutdown mechanism was working properly, but, the error message was due to a second unnecessary shutdown - which could not occur after the first time,

    We've erased the unnecessary line from the script and no errors will be displayed,


    • Article last edited: 10/8/2013