Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. What logs should I be looking at? How do I interpret the messages within these?

    What logs should I be looking at? How do I interpret the messages within these?

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Question
    2. Answer
      1. LOG.VOYAGER
      2. /VAR/ADM/MESSAGES
      3. ALERT_LIBR.LOG
    • Product: Voyager
    • Product Version: 6.5.3

    Question

    What logs should I be looking at? How do I interpret the messages within these logs?

    Answer

    There are 3 logs of importance that you will want to monitor:

    • /var/adm/messages ( log file that tracks hardware-related errors.)
    • /m1/voyager/xxxdb/log/log.voyager (logs Voyager-related errors.)
    • alert_LIBR.log (Oracle errors)
    LOG.VOYAGER

    You will want to look out for the words, WARNING, ERROR, FAILURE, etc. in this log.

    log.voyager will usually have alot of warnings" on a daily basis, related to failed searches and other minor details you usually don't need to be concerned about. (On the contrary, /var/adm/messages will have messages logged on a much lesser basis, and ERROR messages here almost always demand closer attention.)

    There's no way to define in and of itself, which message is crucial and which one isn't. All sorts of stuff is in there, and under normal circumstances none of it is crucial. It tells what has been going on when, which helps paint a picture of what was going on from the servers' perspective at any given time.

    The file is for troubleshooting and is not useful for preventative monitoring. If you have a problem, report it, and Support will look at log.voyager if necessary.

    /VAR/ADM/MESSAGES

    This log tracks hardware-related errors, like scsi failures, full disk-space, and the like.

    If Voyager is completely down, this is the first place you want to look. Call Support immediately if you observe any peculiar messages here. Error messages here demand immediate attention.

    ALERT_LIBR.LOG

    The third log file to be concerned about is alert_LIBR.log. This tracks Oracle errors. To get to this log, do the following as oracle user:

    cd $ORA_LOG

    more alert_LIBR.log

    Again, look for the following words in these logs: ERROR, WARNING, FAILURE, etc.
    It will take "practice" in figuring out which error messages are important and which ones are not."


    • Article last edited: 06-Mar-2015
    View article in the Exlibris Knowledge Center
    1. Back to top
      • What kind of record validation does Voyager Global Data Change do?
      • What populates address fields on Order Claim Notices?
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    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