none
SCOM 2012 Linux Monitoring - RPCBIND, RPCIDMAP, RPCSTAT services not running

    Question

  • We are running SCOM 2012 SP1 and added a test Linux server running Red Hat Enterprise 6.3.  SCOM is reporting that the server is in Critical health because the following three services are not running.

    1) Process Rpcbind Service Health - Rpcbind Mapper Not Running
    2) Process Rpcidmap Service Health - NFSv4 ID Name Mapper Not Running
    3) Process Rpcstat Service Health - NSM Status Monitor Not Running

    My question is that are these services required to be running in order for SCOM to monitor the Linux servers properly?  If yes, can you please give brief explaination as to why so I can explain that to our Linux Administrator.  The Linux Administrator is saying that we do not run these services on any of the Linux servers because they are not needed.  If infact these services are not needed, how can I have SCOM ignore the critical error messages?  Thanks

    Thursday, February 21, 2013 4:14 PM

Answers

  • Not needed. Just out of the box we monitor them as they are generally running on a default install of RHEL 6. To disable them just right-click on them in the Health Explorer and select 'Monitor Properties'. From there select the 'Overrides' tab and hit the 'Disable' button. You can disable it for just that specific system or all systems of type RHEL 6.

    Regards,

    -Steve

    • Marked as answer by SCTechNet22 Thursday, February 21, 2013 8:05 PM
    Thursday, February 21, 2013 5:56 PM

All replies

  • Not needed. Just out of the box we monitor them as they are generally running on a default install of RHEL 6. To disable them just right-click on them in the Health Explorer and select 'Monitor Properties'. From there select the 'Overrides' tab and hit the 'Disable' button. You can disable it for just that specific system or all systems of type RHEL 6.

    Regards,

    -Steve

    • Marked as answer by SCTechNet22 Thursday, February 21, 2013 8:05 PM
    Thursday, February 21, 2013 5:56 PM
  • Steve,

    Thank you for the information.  That helped a lot.  I was able to disable the monitors.

    Shahid

    Thursday, February 21, 2013 8:05 PM
  • Not needed. Just out of the box we monitor them as they are generally running on a default install of RHEL 6. To disable them just right-click on them in the Health Explorer and select 'Monitor Properties'. From there select the 'Overrides' tab and hit the 'Disable' button. You can disable it for just that specific system or all systems of type RHEL 6.

    Regards,

    -Steve


    Generally running? Shouldn't there be a little more intelligence in the discovery then, if NFS is running then let's enable these monitors? I'm personally OK with just disabling since I know we're not using NFS for most things, but if someone was just getting started and had several Linux servers start reporting this I could see where that could lead to panic and general hand flapping ;-)

    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Monday, September 08, 2014 3:28 PM
  • Yup, generally running. I'm assuming you've done a basic install of RHEL 6. All processes listed above are enabled by default on a RHEL 6 install if you take the default settings. If someone is just getting started you can pretty much guarantee they will do a basic install of RHEL 6 and this will not be an issue.

    Could it be done better... sure but at what point do you stop? We could discover all services running on the system and start monitoring them out of the box but what are important and what are not to each customer? The idea is to give you some basic monitoring on a default install based on what each OS provider starts on a "default" install. If this does not suite your needs SCOM is very configurable and adding a custom service monitor is very easy to configure along with disabling existing ones.

    If you'd like to provide feedback on this feel free to open a support ticket with Microsoft and file what we call a 'Design Change Request' [DCR]. We go though these prior to starting each update to SCOM. No guarantee it will get fixed/changed as we do have priorities but we are listening.

    Regards,

    -Steve

    Tuesday, September 09, 2014 2:23 PM
  • Steve, I actually did do a basic install of rhel 6.5 and was getting the errors listed in the OP. Doing the recommended check to see if the service was in fact running I saw that it was. I closed the error and within a few minutes it popped again and my next assumption was that while the mapper was running nfs wasn't installed/configured which was the culprit, an override cleared that up.

    I don't have strong feelings on this, but if the Microsoft assumption is that some service is "generally running" I would think it should be checked up front to verify before we start throwing errors.

    that's all i'm saying


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Tuesday, September 09, 2014 2:32 PM
  • Jeffrey,

    We do appreciate the feedback and the monitors are based off a 6.0 install so things could have changed with 6.5 and it is something we should look into. I'll give this a shot myself and pass it along to my program manager if needed.

    Thanks,

    -Steve

    Tuesday, September 09, 2014 2:40 PM
  • Cool, thanks!

    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    Tuesday, September 09, 2014 4:32 PM