none
Unix and Linux - Agent - The monitor has been initialized for the first time or it has exited maintenance mode RRS feed

  • Question

  • Hello,

    I see at the moment in my environment that my Unix and Linux Agent behave strange.

    We have migrated our SCOM 2012 R2 UR11 to SQL 2014. After we added 6 new Management Server with Windows Server 2012 R2 to SCOM 2012 R2 UR11.

    After 3 weeks time we extended yesterday the Unix and Linux resource pool with 3 additional Management Server for Unix and Linux.

    Today we have seen the "errors" and that they have been there before we added yesterday the 3 additional Management Server.

    I could find until now no explaination why the agents behave in such a way. We have around 400 X-Plat server. The Agent have received the latest updates 1.5.1-216 but we see the behavoir also on 1.5.1-184.

    Maybe you have seen such behavoir and know how to solve the situation

    Cheers,


    • Edited by Martin Elflein Wednesday, November 9, 2016 9:32 AM Additional explaination
    Wednesday, November 9, 2016 9:28 AM

All replies

  • Any solutions ? Just the same behavior, and i have no idea what to do..


    none


    • Edited by SComrrr Thursday, June 13, 2019 5:00 PM add pic
    Thursday, June 13, 2019 4:54 PM
  • hello,

    Have you checked run as account and profiles are distributed correctly for unix\linux monitoring?

    https://docs.microsoft.com/en-us/system-center/scom/manage-security-config-crossplat-runas-profile?view=sc-om-2019

    https://kevinholman.com/2016/11/11/monitoring-unix-linux-with-opsmgr-2016/

    Also, please check if you are getting output for below winrm query from all management servers in the SCX resource pool-

    winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Agent?__cimnamespace=root/scx -username:<UNIX/Linux user> -password:<UNIX/Linux password> -r:https://<UNIX/Linux server>:1270/wsman -auth:basic -encoding:utf-8

    Tuesday, July 2, 2019 4:40 PM
  • Yes its all ok with runas

    Looks like anyway to fix to use m$ support..


    none

    Monday, August 5, 2019 4:03 AM
  • Hi Guys,

    did you manage to solve this? Appreciate your feedback and thanks in advance!

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Wednesday, October 23, 2019 2:02 PM
    Moderator
  • No, problem still exists. 

    none

    Wednesday, October 23, 2019 3:29 PM
  • Hi,

    that is really odd. A couple of thoughts:

    - What are the details of the state change when the state changes to Error (I screenshot would be very nice, I see some details on the screenshot above, but not all)
    - How many agents are affected? All of them?
    - Which monitors are affected? Only the "Free Space" monitors or also other? Is the Free Space monitor showing the strange behaviour for the /data partition only?

    I need to get the bigger picture here, hence the questions. 

    What you will also have to do is to enable Logging as per:

    Logging and Debugging

    In this article there are two types of logs - Operations Manager Module Logging and Linux agent logging. Please enable both of those, wait (should nopt be long, judging by the frequence of occurance) untill the monitor flips states, stop those (important for verbose agent logging, since they are growing fast) and try to find more bout the behavior there. 

    Let me know if you need more details. I am realy curious what the reason could be and I will try to support you with more suggestions. 

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Thursday, October 24, 2019 4:18 PM
    Moderator