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 file lock

Logwatch file lock

Scheduled Pinned Locked Moved Support
5 Posts 3 Posters 39.9k 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.
  • Y
    Y
    yashii
    wrote on last edited by
    #1

    On a Windows system, I'm executing an external script through the nxagent that writes to a .txt file.
    This file is monitored for changes by the logwatch subagent.

    When the external script tries to write to that .txt file, the script's own log shows that the file is locked by the nxagent.
    Is there any way to keep the agent from permanently locking the file?

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

      Hi,

      agent opens file being monitored with "shared for write" access. However, if application that writes to the file attempts to open it without specifying "shared for read" option it will get file open error. In upcoming 2.2.5 release we have added log parser option "keepOpen" that can be set to false to instruct parser to re-open file every time to get new records.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • S
        S
        Spheron
        wrote on last edited by
        #3

        Hi Victor,

        does this option also apply to access to the Windows event log?

        Greets
        Marco

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

          Hi,

          no, it's irrelevant for Windows Event Log. Agent uses appropriate Windows API to access events in event log.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • S
            S
            Spheron
            wrote on last edited by
            #5

            I asked because I still had the same problems with the agent update from V2.2.3 to V2.2.4 that I had described here

            https://www.netxms.org/forum/installation/install-agent-2-2-1-fails/

            Maybe i had same Problem at Agent Update as the user who has opened this Thread:

            https://www.netxms.org/forum/installation/upgrading-agents/

            Greets
            Marco

            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