Web[ceph-users] prometheus has failed - no socket could be created. Steven Vacaroaia Wed, 22 Aug 2024 09:09:41 -0700. Hi, I am trying to enable prometheus on Mimic so I can use it with cephmetrics ... Module 'prometheus' has failed: error('No socket could be created',) .." here is some info ( all commons ran on MON where the MGR is also installled ... WebHost Name and Port¶. Like most web applications, dashboard binds to a TCP/IP address and TCP port. By default, the ceph-mgr daemon hosting the dashboard (i.e., the currently active manager) will bind to TCP port 8443 or 8080 when SSL is disabled.. If no specific address has been configured, the web app will bind to ::, which corresponds to all …
executing python file in terminal - socket.error: no socket could be ...
WebThe dashboard module shows «No socket could be created» with hostnetwork=true #3474 Comments. Is this a bug report or feature request? Deviation from expected behavior: … WebMay 27, 2024 · Since you seem to have 3 nodes: 1 master and 2 workers, 2 pods get created, one on kube2 and one on kube3 node. kube1 is master node tainted as unschedulable so rook-ceph-mon-c cannot be scheduled there. To solve it you can: add one more worker node remove NoSchedule taint with kubectl taint nodes kube1 … kitikmeot inuit association contact
[ceph-users] prometheus has failed - no socket could be created
WebUnfortunately the kernel client does not support the admin socket, but it has similar (if limited) interfaces if your kernel has debugfs enabled. There will be a folder in … WebApr 7, 2016 · So the solution is adding public_addr into ceph.conf file like this: public_network = 192.168.111.0/24 Share Improve this answer Follow answered May 3, 2024 at 1:53 user7954943 21 2 I've tried by adding the mentioned line in ceph.conf file. WebAug 21, 2016 · @sparrc You need superuser access pre-infernalis according to my production cluster. I can spin up a Jewel cluster in OpenStack to confirm the post-infernalis behaviour requires the ceph user, but as of infernalis ceph runs unprivileged as its own user, so I'd be unsurprised if the socket belonged to the process user. mage and the demon queen characters