Hi Adam!
I guess you only want the output for the 9100 port?
[root@darkside1]# ss -tulpn | grep 9100
tcp LISTEN 0 128 [::]:9100 [::]:*
users:(("node_exporter",pid=9103,fd=3))
Also, this:
[root@darkside1 ~]# ps aux | grep 9103
nfsnobo+ 9103 38.4 0.0
okay, not much info on the mon failure. The other one at least seems to be
a simple port conflict. What does `sudo netstat -tulpn` give you on that
host?
On Tue, Jul 25, 2023 at 12:00 PM Renata Callado Borges <
renato.call...@incor.usp.br> wrote:
> Hi Adam!
>
>
> Thank you for your response, but
Hi Adam!
Thank you for your response, but I am still trying to figure out the
issue. I am pretty sure the problem occurs "inside" the container, and I
don´t know how to get logs from there.
Just in case, this is what systemd sees:
Jul 25 12:36:32 darkside1 systemd[1]: Stopped Ceph
The logs you probably really want to look at here are the journal logs from
the mgr and mon. If you have a copy of the cephadm tool on the host, you
can do a "cephadm ls --no-detail | grep systemd" to list out the systemd
unit names for the ceph daemons on the host, or just look find the systemd
