question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

mon demon ignoring monitor_address

See original GitHub issue

ansible 2.8. ceph-ansible 4.0.5. ceph nautilus

previously I was trying things with a single interface. now I’m trying with a more real physical config, and multiple nics. starting from scratch.

I’ve specified monitor_address: as a specific IP addr in all.yml

that IP address is successfully showing up in /etc/ceph/ceph.conf

but the actual mon demon listening on port 3300… is listening on a DIFFERENT IP address. It happens to be listening on the first IP address returned by “Ip addr”. and ONLY that IP address.

Seems like a bug to me.

If this is actually “working as designed”, and it is expected that sysadmin is required to specify interface name in the case of having multiple interfaces… then one might call this a documentation bug.

currently, the comments, aka documetation, say,

"If you want to specify for each monitor which address the monitor will bind to you can set it in your **inventory host file** by using 'monitor_address' variable.
 Preference will go to monitor_address if both monitor_address and monitor_interface are defined.

but… I DID specify monitor_address. and it is not affecting the address the monitor binds to.

(where is the actual demon configured? I looked through /etc/systemd/system/ceph-mon.target.wants/ceph-mon@corpceph1n01.service and /etc/sysconfig/ceph but didnt see anything promising. )

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
dsavineaucommented, Dec 10, 2019

if you specify monitor_address the ceph-mon daemon will bind on that IP address. if you specify monitor_interface the ceph-mon daemon will bind on the first IP address present on that interface. if you specify monitor_address_block the ceph-mon daemon will bind on the first IP address present in that CIDR range present on the node.

0reactions
stale[bot]commented, Jan 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

AF91sv AF Drives Instruction Manual - Eaton
Mon. DEC1. F203 Deceleration 1, 2nd motor. Standard default deceleration,. 2nd motor. Yes 0.1 to. 3000 sec. ... Core monitor address (Reserved) DO...
Read more >
Parent–Student - Berkeley Unified School District
mon Core Standards. The new tests are called “Smarter Balanced” as- sessments and go beyond multiple-choice questions to include extended.
Read more >
The SPARCengineTW IE CPU Card User's Manual
ignored. NOTE System space accesses can only be done using the "alternate space" instructions described in the SPARe Architecture Manual.
Read more >
Enforcing Unique Code Target Property for Control-Flow ...
With this novel method, our PT parser can simply ignore all TNT packets and focuses on the TIP packets that encode BBIDs (detailed...
Read more >
Effectiveness of a Training Program to Enhance Clinical ...
how supervisors monitor, address, and refine counseling skills of their supervisees may be ... mon content themes evident across groups (operationally.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found