KnowledgeBase Event Repository

This site is the central interface to the Adiscon Event Repository

  • Details for this entry
  • Vendor:
    Adiscon
    Software/Device:
    rsyslog
    Syslogtag:
    rsyslogd-2066
    Full Description:
    module could not be loaded
    A problem occurred during dlopen()ing a loadable module (e.g. an input or output plugin).

    Most common causes for this are that the module either does not exist or has incorrect permission settings. Permission problems are less likely if rsyslogd runs as root, what it does by default.

    Note that most packages only distribute a very limited set of plugins via the core rsyslog package. To use enhanced functionality (like the file input, database or mail outputs and many more), you need to install additional packages (there names are distro-specific, so they can not be given here). When building from source, check the ./configure output on which modules are built. A summary is given at the end of the configure run. Use "./configure -help" to see which options enable which modules.
    Search for this Event::
    Search in Knowledge Base  •  Search in this Forum  •  Search on Windows-Expert.com
  • Accessed: 470

Discuss the Event

Discussion for KB Entry 6897 - Syslogtag rsyslogd-2066

by knowledgebase on Mon Jul 27, 2009 8:01 am

This is the discussion thread for the Knowledge Base Entry 6897

Vendor: Adiscon
Software/Device: rsyslog
Syslogtag: rsyslogd-2066
Link to KB Entry

Short Description:
module could not be loaded
User avatar
knowledgebase
Frequent Poster
 
Posts: 128
Joined: Wed May 28, 2008 10:09 am


About the KnowledgeBase Event Repository

This is a repository of known Windows Events, hopefully together with a description of what it means, when it appears and how to troubleshoot it. The event repository was initially provided as a tool for parser creation but has since evolved. It is now part of the overall knowledgebase in the hope that it provides a useful service to the community. Please add your comments and questions (which we try to answer), as this increases the event repository usefulness for all of us.

Return to

cron