Re: podman daemons in error state - where to find logs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Really? Under what user do these containers (osd,msd,mgr etc) run then? I have practically all containers running with specific users. Just to make sure that if there is some sort of issue with the orchestrator, the issue will be limited to the used userid.

I think with cephadm/Ubuntu/podman and the default config, daemons are run under ceph user (user id 167). The logs are forwarded from ceph daemons to conmon (through stderr), then to journald (because containers are started with “--log-driver journald”), then rsyslogd will pick up logs from journald.

With cephadm/Ubuntu/docker, logs are forwarded from ceph daemons to dockerd (through stderr), then to the docker process that starts the container, then to journald (through stderr)

So, to get logs of ceph daemons deployed by cephadm with default configs, one can use “journalctl” command to fetch logs from journald, or by any means configured with syslog. The “cephadm logs” command currently actually invokes journalctl under the hook, but is less flexible, e.g. it seems I cannot pass “--since 16:00” to “cephadm logs”.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux