[
https://issues.apache.org/jira/browse/METRON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329587#comment-16329587
]
Laurens Vets commented on METRON-1408:
--------------------------------------
Some more debugging. Otto asked me to look at
[https://community.hortonworks.com/content/supportkb/150336/errorrequired-configs-hbase-logsearch-conf-isare-n.html.]
When rename metron-alerts-ui-env.xml metron-alerts-ui-env.xml.backup,
ambari-server starts fine, but the "Alerts UI" tab is greyed out/not accessible
in the Ambari UI.
> Upgrade from 0.4.1 to 0.4.2 fails on Alerts UI
> ----------------------------------------------
>
> Key: METRON-1408
> URL: https://issues.apache.org/jira/browse/METRON-1408
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.4.2
> Reporter: Laurens Vets
> Priority: Major
>
> I've started upgrading my environment from 0.4.1 to 0.4.2 and run into some
> issues with alerts-ui. I've done the following:
> * Stop all services.
> * Build Metron 0.4.2.
> * Build Metron 0.4.2 RPMs.
> * Install Metron 0.4.2 RPMs with "rpm -Uvh metron*.rpm". This results in an
> error:
> {code:java}
> [root@metron1 localrepo]# rpm -Uvh metron*.rpm
> Preparing... ########################################### [100%]
> 1:metron-solr ########################################### [ 7%]
> 2:metron-rest ########################################### [ 14%]
> 3:metron-profiler ########################################### [ 21%]
> 4:metron-pcap ########################################### [ 29%]
> 5:metron-parsers ########################################### [ 36%]
> 6:metron-metron-managemen########################################### [ 43%]
> 7:metron-maas-service ########################################### [ 50%]
> 8:metron-indexing ########################################### [ 57%]
> 9:metron-enrichment ########################################### [ 64%]
> 10:metron-elasticsearch ########################################### [ 71%]
> 11:metron-data-management ########################################### [ 79%]
> 12:metron-config ########################################### [ 86%]
> error reading information on service metron-alerts-ui: No such file or
> directory
> warning: %post(metron-config-0.4.2-201801171923.noarch) scriptlet failed,
> exit status 1
> 13:metron-common ########################################### [ 93%]
> 14:metron-alerts ########################################### [100%]
> [root@metron1 localrepo]#{code}
> However, all RPMs seem to be installed.
> * I upgraded the Mpack with:
> {code:java}
> ambari-server upgrade-mpack
> --mpack=/root/metron/metron-deployment/packaging/ambari/metron-mpack/target/metron_mpack-0.4.2.0.tar.gz
> --verbose{code}
> This worked and didn't give any errors.
> * Starting ambari-server fails:
> {code:java}
> [root@metron1 ~]# ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> DB configs consistency check failed. Run "ambari-server start
> --skip-database-check" to skip. If you use this "--skip-da
> tabase-check" option, do not make any changes to your cluster topology or
> perform a cluster upgrade until you correct th
> e database consistency issues. See
> "/var/log/ambari-server/ambari-server-check-database.log" for more details on
> the con
> sistency issues.
> Ambari database consistency check finished
> [root@metron1 ~]#{code}
> * I can start ambari-server with "ambari-server start --skip-database-check"
> and everything seems fine... (Didn't start all services yet though)
> * Doing "ambari-server check-database" results in:
> {code:java}
> 2018-01-17 21:54:11,274 INFO - ******************************* Check
> database started *******************************
> 2018-01-17 21:54:15,924 INFO - Checking for configs not mapped to any cluster
> 2018-01-17 21:54:16,002 INFO - Checking for configs selected more than once
> 2018-01-17 21:54:16,005 INFO - Checking for hosts without state
> 2018-01-17 21:54:16,006 INFO - Checking host component states count equals
> host component desired states count
> 2018-01-17 21:54:16,009 INFO - Checking services and their configs
> 2018-01-17 21:54:18,136 INFO - Processing HDP-2.5 / HDFS
> 2018-01-17 21:54:18,136 INFO - Processing HDP-2.5 / MAPREDUCE2
> 2018-01-17 21:54:18,136 INFO - Processing HDP-2.5 / TEZ
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / SPARK
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / ZOOKEEPER
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / HBASE
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / YARN
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / METRON
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / PIG
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / KIBANA
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / STORM
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / HIVE
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / SLIDER
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / AMBARI_INFRA
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / AMBARI_METRICS
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / ZEPPELIN
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / KAFKA
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / FLUME
> 2018-01-17 21:54:18,137 INFO - Processing HDP-2.5 / ELASTICSEARCH
> 2018-01-17 21:54:18,138 ERROR - Required config(s): metron-alerts-ui-env
> is(are) not available for service METRON with s
> ervice config version 2 in cluster metron
> 2018-01-17 21:54:18,195 INFO - ******************************* Check
> database completed *******************************{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
