Skip to main content
ExLibris

  • Subscribe by RSS
    • Aleph
    Ex Libris Knowledge Center

    ue_nn daemon (such as ue_21) incorrectly started for all libraries by aleph_startup

    1. Last updated
    2. Save as PDF

     

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

     

    Description: 
    A daemon, such as the ue_21 publishing daemon, is being started for *all* libraries by aleph_startup when it should be started for only certain libraries. 

    If the problem is with ue_21, many of the processes (as seen in "top") have very high CPU. 

     

    Resolution: 
    The aleph_start.private incorrectly had: 
    setenv PUB_STARTUP_LIBS "$ALEPH_LIBS xxx01 xxx30" 

    when it should have had: 
    setenv PUB_STARTUP_LIBS "$PUB_STARTUP_LIBS xxx01 xxx30" 

    The same thing could happen with other xxx_STARTUP_LIBS definitions, but the problem is much more severe in the case of ue_21 because of the bug described in Article 000044900 (ue_21 has *very* high CPU or "NO PUBLISHING LIBRARY : EXITING") linked to below. 

    The solution is to correct aleph_start.private and do "source aleph_start" to make the change be in effect.

     

    Additional Info / Related Articles    
    Article:   ue_21 has *very* high CPU or "NO PUBLISHING LIBRARY : EXITING" 

     

     

    • Article last edited: 02-Mar-2016