AnsweredAssumed Answered

Software version alarms

Question asked by terryhealy on Jun 22, 2018
Latest reply on Jun 25, 2018 by terryhealy

Just upgraded to 6.0.1 and have a question about software versions alarms, and perhaps an MCS enhancement request. When a version alarm is received, how can I find out exactly what package is causing the alarm and the expected vs. observed versions on the machine? It seems like this information should be in the "Alarm Information" pop-up in MCS; the 'recommended action' says only to 'restore the correct version of any services you have modified', which is of no help at all. 

 

In this case the node is CentOS 76, and looking at installed packages does not show anything glaring that jumps out to me, other than there seem to be a lot more things in there than under 5.2

 

/opt/mapr/logs]# rpm -qa |grep "^mapr"


mapr-drill-1.13.0.201803281600-1.noarch
mapr-core-6.0.1.20180404222005.GA-1.x86_64
mapr-installer-1.9.0.201803291415-1.noarch
mapr-drill-internal-1.13.0.201803281600-1.noarch
mapr-asynchbase-1.7.0.201711021603-1.noarch
mapr-librdkafka-0.11.3.201803231414-1.noarch
mapr-core-internal-6.0.1.20180404222005.GA-1.x86_64
mapr-fileserver-6.0.1.20180404222005.GA-1.x86_64
mapr-hbase-1.1.8.201711121557-1.noarch
mapr-kafka-connect-jdbc-4.0.0.201803240037-1.noarch
mapr-spark-2.2.1.201804031348-1.noarch
mapr-nfs-6.0.1.20180404222005.GA-1.x86_64
mapr-hadoop-core-2.7.0.20180404222005.GA-1.x86_64
mapr-nodemanager-2.7.0.20180404222005.GA-1.x86_64
mapr-hbase-rest-1.1.8.201711121557-1.noarch
mapr-kafka-connect-hdfs-4.0.0.201804061418-1.noarch
mapr-mapreduce2-2.7.0.20180404222005.GA-1.x86_64
mapr-installer-definitions-1.9.0.201803291415-1.noarch
mapr-kafka-1.0.1.201803222228-1.noarch
mapr-collectd-5.7.2.201804032030-1.x86_64
mapr-kafka-rest-4.0.0.201804031926-1.noarch

Outcomes