Feature #45876
Updated by Sebastian Wagner almost 4 years ago
<pre>
INFO:cephadm:Verifying port 9100 ...
WARNING:cephadm:Cannot bind to IP 0.0.0.0 port 9100: [Errno 98] Address already in use
ERROR: TCP Port(s) '9100' required for node-exporter is already in use
Traceback (most recent call last):
File "/usr/share/ceph/mgr/cephadm/module.py", line 1638, in _run_cephadm
code, '\n'.join(err)))
RuntimeError: cephadm exited with an error code: 1, stderr:INFO:cephadm:Deploying daemon node-exporter.ceph-mon ...
INFO:cephadm:Verifying port 9100 ...
WARNING:cephadm:Cannot bind to IP 0.0.0.0 port 9100: [Errno 98] Address already in use
ERROR: TCP Port(s) '9100' required for node-exporter is already in use
2020-05-15T13:33:46.966159+0000 mgr.ceph-mgr.dixgvy (mgr.14161) 678 : cephadm [WRN] Failed to apply node-exporter spec ServiceSpec(
{'placement': PlacementSpec(host_pattern='*'), 'service_type': 'node-exporter', 'service_id': None, 'unmanaged': False}
): cephadm exited with an error code: 1, stderr:INFO:cephadm:Deploying daemon node-exporter.ceph-mon ...
INFO:cephadm:Verifying port 9100 ...
WARNING:cephadm:Cannot bind to IP 0.0.0.0 port 9100: [Errno 98] Address already in use
ERROR: TCP Port(s) '9100' required for node-exporter is already in use
</pre>
Important bits are:
* *We already know which services want which ports.*
* we can easily prevent port conflicts for known know daemons.
* open Q: how to handle unknown daemons (i.e. pre-existing node expoter)