Shulou(Shulou.com)06/01 Report--

This article mainly explains "Ceph due to the change of IP address caused by MON exception how to solve", the article explains the content is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in depth, together to study and learn "Ceph due to the change of IP address caused by MON exception how to solve" it!

Introduction

Due to the need to change the IP address of the machine, after the change and restart, each ceph monitoring process has an exception and cannot be started. This document is used to record and explain this problem.

Phenomenon

After changing the IP address, the direct boot mon cannot be started, and the error of binding IP address is always found. The initial guess is as follows:

The process needs to bind the local IP:PORT to listen. The address has been changed, but the binding address is still the address before modification. Binding fails, so an error is reported.

[root@gnop029-ct-zhejiang_wenzhou-16-20 ceph] #. / startmon.sh monmaptool: monmap file / etc/ceph/monmapmonmaptool: / etc/ceph/monmap exists -- clobber to overwrite'/var/lib/ceph/mon/ceph-a' already exists and is not empty: monitor may already exist=== mon.a = Starting Ceph mon.an on ceph-10...2015-11-23 13 7f4a5a36a7a0 47.855887 7f4a5a36a7a0-1 WARNING: 'mon addr' config option 101.71.4.20 clobber to overwrite'/var/lib/ceph/mon/ceph-a' already exists and is not empty 678920 7f4a5a36a7a0 0 does not match monmap file continuing with monmap configuration2015-11-23 13 13 clobber to overwrite'/var/lib/ceph/mon/ceph-a' already exists and is not empty 23 Starting Ceph mon.an on ceph-10...2015-11-23 13 Starting Ceph mon.an on ceph-10...2015-23 13 Starting Ceph mon.an on ceph-10...2015-11-23 13 Starting Ceph mon.an on ceph-10...2015-23 13 Starting Ceph mon.an on ceph-10...2015-11-23 13 Starting Ceph mon.an on ceph-10...2015-11-23 13 67.163.20 7f4a5a36a7a0 6789: (99) Cannot assign requested address2015-11-23 13 accepter.accepter.bind was unable to bind 23 accepter.accepter.bind was unable to bind 47.856085 Trying again in 5 seconds 2015-11-23 13 7f4a5a36a7a0 52.856281 7f4a5a36a7a0-1 accepter.accepter.bind unable to bind to 101.67.163.20 accepter.accepter.bind unable to bind to 6789: (99) Cannot assign requested address2015-11-23 13 7f4a5a36a7a0 23 Cannot assign requested address2015-1 accepter.accepter.bind was unable to bind. Trying again in 5 seconds 2015-11-23 13 7f4a5a36a7a0-1 accepter.accepter.bind unable to bind to 101.67.163.20 7f4a5a36a7a0-1 accepter.accepter.bind unable to bind to 101.67.163.20 accepter.accepter.bind unable to bind to 6789: (99) Cannot assign requested address2015-11-23 13 7f4a5a36a7a0 23Trying again in 57.856657 7f4a5a36a7a0-1 accepter.accepter.bind was unable to bind after 3 attempts: (99) Cannot assign requested address2015-11-23 1315 23V 57.856670 7f4a5a36a7a0-1 unable to bind monitor to 101.67.163.20:6789/0failed: 'ssh ceph-10 ulimit-n 32768 / usr/bin/ceph-mon-I a-- pid-file / var/run/ceph/mon.a.pid-c / etc/ceph/ceph.conf-- cluster ceph 'solution

Modify the ceph.conf configuration file and regenerate the monmap file to start the mon process

Regenerate the monmap file

Sudo monmaptool-- create-- generate-c / etc/ceph/ceph.conf / etc/ceph/monmap

You can also get a new monmap through the command

Monmaptool-- create-- add mon.a 101.71.4.20 add mon.a 6789-- add mon.b 101.71.4.21 add mon.b 6789\-- add mon.c 101.71.4.22 add mon.a 6789-- add mon.d 101.71.4.23 add mon.a 6789-- add mon.e 101.71.4.24 add mon.a 6789-- fsid c6e7e7d9-2b91-4550-80b0-6fa46d0644f6\-- clobber monmapmonmaptool-- print monmap

After you get the monmap, re-inject the monmap

Ceph-mon-I monid-- inject-monmap monmap

According to the above method, the problem that the monitoring process cannot be started due to the modification of IP address can be solved.

[root@ceph0 ceph] # sudo / etc/init.d/ceph-a start mon.ceph0=== mon.ceph0=== Starting Ceph mon.ceph0 on ceph0...Starting ceph-create-keys on ceph0... [root@ceph0 ceph] # ps aux | grep monroot 3768 1.00.0 226328 16784 pts/0 Sl 11:28 0:00 / usr/bin/ceph-mon-I ceph0-- pid-file / var/run/ceph/mon.ceph0.pid-c / etc/ceph/ceph. Conf-- cluster ceph Thank you for your reading The above is the content of "how to solve the MON exception caused by the change of IP address in Ceph". After the study of this article, I believe you have a deeper understanding of how to solve the problem of MON exception caused by the change of IP address in Ceph. The specific use situation also needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.