search

betrotle / scom-rhel8

Management packs for SCOM to support RHEL 8
1 stars 0 forks source link

Discovering rh8 servers in scom 1801 #1

Open lv986 opened 4 years ago

lv986 commented 4 years ago

Hi, Thanks for making this MP. I've installed it on my scom 1801 environment, but still can not discover linux rh8 servers. Is there something I need to do? I'm using a ssh key for discovering other linux machines. Regards, Luc

betrotle commented 4 years ago

Where does it error out Luc? Does it fail to discover? Or fail to install the agent and manage the instance? I have only tested against SCOM 2016 sorry.

On Thu, Apr 23, 2020 at 3:53 PM lv986 notifications@github.com wrote:

Hi, Thanks for making this MP. I've installed it on my scom 1801 environment, but still can not discover linux rh8 servers. Is there something I need to do? I'm using a ssh key for discovering other linux machines. Regards, Luc

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM55Q7HMQGZBS7OT7VIPLILRN7XY3ANCNFSM4MO2Q5CA .

lv986 commented 4 years ago

Hi,

Fail to discover, got the error unreachable

Regards,

Luc

Van: betrotle notifications@github.com Verzonden: donderdag 23 april 2020 10:43 Aan: betrotle/scom-rhel8 scom-rhel8@noreply.github.com CC: lv986 luc@lvdbprojects.be; Author author@noreply.github.com Onderwerp: Re: [betrotle/scom-rhel8] Discovering rh8 servers in scom 1801 (#1)

Where does it error out Luc? Does it fail to discover? Or fail to install the agent and manage the instance? I have only tested against SCOM 2016 sorry.

On Thu, Apr 23, 2020 at 3:53 PM lv986 <notifications@github.com mailto:notifications@github.com > wrote:

Hi, Thanks for making this MP. I've installed it on my scom 1801 environment, but still can not discover linux rh8 servers. Is there something I need to do? I'm using a ssh key for discovering other linux machines. Regards, Luc

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM55Q7HMQGZBS7OT7VIPLILRN7XY3ANCNFSM4MO2Q5CA .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-618266545 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5J67RZUNLIKRWO2JGHLDTRN75Q7ANCNFSM4MO2Q5CA . https://github.com/notifications/beacon/AM5J67T2YYD3CFV6QYRSPXDRN75Q7A5CNFSM4MO2Q5CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOETM77MI.gif

betrotle commented 4 years ago

That’s not a management pack issue, it’s a connection issue. Is there a firewall running on your Linux host, or in between the scom management server and the Linux host? Does it allow icmp ping, tcp port 22 (ssh) and tcp port 1270?

Sent from my iPhone

On 23 Apr 2020, at 4:51 pm, lv986 notifications@github.com wrote:

 Hi,

Fail to discover, got the error unreachable

Regards,

Luc

Van: betrotle notifications@github.com Verzonden: donderdag 23 april 2020 10:43 Aan: betrotle/scom-rhel8 scom-rhel8@noreply.github.com CC: lv986 luc@lvdbprojects.be; Author author@noreply.github.com Onderwerp: Re: [betrotle/scom-rhel8] Discovering rh8 servers in scom 1801 (#1)

Where does it error out Luc? Does it fail to discover? Or fail to install the agent and manage the instance? I have only tested against SCOM 2016 sorry.

On Thu, Apr 23, 2020 at 3:53 PM lv986 <notifications@github.com mailto:notifications@github.com > wrote:

Hi, Thanks for making this MP. I've installed it on my scom 1801 environment, but still can not discover linux rh8 servers. Is there something I need to do? I'm using a ssh key for discovering other linux machines. Regards, Luc

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM55Q7HMQGZBS7OT7VIPLILRN7XY3ANCNFSM4MO2Q5CA .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-618266545 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5J67RZUNLIKRWO2JGHLDTRN75Q7ANCNFSM4MO2Q5CA . https://github.com/notifications/beacon/AM5J67T2YYD3CFV6QYRSPXDRN75Q7A5CNFSM4MO2Q5CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOETM77MI.gif

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

betrotle commented 4 years ago

I've updated the README.md with more precise prerequisites.

lv986 commented 4 years ago

Hi,

Thanks for your anwer.

The problem is now solved by the linux team. There was a problem with the firewall.

We had another problem after that by deploying the agent, because the agent scx-1.6.4-007.rhel.8.x64.sh was not in the C:\Program Files\Microsoft System Center\Operations Manager\Server\AgentManagement\UnixAgents\DownloadedKits directory after installing your bundle. This problem is now solved by manualy copying the file.

Now we have agents deployed onto 2 RH8 server. Everything is discovered but stays grayed out.

What can be the problem of this you think?

Regards,

Luc

betrotle schreef op 23/04/2020 16:26:

That's not a management pack issue, it's a connection issue. Is there a firewall running on your Linux host, or in between the scom management server and the Linux host? Does it allow icmp ping, tcp port 22 (ssh) and tcp port 1270?

Sent from my iPhone

On 23 Apr 2020, at 4:51 pm, lv986 notifications@github.com wrote:

Hi,

Fail to discover, got the error unreachable

Regards,

Luc

Van: betrotle notifications@github.com Verzonden: donderdag 23 april 2020 10:43 Aan: betrotle/scom-rhel8 scom-rhel8@noreply.github.com CC: lv986 luc@lvdbprojects.be; Author author@noreply.github.com Onderwerp: Re: [betrotle/scom-rhel8] Discovering rh8 servers in scom 1801 (#1)

Where does it error out Luc? Does it fail to discover? Or fail to install the agent and manage the instance? I have only tested against SCOM 2016 sorry.

On Thu, Apr 23, 2020 at 3:53 PM lv986 <notifications@github.com mailto:notifications@github.com > wrote:

Hi, Thanks for making this MP. I've installed it on my scom 1801 environment, but still can not discover linux rh8 servers. Is there something I need to do? I'm using a ssh key for discovering other linux machines. Regards, Luc

-- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM55Q7HMQGZBS7OT7VIPLILRN7XY3ANCNFSM4MO2Q5CA .

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-618266545 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5J67RZUNLIKRWO2JGHLDTRN75Q7ANCNFSM4MO2Q5CA . https://github.com/notifications/beacon/AM5J67T2YYD3CFV6QYRSPXDRN75Q7A5CNFSM4MO2Q5CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOETM77MI.gif

-- You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-618425392 [2] https://github.com/notifications/unsubscribe-auth/AM5J67UVTD7J7P4CY6JN7JLROBFXRANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc,

Did you deploy using the bundle (.mpb) or the xml? The bundle definitely includes scx-1.6.4-007.rhel.8.x64.sh, the xml will not.

Do you have other Linux servers attached to this SCOM instance that are working? Can you please:

  1. Check all prerequisites listed in the README.md

a) Firewall ports (https://docs.microsoft.com/en-us/system-center/scom/plan-security-config-firewall?view=sc-om-2016), namely ICMP ping, TCP port 22 (SSH) and TCP port 1270 from all servers in the UNIX/Linux Management Server Resource Pool to the target UNIX/Linux servers.

b) Configuration of SCOM UNIX/Linux accounts (https://kevinholman.com/2016/11/11/monitoring-unix-linux-with-opsmgr-2016/)

c) Local UNIX/Linux monitoring account creation including sudo configuration (https://social.technet.microsoft.com/wiki/contents/articles/7375.scom-configuring-sudo-elevation-for-unix-and-linux-monitoring.aspx#D)

  1. Have the Linux team search for failed sudo commands from your scom user in /var/log/secure and remediate. Regards, Betrotle
lv986 commented 4 years ago

Hi,

I did the deployment via the bundle (.mbp), but the scx-1.6.4-007.rhel.8.x64.sh was not there on the right directory. Maybe is this a problem with scom 1801. But now this is solved by manualy copying the file.

We have a lot of redhat6 and redhat7 servers attached in our scom environment, without problems.

All the prerequisites are OK.

This is what we get in scom:

This is the answer from our linux team for a ntp check monitor that we have on all our linux machines:

APR 26 03:49:56 PVX2ALF01N3 SUDO[21117]: SCOM : TTY=UNKNOWN ; PWD=/VAR/OPT/MICROSOFT/SCX/TMP ; USER=ROOT ; COMMAND=/BIN/SH -C /OPT/SYSADM/SCRIPTS/CHECK_NTP.SH

APR 26 03:49:56 PVX2ALF01N3 SUDO[21117]: PAM_UNIX(SUDO:SESSION): SESSION OPENED FOR USER ROOT BY (UID=0)

APR 26 03:49:56 PVX2ALF01N3 SUDO[21117]: PAM_UNIX(SUDO:SESSION): SESSION CLOSED FOR USER ROOT

APR 26 03:50:08 PVX2ALF01N3 OMISERVER[24021]: PAM_UNIX(OMI:SESSION): SESSION CLOSED FOR USER SCOM

Do you have any suggestions?

Kind regards,

Luc

betrotle schreef op 25/04/2020 01:02:

Hi Luc,

Did you deploy using the bundle (.mpb) or the xml? The bundle definitely includes scx-1.6.4-007.rhel.8.x64.sh, the xml will not.

Do you have other Linux servers attached to this SCOM instance that are working? Can you please:

  • Check all prerequisites listed in the README.md

a) Firewall ports (https://docs.microsoft.com/en-us/system-center/scom/plan-security-config-firewall?view=sc-om-2016), namely ICMP ping, TCP port 22 (SSH) and TCP port 1270 from all servers in the UNIX/Linux Management Server Resource Pool to the target UNIX/Linux servers.

b) Configuration of SCOM UNIX/Linux accounts (https://kevinholman.com/2016/11/11/monitoring-unix-linux-with-opsmgr-2016/)

c) Local UNIX/Linux monitoring account creation including sudo configuration (https://social.technet.microsoft.com/wiki/contents/articles/7375.scom-configuring-sudo-elevation-for-unix-and-linux-monitoring.aspx#D)

  • Have the Linux team search for failed sudo commands from your scom user in /var/log/secure and remediate. Regards, Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-619273417 [2] https://github.com/notifications/unsubscribe-auth/AM5J67QGWWFQC3HSSDIQND3ROILBDANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, It looks like the SCOM Management server can access and communicate with the server fine, it's running your custom checks. If you inspect the health explorer view can you figure out what check isn't working? Possibly the heartbeat test? Betrotle

betrotle commented 4 years ago

Are the standard tests set to disabled and you need to override to enable? Or visa-versa (the checks overrided to disabled and you need to remove the override)?

lv986 commented 4 years ago

Hi,

I don't see any overrides. It's very strange because we have state changes in green but the monitors stays grayed out, as you can see in the screenshot:

And we only have this with the redhat 8 servers.

Do you have any idea?

Thanks,

Kind regards,

Luc

betrotle schreef op 29/04/2020 01:50:

Are the standard tests set to disabled and you need to override to enable? Or visa-versa (the checks overrided to disabled and you need to remove the override)?

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-620912892 [2] https://github.com/notifications/unsubscribe-auth/AM5J67SJ6KAKVV3YKZKINUTRO5TV3ANCNFSM4MO2Q5CA

lv986 commented 4 years ago

Hi,

I don’t know if you can see the screenshot that I’ve sended to you in the previous email in github?

Kind regards,

Luc

Van: betrotle notifications@github.com Verzonden: woensdag 29 april 2020 01:51 Aan: betrotle/scom-rhel8 scom-rhel8@noreply.github.com CC: lv986 luc@lvdbprojects.be; Author author@noreply.github.com Onderwerp: Re: [betrotle/scom-rhel8] Discovering rh8 servers in scom 1801 (#1)

Are the standard tests set to disabled and you need to override to enable? Or visa-versa (the checks overrided to disabled and you need to remove the override)?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-620912892 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5J67SJ6KAKVV3YKZKINUTRO5TV3ANCNFSM4MO2Q5CA . https://github.com/notifications/beacon/AM5J67VUJQC6SJARFYYGXV3RO5TV3A5CNFSM4MO2Q5CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEUBGB7A.gif

lv986 commented 4 years ago

Hi,

I did some testing yesterday around this strange problem.

Cannot find resource with ID Universal.Linux.RHEL.8.Kit.x64

Maybe this is the problem with the greyed out status?

Kind regards,

Luc

betrotle schreef op 29/04/2020 01:50:

Are the standard tests set to disabled and you need to override to enable? Or visa-versa (the checks overrided to disabled and you need to remove the override)?

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-620912892 [2] https://github.com/notifications/unsubscribe-auth/AM5J67SJ6KAKVV3YKZKINUTRO5TV3ANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, The issue with that is that the resource Universal.Linux.RHEL.8.Kit.x64 defined in the XML is:

The bundle contains scx-1.6.4-007.rhel.8.x64.sh but the .xml does not. I don't think this is cause of your original issue. Betrotle

betrotle commented 4 years ago

The xml did not render in my last post... <DeployableResource ID="Universal.Linux.RHEL.8.Kit.x64" Accessibility="Internal" FileName="scx-1.6.4-007.rhel.8.x64.sh" HasNullStream="false" />

lv986 commented 4 years ago

Hi,

Thanks for your answer.

Do you received my screenshot with the green state changes and the grayed out monitors?

Do you have any idea what this strange effect can be? Difference between scom2016 and 1801?

I’ve tested everything the last days, yesterday I cleared all caches from the scom servers without success.

Kind regards,

Luc

Van: betrotle notifications@github.com Verzonden: donderdag 30 april 2020 07:18 Aan: betrotle/scom-rhel8 scom-rhel8@noreply.github.com CC: lv986 luc@lvdbprojects.be; Author author@noreply.github.com Onderwerp: Re: [betrotle/scom-rhel8] Discovering rh8 servers in scom 1801 (#1)

The xml did not render in my last post...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-621617972 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5J67UHHI5CQN3JJXGYV4TRPECYJANCNFSM4MO2Q5CA . https://github.com/notifications/beacon/AM5J67VRQN34LXUSSKJQCZ3RPECYJA5CNFSM4MO2Q5CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEUGSGNA.gif

betrotle commented 4 years ago

Hi Luc, No I haven't got access to any screenshots sorry, but I can guess at what you mean. In the coming days I can attempt to create a management pack for SCOM 1801 but haven't any SCOM 1801 instances to test on, so I would need to release without testing. Betrotle

lv986 commented 4 years ago

Hi,

That’s great news. I can test it for you.

Can you give me an email adres, than I can send you the screenshots?

Regards,

Luc

Van: betrotle notifications@github.com Verzonden: donderdag 30 april 2020 11:35 Aan: betrotle/scom-rhel8 scom-rhel8@noreply.github.com CC: lv986 luc@lvdbprojects.be; Author author@noreply.github.com Onderwerp: Re: [betrotle/scom-rhel8] Discovering rh8 servers in scom 1801 (#1)

Hi Luc, No I haven't got access to any screenshots sorry, but I can guess at what you mean. In the coming days I can attempt to create a management pack for SCOM 1801 but haven't any SCOM 1801 instances to test on, so I would need to release without testing. Betrotle

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-621724120 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5J67WP6XO2XZJWKKRBNZTRPFA4JANCNFSM4MO2Q5CA . https://github.com/notifications/beacon/AM5J67TZRUHRAH2ZPVOPOZDRPFA4JA5CNFSM4MO2Q5CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEUHMDWA.gif

betrotle commented 4 years ago

Hi Luc, Diving into this, it's clear why it's not working. SCOM 2016 uses omi and scx deployed on monitored hosts. SCOM 1801 is using the omsagent instead. Can you send me the sudo rules implemented on RHEL 8 for your local SCOM user? Betrotle

lv986 commented 4 years ago

Hi,

Thanks for investing you time in this.

This is information about sudo that I received from the linux team:

[SCOM@PVX2ALF01N3 ~]$ SUDO -L

MATCHING DEFAULTS ENTRIES FOR SCOM ON PVX2ALF01N3: 

!VISIBLEPW, ALWAYS_SET_HOME, MATCH_GROUP_BY_GID,

ALWAYS_QUERY_GROUP_PLUGIN, ENV_RESET, ENV_KEEP="COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS", ENV_KEEP+="MAIL PS1 PS2 QTDIR USERNAME LANG 

LC_ADDRESS LC_CTYPE", ENV_KEEP+="LC_COLLATE LC_IDENTIFICATION

LC_MEASUREMENT LC_MESSAGES", ENV_KEEP+="LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE", ENV_KEEP+="LC_TIME LC_ALL LANGUAGE LINGUAS 

_XKB_CHARSET XAUTHORITY",

SECURE_PATH=/SBIN\:/BIN\:/USR/SBIN\:/USR/BIN

USER SCOM MAY RUN THE FOLLOWING COMMANDS ON PVX2ALF01N3: 

(ALL) NOPASSWD: ALL

Is there something that I already can test for you?

Regards,

Luc

betrotle schreef op 06/05/2020 05:25:

Hi Luc, Diving into this, it's clear why it's not working. SCOM 2016 uses omi and scx deployed on monitored hosts. SCOM 1801 is using the omsagent instead. Can you send me the sudo rules implemented on RHEL 8 for your local SCOM user? Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-624422688 [2] https://github.com/notifications/unsubscribe-auth/AM5J67QJBU2N3KD2PPZBKGDRQDKD7ANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, I've generated the .mpb but it's too large for github to push it (it's ~140MB). Have you got an alternate way for me to get it to you? Betrotle

lv986 commented 4 years ago

Hi,

Maybe you can send it with wetransfert?

My email address is luc@lvdbprojects.be.

Regards,

Luc

betrotle schreef op 06/05/2020 08:21:

Hi Luc, I've generated the .mpb but it's too large for github to push it (it's ~140MB). Have you got an alternate way for me to get it to you? Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-624463394 [2] https://github.com/notifications/unsubscribe-auth/AM5J67V3H46ZDVPERJIBM5DRQD6WXANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Transferring now.

Please:

lv986 commented 4 years ago

Hi,

Received your bundle, but after installing the agent is not installed in the right directory on my scom servers, as I also had before.

Can you send me the agent files, so I can manually put them in the directory?

Kind regards,

Luc

Van: betrotle notifications@github.com Verzonden: woensdag 6 mei 2020 08:59 Aan: betrotle/scom-rhel8 scom-rhel8@noreply.github.com CC: lv986 luc@lvdbprojects.be; Author author@noreply.github.com Onderwerp: Re: [betrotle/scom-rhel8] Discovering rh8 servers in scom 1801 (#1)

Transferring now.

Please:

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-624476433 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5J67VZLBHNKLDBVE3LSVLRQEDBPANCNFSM4MO2Q5CA . https://github.com/notifications/beacon/AM5J67XIHEUU2XSMPZNLZXTRQEDBPA5CNFSM4MO2Q5CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEU4MCEI.gif

betrotle commented 4 years ago

Hi Luc, It's just the agent from Microsoft: https://github.com/microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent_v1.12.15-0/omsagent-1.12.15-0.universal.x64.sh Betrotle

lv986 commented 4 years ago

Hi,

I did a test to install an agent on a linux 8 machine and this is the error that I received:

Task invocation failed with error code -2130771918. Error message was: The SCXCertWriteAction module encountered a DoProcess exception. The workflow "Universal.Linux.RHEL.8.Agent.Install.Task" has been unloaded.

Module: SCXCertWriteAction

Location: DoProcess

Exception type: ScxCertLibException

Exception message: Unable to create certificate context ; {ASN1 bad tag value met. }

Additional data: Sudo path: /usr/bin/

Management group: PV_SCOM_PRD

Workflow name: Universal.Linux.RHEL.8.Agent.Install.Task

Object name: Linux Servers

Object ID: {C15E6A49-86F9-BB95-E8CE-1F2BF080D604}

Can you take a look?

Regards,

Luc

betrotle schreef op 06/05/2020 13:50:

Hi Luc, It's just the agent from Microsoft: https://github.com/microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent_v1.12.15-0/omsagent-1.12.15-0.universal.x64.sh Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-624603767 [2] https://github.com/notifications/unsubscribe-auth/AM5J67T2VDZNMYDZT3U6Q6TRQFFJTANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, Can you try install the agent manually and see what the result is? Copy the installer to a RHEL 8 server, make it executable then run it with --install --enable-opsmgr Betrotle

lv986 commented 4 years ago

Hi,

Do you mean these 2 files?

scx-1.6.4-007.rhel.8.x64

omsagent-1.12.15-0.universal.x64.sh

In which order do I execute these?

Regards,

Luc

betrotle schreef op 07/05/2020 01:16:

Hi Luc, Can you try install the agent manually and see what the result is? Copy the installer to a RHEL 8 server, make it executable then run it with --install --enable-opsmgr Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-624939029 [2] https://github.com/notifications/unsubscribe-auth/AM5J67SIV3ZBC33SEPN732LRQHVUHANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, Just the SCOM 1801 agent (omsagent-1.12.15-0.universal.x64.sh). Betrotle

lv986 commented 4 years ago

Hi,

How was your weekend?

The linux team installed the agent manually and I was able to sign and manage the server from scom, so only pushing the agent is not working in your MP.

On the other side, I have a strange situation, also with a last added RH7 into scom, maybe nothing to do with you MP, but maybe you can help me with this:

My network adaptor and heartbeat provider are grayed out, everything else will be monitored, and also the server stays grayed out. I send you a screenshot to your email adres.

Do you know what the problem can be?

Regards,

Luc

betrotle schreef op 08/05/2020 04:50:

Hi Luc, Just the SCOM 1801 agent (omsagent-1.12.15-0.universal.x64.sh). Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-625600127 [2] https://github.com/notifications/unsubscribe-auth/AM5J67WCV7PEZGXBRNH4OHLRQNXOJANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, Had a good weekend thanks I have no ideas off top of my head sorry, however, if the issue is occurring with a supported operating system (RHEL 7) then you should be entitled to Microsoft support to help diagnose. Please do let me know what the issue was once resolved. Betrotle

lv986 commented 4 years ago

Hi,

I will investigate on this problem this week and let you know.

Do you know what the problem is with the pushing of you agent from scom?

As I understand in your previous email the omsagent... is replacing the scx... agent? Isn't it?

Regards,

Luc

betrotle schreef op 11/05/2020 06:47:

Hi Luc, Had a good weekend thanks I have no ideas off top of my head sorry, however, if the issue is occurring with a supported operating system (RHEL 7) then you should be entitled to Microsoft support to help diagnose. Please do let me know what the issue was once resolved. Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-626466843 [2] https://github.com/notifications/unsubscribe-auth/AM5J67UVZZVQRIHRW3LJYLTRQ57OLANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, At a guess, the agent deployment might not be running with the correct installation flags (--enable-opsmgr). To get around this I'd need to alter the omsagent script to enable this by default. I would have to have access to a SCOM 1801 instance to diagnose properly though. Correct, omsagent is the agent installer used by SCOM 1801. The scx script is SCOM 2016 only. Betrotle

lv986 commented 4 years ago

Hi,

When you have something that I can test for you with de problem of the push of the scom agent, let me know and I do it for you.

Regards,

Luc

betrotle schreef op 11/05/2020 07:15:

Hi Luc, At a guess, the agent deployment might not be running with the correct installation flags (--enable-opsmgr). To get around this I'd need to alter the omsagent script to enable this by default. I would have to have access to a SCOM 1801 instance to diagnose properly though. Correct, omsagent is the agent installer used by SCOM 1801. The scx script is SCOM 2016 only. Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-626474015 [2] https://github.com/notifications/unsubscribe-auth/AM5J67SAS4QSRBSGG35CZMDRQ6CVXANCNFSM4MO2Q5CA

lv986 commented 4 years ago

Hi,

Thanks for sending me the new scom agent.

I will do a test as soon as possible, but first I need to figure out what the problem is with the grayed out linux servers that we added last. It's a strange thing, everything will be monitored, but the status stays gray.

Do you have any idea where we can search for this problem?

Regards,

Luc

betrotle schreef op 11/05/2020 07:15:

Hi Luc, At a guess, the agent deployment might not be running with the correct installation flags (--enable-opsmgr). To get around this I'd need to alter the omsagent script to enable this by default. I would have to have access to a SCOM 1801 instance to diagnose properly though. Correct, omsagent is the agent installer used by SCOM 1801. The scx script is SCOM 2016 only. Betrotle

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/betrotle/scom-rhel8/issues/1#issuecomment-626474015 [2] https://github.com/notifications/unsubscribe-auth/AM5J67SAS4QSRBSGG35CZMDRQ6CVXANCNFSM4MO2Q5CA

betrotle commented 4 years ago

Hi Luc, Microsoft support should be able to assist, just log a case with them. Betrotle

pmostrom commented 4 years ago

Just imported the management pack and installed the agents (manually) on a couple of our RHEL8 test servers in our system test SCOM 2016 environment. So far everything looks good. Lots of interest in getting RHEL8 going in our environment, but without support for it in SCOM 2016 it is causing a lot of 'wailing and gnashing of teeth!'. SCOM 2019 is months away for us and we will still have several hundred RHEL 6 servers around for a year or more, so SCOM 2016 is still our best bet. Thanks so much for your time and hard work! Paul M.

betrotle commented 4 years ago

Thanks for the feedback Paul, glad to know it works and is helping.