ICMP ping issue by Windows base End Point Operations Agent

As you know vRealize Operation Manager can monitor remote devices by ICMP check. It is a simple checking method, we use it to monitor at basic level, our remote routers or switches.

Implementation process:

  1. Go Environment / All Objects / EP OPS Adapter / Remote Cheks Word
  2. From Actions menu select “Monitor this object remotely”
    • Add Display nama E.g.: WAN-1
    • Monitored from select your Agent
    • Under Check Method select ICMP check
    • Hostname: IP address of device
  3. Under Advanced settings you can change “sotimeout” and “Collection Interval” (we use one minute)
  4. Click OK

Under Environment / All Objects / EP OPS Adapter / ICMP Check tree you will find all your ICMP checked objects, and you can select one of them for details or All Metrics data.

Now, you are able to create an Alert, base on resource availability state. Yes, but we received lots of alert from vROps, becouse the resources wasn’t available many times. We tried rise up sotimeout. Not worked.

We changed Agent log level to Debug and we saw many of this messages.

26-09-2017 20:23:36,043 CEST DEBUG [pool-1-thread-11] [Collector] name=ICMP Check, thread=pool-1-thread-11, result=Tue Sep 26 20:23:36 CEST 2017 (/192.168.xxx.xxx) null values={Availability=0.0, ResponseTime=19969.0}

(In my next Article I will show you how you can change EP OPS Agent’s log level and file size.)


We opened a new case at GSS (VMware Global Service Support) about this problem, but fortunetly in the maintime (under weeks – waited for GSS) we find a Release Note for vRealize Operation Manager 6.2. The subscription in this note looks like very similar as our problem ūüôā

No data returned when running ICMP check
When attempting to run an ICMP check for remote monitoring from an Agent running on a Windows platform, no data is returned.
Workaround: Do not use ICMP checking from an agent that is deployed on a Windows platform.

Link: http://pubs.vmware.com/Release_Notes/en/vrops/62/vrops-62-release-notes.html

We changed the Agent from Windows base OS to Linux OS, and in the last weeks we didn’t revecive fals alerts. I’m really sad becouse we use vRealize Operation 6.6.1 and the problem, wich was discovered in 6.2,¬† is still exists in the latest release.

Disable directory browsing Apache2 Debian8

Change Apache config file. Defult config is here: “/etc/apache2/sites-available/000-default.conf”

You can see similar this, without text in red box:


Add this text below to the config file:

<Directory “/var/www/html”>
Options Includes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
Allow from all

Safe file

Restart Apache service

“sudo service apache2 restart”


You can test when create folders in root directory (in this eximple: /var/www/html) and try browsing this directory any web browser.


You can see like this error message when you did everything well.

I hope this short article will help for You!

Set Up Apache Virtual Host on Ubuntu 14.04 LTS

We have to install apache2 for own server

# sudo apt-get update
# sudo apt-get install apache2

Create new folder for site

# sudo mkdir -p /var/www/example.com/public_html

If you would like change permission you do that

# sudo chown -R $USER:$USER /var/www/example.com/public_html

 Add read access www folder

# sudo chmod -R 755 /var/www

Create a page

# sudo nano /var/www/example.com/public_html/index.html

Insert this text into index.html file:

<title>Welcome to
<h1>Success! The
example.com virtual host is working!</h1>

You need create a Virtual Host file (in older version 000-default.conf was simple default file, but in the new version we have to use the new, and *.conf extension)

# sudo cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/example.com.conf

Edit config file

# sudo nano /etc/apache2/sites-available/example.com.conf

In the simple config file we can see like this


Apache2 default config file

Add new lines to config file, and if you want, delete comments.
“ServerName” is usually your domain name like in IIS hostheader
“ServerAlies” this is a alternative name, this help matching for example www a record
“DocumentRoot” is a place where you going to store your website (in this example index.html)

<VirtualHost *:80>

ServerAdmin admin@example.com
ServerName example.com
ServerAlias http://www.example.com
DocumentRoot /var/www/example.com/public_html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined


We have to enable site

# sudo a2ensite example.com.conf

Restart service

# sudo service apache2 restart

After restart you will see something like this

* Restarting web server apache2
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using Set the ‘ServerName’ directive globally to suppress this message

Don’t worry, this is OK.

I checked my site on server

Edit host file, add you server’s ip address into host file

# sudo nano /etc/hosts

YOURIP example.com

Check: ping example.com, and if you getting answer, your host file settings are ready

# w3m example.com (w3m is a command line browser, i checked my site by this tool)

press “q” to quit from w3m browser

HTTPs check in Nagios error Invalid option – SSL is not available

When you want¬†check https site with “./check_http –ssl google.com” command in Nagios, you may get this error “Invalid option – SSL is not available”

You will able to solve this problem, when you follow this instructions below:

# sudo apt-get install libssl-dev

(navigate to the directory that you have your nagios plugins extracted, Eximple: /home/install-username/nagios-plugins-2.0.3/)

# sudo ./configure –with-openssl=/usr/bin/openssl
# sudo make
# sudo make install
# sudo service nagios restart

Check plugin: go nagios libex folder (maybe there: cd /usr/local/nagios/libexec$)

#¬†sudo ./check_http –ssl google.com
# HTTP OK: HTTP/1.0 302 Found Р524 bytes in 0.132 second response time |time=0.132414s;;;0.000000 size=524B;;;0

Add new Read Only User to Nagios Core

!!! Don’t forget¬†make Snapshot or Backup from Your system !!!

I have used Ubuntu 14.04 and Nagios Core 4.0.8, and this steps worked, I tried!

# sudo htpasswd /usr/local/nagios/etc/htpasswd.users newusername
# /etc/init.d/apache2 reload

edit nagios cgi.cfg file, which located maybe here

# sudo nano /usr/local/nagios/etc/cgi.cfg

you will found this part in the cgi.cfg, and add next to it with comma


You have to restart nagios

# sudo service nagios reload

after reload you can able to login into nagios web page by newuser, and you have read only rights.