How to Check Call Home Activity

There are 2 known issues with sending Call Home notification.

  1. Call Home email wont be sent due to network limitation.
  2. When setting a static IP call home will not work (Relevant up to 2.1.X)


Problems:

Problem 1:

This problem usually occur when the "api.sendgrid.com" is not reachable from EMS.

Good Messages-

root@emanage ~# grep "Sent call home report" /elastifile/log/emanage/production.log
I, [2017-07-08T23:00:00.694249 #909]  INFO -- : Sent call home report
I, [2017-07-09T23:00:00.844501 #909]  INFO -- : Sent call home report


Bad Messages-

root@emanage ~# grep "Sent call home report" /elastifile/log/emanage/production.log
E, [2017-07-08T23:00:00.694249 #909]  ERROR -- : Error sending call home report
E, [2017-07-09T23:00:00.844501 #909]  ERROR -- : Error sending call home report


Problem 2:

This problem occurs when the user set a static IP in EMS setup.

The current code will set the resolve configuration file with wrong permissions which will fail the scheduler service when reading it.


/elastifile/log/epa/epa-server.log

2017-07-30 06:13:06,424 INFO 786:140348575700736 [infra.py:78]: Writing: /etc/.resolv.conf.bIzhOW
2017-07-30 06:13:06,424 INFO 786:140348575700736 [infra.py:93]: Rename: /etc/.resolv.conf.bIzhOW --> /etc/resolv.conf


/var/log/messages

Jul 16 17:00:00 emanage rake: { 69922002164140 rufus-scheduler intercepted an error:
Jul 16 17:00:00 emanage rake: 69922002164140   job:
Jul 16 17:00:00 emanage rake: 69922002164140     Rufus::Scheduler::CronJob "00 23 * * *" {}
Jul 16 17:00:00 emanage rake: 69922002164140   error:
Jul 16 17:00:00 emanage rake: 69922002164140     69922002164140
Jul 16 17:00:00 emanage rake: 69922002164140     SocketError
Jul 16 17:00:00 emanage rake: 69922002164140     getaddrinfo: Name or service not known


Solutions:

Follow these steps to resolve problem 1:

1. Open port 443 outbound from EMS server to api.sendgrid.com

2. Verify by running telnet on the EMS:

root@emanage ~# telnet api.sendgrid.com 443
Trying 159.122.224.200...
Connected to api.sendgrid.com.
Escape character is '^]'.
^]
telnet> quit
Connection closed.


Follow these steps to resolve problem 2:

If secondary EMS is deployed this procedure should be executed on both.

1. Change resolve configuration mode

root@emanage ~# chmod 644 /etc/resolv.conf

2. Restart emanage service

root@emanage ~# systemctl restart emanage


Forcing a Manual CallHome Request:

root@emanage2 /elastifile/emanage# ./console.sh
Loading production environment (Rails 4.2.3)
irb(main):001:0> CallHome.call
Sent call home report
=> true






S
Snir is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.