Alertmanager not starting

Summary

Upgraded Omnibus version v11.2.1 to v11.2.3 using apt-get upgrade (Ubuntu 16.04)

Steps to reproduce

Upgrade issue

Example Project

No example

What is the current bug behavior?

Upgraded Omnibus version v11.2.1 to v11.2.3 Upgrade seemed successful but Alertmanager will not restart

What is the expected correct behavior?

Alertmanager starts

Relevant logs and/or screenshots

Lines repeat in /var/log/gitlab/alertmanager/current

2018-08-29_00:51:00.40230 level=info ts=2018-08-29T00:51:00.402197632Z caller=main.go:174 msg="Starting Alertmanager" version="(version=0.15.1, branch=master, revision=041ca4ad17ccac69b3b5c32190d624f4ff422b8c)" 2018-08-29_00:51:00.40231 level=info ts=2018-08-29T00:51:00.402279449Z caller=main.go:175 build_context="(go=go1.10.3, user=GitLab-Omnibus, date=2018-08-28T16:15:17+00:00)" 2018-08-29_00:51:00.40927 level=warn ts=2018-08-29T00:51:00.409219255Z caller=cluster.go:148 component=cluster err="couldn't deduce an advertise address: no private IP found, explicit advertise addr not provided" 2018-08-29_00:51:00.41436 level=error ts=2018-08-29T00:51:00.41431583Z caller=main.go:199 msg="unable to initialize gossip mesh" err="create memberlist: Failed to get final advertise address: No private IP address found, and explicit IP not provided"

Output of checks

self hosted

Results of GitLab environment info

Expand for output related to GitLab environment info

System information System: Ubuntu 16.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.4.4p296 Gem Version: 2.7.6 Bundler Version:1.16.2 Rake Version: 12.3.1 Redis Version: 3.2.11 Git Version: 2.18.0 Sidekiq Version:5.1.3 Go Version: unknown

GitLab information Version: 11.2.3-ee Revision: aadca99 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.8 URL: https://gitlab.ecs.vuw.ac.nz HTTP Clone URL: https://gitlab.ecs.vuw.ac.nz/some-group/some-project.git SSH Clone URL: git@gitlab.ecs.vuw.ac.nz:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: no

GitLab Shell Version: 8.1.1 Repository storage paths:

  • default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

Checking GitLab Shell ...

GitLab Shell version >= 8.1.1 ? ... OK (8.1.1) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... .. many all OK or empty .. 554/3037 ... repository is empty Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK

Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Reply by email ...

IMAP server credentials are correct? ... yes Init.d configured correctly? ... skipped MailRoom running? ... skipped

Checking Reply by email ... Finished

Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... ..all yes ..

Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.4.4) Git version >= 2.9.5 ? ... yes (2.18.0) Git user has default SSH configuration? ... yes Active users: ... 646 Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)

Checking GitLab ... Finished