OMS Log Analytics Ubuntu 16.04 on-boarding undefined symbol: SSLv3_method

Hello All,

Just short post about issue during Ubuntu 16.04 on-boarding to OMS (Log Analytics).

First of all check this Microsoft/OMS-Agent-for-Linux – on this page you can find list of supported versions of Linux Operating Systems and links to many useful resources regarding OMS Agent on Linux.

Second if you try to on-board your Azure Ubuntu 16.04 VM to OMS right out-of-the-box – everything with work fine.

Third…here comes an error

But assume that you have installed PHP 5.6 from added repository as described here: this involves adding repository which contains OpenSSL build without SSLv3 support.

This will lead to following error during install of OMS Linux Agent

Configuring OMI service …
Created symlink from /etc/systemd/system/multi-user.target.wants/omid.service to /lib/systemd/system/omid.service.
Setting up scx (1.6.3.48) …
Setting up omsagent (1.2.0.148) …
-e info Reading onboarding params from: /etc/omsagent-onboard.conf
-e info Reusing previous agent GUID
/opt/microsoft/omsagent/ruby/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require’: /opt/microsoft/omsagent/ruby/lib/ruby/2.2.0/x86_64-linux/openssl.so: undefined symbol: SSLv3_method – /opt/microsoft/omsagent/ruby/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)
from /opt/microsoft/omsagent/ruby/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require’
from /opt/microsoft/omsagent/ruby/lib/ruby/2.2.0/openssl.rb:17:in `<top (required)>’
from /opt/microsoft/omsagent/ruby/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require’
from /opt/microsoft/omsagent/ruby/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require’
from /opt/microsoft/omsagent/bin/auth_key.rb:2:in `<main>’

OR it will lead to failure IF you upgrade OpenSSL package with

apt-get update

apt-get upgrade

And here is how we could solve issue:

  • if you have OMS Agent installed and upgraded OpenSSL to one from repository – > Agent fail to start

Downgrade to previous version of OpenSSL:

#Check installed and previous version

apt-cache policy openssl
openssl:
Installed: 1.0.2j-1+deb.sury.org~xenial+1
Candidate: 1.0.2j-1+deb.sury.org~xenial+1
Version table:
*** 1.0.2j-1+deb.sury.org~xenial+1 500
500 http://ppa.launchpad.net/ondrej/php/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
1.0.2g-1ubuntu4.5 500
500 http://azure.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
1.0.2g-1ubuntu4 500
500 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

#Install OpenSSL from Ubuntu repository

apt-get install openssl=1.0.2g-1ubuntu4.5

#Restart Agent and check status

scxadmin -restart

scxadmin -status

omiserver: is running
omiagent: 1 instance running

  • IF you want to on-board but and received error after running install script:

#Uninstall OMS Agent:

sudo dpkg -P omsconfig
sudo dpkg -P omsagent
sudo /opt/microsoft/scx/bin/uninstall


#Install OpenSSL from Ubuntu repository

apt-get install openssl=1.0.2g-1ubuntu4.5

#Install OMS Agent again:

sudo sh ./omsagent-<DOWNLOADED_SCRIPT_VERSION>.sh --install -w <workspaceid> -s <shared key>

Happy Monitoring!

THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru AG IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.

OMS (Log Analytics) and Red Hat/CentOS integration issue

If you are trying to use Operations Manager Suite to monitor your Red Hat or CentOS VMs you will probably face following issue if you use “Connect” button on Log Analytics section in Azure:

5

There are two ways (tested on CentOS but it same behavior on Red Hat) to make it work:

 

First way:

  1. Disable Diagnostics for VM during creation

1

  1. Use connect button on portal.azure.com

2

  1. And after some time

3

And data will appear in OMS Logs.

Pros: That Workspace Connected on Azure Portal

Cons: Disabled Azure Diag (you’ll monitor VM with OMS  – so no need)

 

Second way:

 

  1. Deploy VM with Azure Diag Enabled:

4

  1. In order to enable OMS you’ll have to install agent Manually:

If previously you tried to use Connect VM button on Azure Portal and it was Fail: You have to use Disconnect button and wait until operation finished (VM have to be turned on.)

In Putty on VM

$> wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/v1.1.0-28/omsagent-1.1.0-28.universal.x64.sh

$> sha256sum ./omsagent-1.1.0-28.universal.x64.sh

$> sudo sh ./omsagent-1.1.0-28.universal.x64.sh –upgrade -w <YOUR OMS WORKSPACE ID> -s <YOUR OMS WORKSPACE PRIMARY KEY>

  1. At the End on azure portal in will be listed as Not Connected but monitoring and data in OMS should appear.

3

Pros But at the end you’ll both OMS data and Azure Diag.

Cons Not Connected in Azure Portal

 

Both ways should bring OMS Linux

If you deployed VM with Azure Diag Enabled and decided to disable it and use Connect Button in Log Analytics Section of Portal – it will NOT Fail if

5

You have to remove extension totally by running following commands:

> sudo rpm -e omsconfig
> sudo rpm -e omsagent
> sudo /opt/microsoft/scx/bin/uninstall

 

After that you Can use “Connect” feature)

Happy Monitoring 🙂

THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru AG IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.