Skip to main content

Motadata Web Console and Discovery issue

1. Motadata service could not start​

Linux Server: Permission denied error:

Provide 775 permission on worker, worker-manager and motadata files in the motadata directory.

Check for SELinux if It is disabled or not, if not then disable it. To disable SELinux run below mentioned commands:

#sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/g’ /etc/sysconfig/selinux

#sed -i ‘s/SELINUX=enabled/SELINUX=disabled/g’ /etc/sysconfig/selinux

#sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/g’ /etc/selinux/config

#sed -i ‘s/SELINUX=enabled/SELINUX=disabled/g’ /etc/selinux/config

#setenforce 0

2. Linux Server​

Check if java, motadata, redis, elasticsearch, worker, nsq, jetty and metadata-db-engine all processes are running.

Check with Elasticsearch health with below URL. it should be in yellow or green.

http://localhost:9200/_plugin/head

3. NSQ Reque Check​

Check nsq status with below steps:

#cd /motadata/motadata/nsq/bin

#./nsqadmin --lookupd-http-address=localhost:4161 &

And check nsq with the web on http://localhost:4171

4. Elasticsearch issue​

An issue with index creation. While you start motadata-db-engine and in all index, there are 8 shards per index. If any one index is not able to initialize even a single shard and after a wait, for too long there is no progress then, goto #cd elasticsearch/data/motadata-cluster/nodes/0/indices/ index-name

index name: place the index name which is not initializing

If there is even 1 folder in nodes, delete that folder also.

[example : elasticsearch/data/motadata-cluster/nodes/1/indices/ index-name]

5. License Expired​

  • Specify assigned permissions to the license file. It must have read permissions
  • In a case of any changes in date-time or Time zone after Motadata Installation has been done will cause License to expire latest by the end of the day.
  • Provide license file to the Mindarray Support team.
  • License file with MAC address: Check if the MAC address with the license is in all Caps. Small characters might not work.

6. Discovery Issues​

  • Check if ping is working using the Motadata Utility for Master Server.
  • Similarly, check port availability.
  • Check logs for Discovery_Engine_Error in motadata > logs folder.
  • Refer Prerequisite document configuration verification.
  • SNMP response failed or Authentication failed Notification
  • Make sure the SNMP is enabled on the device to be discovered
  • The community must be correct.
  • SNMPv3 Device: Make sure to set the password of minimum 8 characters for Authentication.

Device Discovering but data is not coming in dashboard (error - all thread failed).

note

Generally error comes because of memory issue, Check available memory and which process is Utilizing more memory, Like in my case java is utilizing more than 40%. Stop motadata service, Kill java process and start motadata again.

7. Flow Not Being Captured​

  • Check if the network device is Flow enabled

  • Check the version of the Flow and I the same plugin is available in motadata.

  • Check with TCP Dump command if we are receiving Flow to Motadata server.:

    tcpdump -i eth0 src Switch\_IP\_Address\_where\_Flow\_Enabled

If Flow is coming on tcpdump, check configuration file for flow.:

/motadata/motadata/config/motadata-config

8. Logs Not Being Captured​

  • Check if the network device Syslog is Configured.
  • Check the Log parser plugin is available in motadata.
  • Check with TCPDump Commands if we are receiving logs to Motadata Server.

9. Web Console is slow​

  • Get Memory, RAM, CPU Utilization.
  • Check Polling interval. If it is too less on too many monitors then that may make it slow.
  • Check the exact location where the performance is slow in specific cases.
  • In a case of Report generation, check a number of monitors, attributes and time span selected.
  • Browser might crash in handling a high amount of data.
  • Change the granularity in such cases.Check if there are too many Global notifications.

10. Mail Delivery Issues​

  • Mail Server might be taking the time to send Email agent might refresh the mail after the certain interval.
  • Mail Server could not be connected.
  • Check Global Notifications in Motadata to see any error.