NSClient++ Help (#1) - CheckEventLog [SOLVED] (#595) - Message List

CheckEventLog [SOLVED]

We are experiencing the windows problem described in the documentation for the File option that only returns the application log and not the system or security log. I really need the system log. Is there a fix that will let nscp access the system log? This is happening across Windows Server versions, nscp versions, and platforms (x64 and x86).

I tried to look first for this but I couldn't find the answer.

  • Message #1816

    This should work.

    Worth noticing is that if the log is not found the "application log" will be used (this is Microsoft behavior) so maybe your names are wrong?

    Note that log files can be renamed with a local name.

    All in all I would say show me the debug log from nsclient++ /test and I will have more to work with.

    Michael Medin

    • Message #1817

      Thanks! It appears that it works fine with /test but not when run as a service. My entire nagios has only application log but now that I just ran as /test I see system log entries for this host. Do I need to set the user name that the service runs as?

      • Message #1818

        Humm, not really sure. Nothing I have encountered before. Which windows version?

        AFAIK all logs are readable by all users but I guess it is technically possible to change this?

        Michael Medin

        • Message #1819

          Ok I just confirmed the issue. When the service login is as installed by nscp installer it only shows me the Application log but if I check the checkbox "Allow service to interact with the desktop" (and restart the service) it then shows the system log errors and warnings. This is for Windows 2008 R2 so far but I can confirm for Windows 2003 R2 soon.

          • Message #1820

            I just installed a new copy of nscp 3.8 x86 from the download site onto Windows Server 2003 R2 and it works without the checkbox in "Allow.." So it appears that its a Windows Server 2008 R2 thing.

          • Message #1821

            On my windows 7 it does not behave like that (I just verified) so could be something in the server editions...

            Let me know if you get the same behavior on w2k3.

            Michael Medin

            • Message #1822

              It appears to be Windows 2008 R2 only so far. W2K3 R2 does not have this problem.

              • Message #1836

                Right, could you raise this as a ticket so I wont forget looking into this?

                Michael Medin

Subscriptions