Skip to main content
ExLibris

Knowledge Assistant

BETA
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Apache startup on reboot

    Apache startup on reboot

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description:
    When rebooting the production server I get the following message::

    "apache start

    ./start_stop: /exlibris/aleph/u16_1/alephe/apache/bin/apachectl_auto: not found"

    However, apache is running ok after the reboot, but when trying to restart apache via util w I get the following:

    "/exlibris/aleph/u17_7/alephe/apache/bin/apachectl restart: httpd not running, trying to start
    (125)Address already in use: make_sock: could not bind to address [::]:80
    no listening sockets available, shutting down
    Unable to open logs
    /exlibris/aleph/u17_7/alephe/apache/bin/apachectl restart: httpd could not be started
    "

    This is despite the fact that apache is running. 

    Any ideas why this is happening?

     

    Resolution:
    At the moment both ver 16 and ver 17 apache are defined to be started upon reboot in /exlibris/startup/init.dat:

    # apache
    Y:apache:root:httpd:/exlibris/aleph/u17_7:../a17_7:apachectl_auto:apachectl
    Y:apache:root:httpd:/exlibris/aleph/u16_1:../a16_1:apachectl_auto:apachectl

    You need to modify this file - either remove ver 16 line or set it to N:

    N:apache:root:httpd:/exlibris/aleph/u16_1:../a16_1:apachectl_auto:apachectl

    That's why ver 17 apache started fine this morning, and ver 16 one gave an error.

    To start apache from util w, you need to stop it first.

    ps -ef |grep apach
    kill [pid]

    Note: If you have multiple instances (such as Prod and Test) on this server, make sure that the apache processes you are killing are for the instance you are working with.

     

     


    • Article last edited: 26-Jun-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Apache startup fails: "libgcc_s.so.1: open failed: No such file or directory"
      • Apache version used with Aleph 22/23
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved