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. Problem with agent log: could not open

Problem with agent log: could not open

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 37.4k 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.
  • B
    B
    blairmc96
    wrote on last edited by
    #1

    I have a Windows Server 2008 box with the 2.2.15 agent installed and get an alarm after adding the node "Problem with agent log: could not open"

    I've removed and reinstalled and installed it just like all my other servers, but am not sure why this one is failing.  I also tried to reapply the permissions down the tree from c:\netxms, but that didn't work either.

    If I run the agent manually, I get this below.

    C:\NetXMS\bin>nxagentd -D6
    ERROR: Cannot open log file, logs will be written to syslog with debug level 1
    

    When I do a full poll, everything seems to run fine (see below)

    [2019.06.06 10:18:28] **** Poll request sent to server ****
    [2019.06.06 10:18:28] Poll request accepted
    [2019.06.06 10:18:28] Starting configuration poll for node CHRONOS
    [2019.06.06 10:18:28] Capability reset
    [2019.06.06 10:18:28] Checking node's capabilities...
    [2019.06.06 10:18:28]    Checking NetXMS agent...
    [2019.06.06 10:18:28]    NetXMS native agent is active
    [2019.06.06 10:18:28]    NetXMS agent version changed to 2.2.15
    [2019.06.06 10:18:28]    Platform name changed to windows-x64
    [2019.06.06 10:18:28]    System description changed to Windows CHRONOS 6.1.7601 Windows Server 2008 R2 Build 7601 Service Pack 1 AMD-64
    [2019.06.06 10:18:28]    Reading list of available Windows Performance Counters...
    [2019.06.06 10:18:38]    75 counters read
    [2019.06.06 10:18:39]    Checking SNMP...
    [2019.06.06 10:19:01] Capability check finished
    [2019.06.06 10:19:01] Checking interface configuration...
    [2019.06.06 10:19:01] Interface configuration check finished
    [2019.06.06 10:19:01] Checking node name
    [2019.06.06 10:19:01] Node name is OK
    [2019.06.06 10:19:01] Reading list of installed software packages
    [2019.06.06 10:19:01] Got information about 71 installed software packages
    [2019.06.06 10:19:02] Finished configuration poll for node CHRONOS
    [2019.06.06 10:19:02] Node configuration was changed after poll
    [2019.06.06 10:19:02] **** Poll completed successfully ****
    

    Any help is appreciated!

    1 Reply Last reply
    0
    • T
      T
      Tursiops
      wrote on last edited by
      #2

      Can you post your Agent configuration file, please?

      1 Reply Last reply
      0
      • B
        B
        blairmc96
        wrote on last edited by
        #3

        Here it is.  It's the same as all the rest.

        Thanks!

        #
        # NetXMS agent configuration file
        # Created by agent installer at Wed May 29 09:41:58 2019
        #
        
        MasterServers = ###.###.###.### (NetXMS server IP)
        ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
        LogFile = {syslog}
        FileStore = C:\NetXMS\var
        SubAgent = ecs.nsm
        SubAgent = filemgr.nsm
        SubAgent = ping.nsm
        SubAgent = logwatch.nsm
        SubAgent = portcheck.nsm
        SubAgent = winperf.nsm
        SubAgent = wmi.nsm
        
        1 Reply Last reply
        0
        • T
          T
          Tursiops
          wrote on last edited by
          #4

          You haven't configured a log file as such.
          It's possible the error message is misleading. {syslog} on Windows means it will log to the Windows Event Log, not a file.

          If you want an actual log file, you would need to enter the full path/filename, e.g.

          LogFile = C:\NetXMS\nxagentd.log
          
          1 Reply Last reply
          0
          • B
            B
            blairmc96
            wrote on last edited by
            #5

            Thanks for the help, that seemed to work, but I've got many other Windows servers with the exact same settings that work just fine.

            I appreciate the help.

            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