Gitlab-monitor fails to start, drives high CPU usage

Hello,

gitlab-monitor fails to start successfully, and it appears its constant attempts to start are driving CPU usage to close to 50%. Over time this causes severe performance degradation which is temporarily resolved via reboot.

This is the error I am seeing in the logs (/var/log/gitlab/gitlab-monitor/current), repeated every few seconds:

2017-07-21_18:14:19.04827 [2017-07-21 14:14:19] INFO  WEBrick 1.3.1
2017-07-21_18:14:19.04842 [2017-07-21 14:14:19] INFO  ruby 2.3.3 (2016-11-21) [x86_64-linux]
2017-07-21_18:14:19.05627 /opt/gitlab/embedded/lib/ruby/2.3.0/socket.rb:231:in `getaddrinfo': getaddrinfo: Name or service not known (SocketError)
2017-07-21_18:14:19.05705       from /opt/gitlab/embedded/lib/ruby/2.3.0/socket.rb:231:in `foreach'
2017-07-21_18:14:19.05708       from /opt/gitlab/embedded/lib/ruby/2.3.0/socket.rb:757:in `tcp_server_sockets'
2017-07-21_18:14:19.05711       from /opt/gitlab/embedded/lib/ruby/2.3.0/webrick/utils.rb:65:in `create_listeners'
2017-07-21_18:14:19.05713       from /opt/gitlab/embedded/lib/ruby/2.3.0/webrick/server.rb:134:in `listen'
2017-07-21_18:14:19.05720       from /opt/gitlab/embedded/lib/ruby/2.3.0/webrick/server.rb:115:in `initialize'
2017-07-21_18:14:19.05724       from /opt/gitlab/embedded/lib/ruby/2.3.0/webrick/httpserver.rb:47:in `initialize'
2017-07-21_18:14:19.05727       from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/rack-1.6.8/lib/rack/handler/webrick.rb:31:in `new'
2017-07-21_18:14:19.05729       from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/rack-1.6.8/lib/rack/handler/webrick.rb:31:in `run'
2017-07-21_18:14:19.05732       from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1506:in `start_server'
2017-07-21_18:14:19.05736       from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1444:in `run!'
2017-07-21_18:14:19.05741       from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/gitlab-monitor-1.9.0/lib/gitlab_monitor/cli.rb:317:in `run'
2017-07-21_18:14:19.05745       from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/gitlab-monitor-1.9.0/bin/gitlab-mon:11:in `main'
2017-07-21_18:14:19.05747       from /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/gitlab-monitor-1.9.0/bin/gitlab-mon:17:in `<top (required)>'
2017-07-21_18:14:19.05750       from /opt/gitlab/embedded/bin/gitlab-mon:22:in `load'
2017-07-21_18:14:19.05753       from /opt/gitlab/embedded/bin/gitlab-mon:22:in `<main>'

Environment info:

$ sudo gitlab-rake gitlab:env:info

System information
System:         RedHatEnterpriseServer 6.5
Current User:   git
Using RVM:      no
Ruby Version:   2.3.3p222
Gem Version:    2.6.6
Bundler Version:1.13.7
Rake Version:   10.5.0
Redis Version:  3.2.5
Git Version:    2.13.0
Sidekiq Version:5.0.0
Go Version:     unknown

GitLab information
Version:        9.3.9
Revision:       755bb71
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            [omitted]
HTTP Clone URL: [omitted]
SSH Clone URL:  [omitted]
Using LDAP:     yes
Using Omniauth: no

GitLab Shell
Version:        5.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

Any suggestions are welcome!

Thanks,
Andrew