Mailroom crash when lost IMAP connection
Summary
bundler: failed to load command: mail_room (/home/git/gitlab/vendor/bundle/ruby/2.4.0/bin/mail_room)
Net::IMAP::ByeResponseError: AXIGEN Proxy front1 IMAP4rev1: cannot connect to AXIGEN
/usr/local/lib/ruby/2.4.0/net/imap.rb:1188:in `get_tagged_response'
/usr/local/lib/ruby/2.4.0/net/imap.rb:1248:in `block in send_command'
/usr/local/lib/ruby/2.4.0/monitor.rb:214:in `mon_synchronize'
/usr/local/lib/ruby/2.4.0/net/imap.rb:1230:in `send_command'
/usr/local/lib/ruby/2.4.0/net/imap.rb:434:in `login'
/home/git/gitlab/vendor/bundle/ruby/2.4.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:84:in `log_in'
/home/git/gitlab/vendor/bundle/ruby/2.4.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:68:in `setup'
/home/git/gitlab/vendor/bundle/ruby/2.4.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:54:in `rescue in wait'
/home/git/gitlab/vendor/bundle/ruby/2.4.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:44:in `wait'
/home/git/gitlab/vendor/bundle/ruby/2.4.0/gems/mail_room-0.9.1/lib/mail_room/mailbox_watcher.rb:34:in `block in run'
Steps to reproduce
Temporary shutdown mail server
What is the current bug behavior?
Service crash and stopped till manual start
What is the expected correct behavior?
Wait and reconnect
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Current User: git Using RVM: no Ruby Version: 2.4.4p296 Gem Version: 2.6.14.1 Bundler Version:1.16.3 Rake Version: 12.3.1 Redis Version: 4.0.11 Git Version: 2.18.0 Sidekiq Version:5.1.3 Go Version: go1.11 linux/amd64
GitLab information Version: 11.2.2 Revision: c815ed0383d Directory: /home/git/gitlab DB Adapter: postgresql URL: https://git-wal.colvir.ru HTTP Clone URL: https://git-wal.colvir.ru/some-group/some-project.git SSH Clone URL: git@git-wal.colvir.ru:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers: google_oauth2, cas3
GitLab Shell Version: 8.1.1 Repository storage paths:
- default: /home/git/repositories Hooks: /home/git/gitlab-shell/hooks Git: /usr/local/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: ... Running /home/git/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /home/git/.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? ... yes MailRoom running? ... yes
Checking Reply by email ... Finished
Checking LDAP ...
Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results)
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? ... yes Init script up-to-date? ... yes Projects have namespace: ... 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: ... 12
Checking GitLab ... Finished