Blog
- Home
- Blog
WMI Error: Login to remote object in Nagios - Fix it Now ?
This article covers how to fix the WMI error for our customers.
Sometimes the standard permission levels defined in the Monitoring Windows Using WMI documentation do not expose all the monitoring capabilities of the WMI plugin.
In these cases you can elevate permissions by adding the WMI user to one of the two local groups:
- Performance Monitor Users
- Administrators
Need at least 2 WMI samples% - Fix it Now ?
This article covers how to tackle the error, Need at least 2 WMI samples%. The reason for the message is that the WMI user account does not have sufficient permissions. This can be resolved by adding the user account to the Performance Log Users security group on the windows computer.
- This can be performed by opening the Computer Management console (located in Administrative tools).
- Expand System Tools > Local Users and Groups > Groups.
- Edit the Performance Log Users security group and add the user account (wmiagent) to this group.
Restrict su access to Privileged Accounts in Linux - Steps to do it ?
This article covers how to restrict the su access in Linux.
Important things to note:
- Create a Linux group call sysadmins.
- Configure PAM to permit users from a group permission to use su.
- Switching as any other user with su will fail.
WMI ERROR: Retrieve result data - Fix it Now ?
This article covers process to fix WMI ERROR for our Customers. Due to a memory leak in the WMI functions in Windows 2008 and Windows 7, the system resources may be exhausted in the Windows system, resulting in the error message found above.
It has been seen that systeminfo and wmic commands executed via the command prompt fails in case this issue is present, displaying error messages such as:
The paging file is too small for this operation to complete.
Looking at the process list in the Windows system, it can be determined that the WmiPrvSE.exe process has allocated unusually large amounts of memory.
Workgroup Failover Cluster without Active Directory in Windows
This article covers how to go about Workgroup Failover Cluster. While Availability Group was a viable replacement for Database Mirroring, there were a couple of blocking issues that prevented customers from upgrading. In older Windows Server versions prior to Windows Server 2016, you could create a failover cluster only between the servers in the same Active Directory domain. The new version allows to create two- (or more) nodes failover cluster between servers joined to different domains, and even between workgroup servers (not AD domain joined) – a so-called Workgroup Cluster.
Service Not Listed in WMI Wizard in Nagios - Fix it Now ?
This article covers methods to tackle Service Not Listed in WMI Wizard in Nagios. Basically, Service may not get listed in WMI Wizard in Nagios due to reasons like lower value of Truncate Output Length or insufficient permission of the user account. Windows Management Instrumentation (WMI) is a part of Windows operating systems and can provide management data and operational information about those system. WMI can be used to automate administrative tasks on remote Windows-based computers. Nagios Core and Nagios XI are capable of monitoring Windows machines via WMI. .
To Check the permissions of the files, use this command:
ls -ls /tmp/*.state
Here you can see that the root user/group is the owner of the file:
-rw-r--r-- 1 root root 91 Apr 24 16:10 /tmp/cwpss_checkcpu__1025143___.state
The simplest option is to delete the files with this command:
rm -rf /tmp/*.state
