Exiting: resource 'metricbeat-7.4.0' exists, but it is not an alias

I update my metricbeat from 7.1.0. It is ok.

But today it didn't work. When I input this -'sudo metricbeat setup -e';

2019-10-21T17:30:15.706+0800	INFO	template/load.go:169	Existing template will be overwritten, as overwrite is enabled.
2019-10-21T17:30:15.988+0800	INFO	template/load.go:108	Try loading template metricbeat-7.4.0 to Elasticsearch
2019-10-21T17:30:16.210+0800	INFO	template/load.go:100	template with name 'metricbeat-7.4.0' loaded.
2019-10-21T17:30:16.210+0800	INFO	[index-management]	idxmgmt/std.go:289	Loaded index template.
2019-10-21T17:30:16.242+0800	ERROR	instance/beat.go:878	Exiting: resource 'metricbeat-7.4.0' exists, but it is not an alias
Exiting: resource 'metricbeat-7.4.0' exists, but it is not an alias

And I remove it ,reinstall it .It doesn't work.

My os is ubuntu 16.04

thanks.

my config

###################### Metricbeat Configuration Example #######################

#==========================  Modules configuration ============================

metricbeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

#==================== Elasticsearch template setting ==========================

setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression
  #_source.enabled: false

#================================ General =====================================


# Optional fields that you can specify to add additional information to the
# output.
#fields:
#  env: staging


#============================== Dashboards =====================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  #host: "localhost:5601"

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

#============================= Elastic Cloud ==================================

# These settings simplify using metricbeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

#================================ Outputs =====================================

# Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
  # Array of hosts to connect to.

  hosts: ["http://xxxxxxx:9200"]

  username: "xxxx"
  password: "xxxx"


  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

#----------------------------- Logstash output --------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

#================================ Processors =====================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~

#================================ Logging =====================================

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]

#============================== Xpack Monitoring ===============================
# metricbeat can export internal metrics to a central Elasticsearch monitoring
# cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

#================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

Hi @LiuGangR,

can you add a description of what you are trying to achieve and your configuration?
Thanks

I update my desc. Thanks.

Can you also post your configuration file?

I add my config.Thanks

I think there might be an index or some other object called metricbeat-7.4.0, while metricbeat is expecting to create an alias with that same name pointing to the real index.

can you curl (use your server and credentials)
curl elasticsearch:9200/_cat/indices
(should show indices like metricbeat-7.4.0-2019.10.24-000001)

curl elasticsearch:9200/_cat/aliases
(should show alias like metricbeat-7.4.0 pointing to the index above)

if I don't have this ‘curl elasticsearch:9200/_cat/aliases’

what can I do for my problem?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.