Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. LogWatch Cannot Format Message

LogWatch Cannot Format Message

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 13.7k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P
    P
    peter
    wrote on last edited by
    #1

    I am forwarding windows server 2003 events to NetXMS. On one of the servers Snort is running and it logs events into the application log that look as follows:

    Event Type: Warning
    Event Source: snort
    Event Category: None
    Event ID: 1
    Date: 2/6/2013
    Time: 1:16:06 PM
    User: N/A
    Computer: MDCFW
    Description:
    The description for Event ID ( 1 ) in Source ( snort ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [1:1448:13] MISC MS Terminal server request [Classification: Generic Protocol Command Decode] [Priority: 3] {TCP} XXX.xxx.xxx.xxx:4199 -> xxx.xxx.xxx.xxx:3389.

    These events are not forwarded but instead I get a message that LogWatch cannot format the event message.

    Is there a work-around for this or perhaps a method to grab snort events directly?

    Thanks
    Peter

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi!

      Actually, event log tells you the same: that there are no description for the message. Looks like Snort don't register event source correctly. Quick search gives couple of people with same problem but no solution. I would suggest to reconfigure Snort to send it's log to text file instead of WIndows Event Log, and capture events from that text log file.

      Best regards,
      Victor

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups