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. NXAGENTD 100% Processor

NXAGENTD 100% Processor

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 12.8k 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.
  • N
    N
    Netvoid
    wrote on last edited by
    #1

    Windows 2003 R2
    32bit systems running the 1.04 client

    The netXMS client is monitoring system, security, and application windows event logs and 1 file log from a jboss/tomcat server using the following configuration. Whenever I restart the jboss/tomcat portal service the NXAGENTD peg's the processor at 100% utilization and my server takes 30 minutes to restart the portal. Even when the portal finally completes and is started the NXAGENTD service continues to hammer the processor until I kill the process and restart the service.

    I have this exact scenario happening on two different systems. Both are the same environment.

    Any input on how I can keep the process from going crazy and/or pinpoint why it is happening? The only thing I have played around with is the processAll option, I have turned that on and off a couple times.

    <parser processAll="0">
      <file>C:\portal\server\default\log\server.log</file>
      <macros>
          <macro name="timestamp">[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2},[0-9]{3}</macro>
      </macros>
      <rules>
          <rule break="1">
            <match>@{timestamp}.ERROR (.*)</match>
            <event params="1">100002</event>
          </rule>
            </rules>
    </parser>

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

      Hi!

      Could you please test agent version 1.0.6 (available at https://www.netxms.org/download/agent_packages/nxagent-1.0.6.exe)? There are some changes in text log file monitoring, and it may work better in your case.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • N
        N
        Netvoid
        wrote on last edited by
        #3

        Victor,

        Yes, thank you that seemed to correct the processor pegging issue.

        Regards,

        Clark

        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