Re: ceph.log using seconds since epoch instead of date/time stamp

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

 



I looked at that last year, I'm sure this is fixed in 17.2.8 and newer.

Zitat von "Stillwell, Bryan" <bstillwe@xxxxxxxxxx>:

Does anyone know why log entries in ceph.log and ceph.audit.log would use seconds since epoch on Quincy 17.2.7/Ubuntu 20.04, but ceph-mon.*.log and ceph-osd.*.log use date/time stamps?

Example:
# ceph.log
1740114003.665984 osd.243 (osd.243) 2137 : cluster [DBG] 3.1615 scrub ok

# ceph-mon.log
2025-02-21T00:00:01.814-0500 7fe33378e700 0 mon.XXXXXX@0(leader) e2 handle_command mon_command({"prefix": "osd dump"} v 0) v1

This doesn't seem to be the case on my home cluster running Squid 19.2.1/Ubuntu 24.04.

I found this Proxmox forum post that seems to imply that could be a distro setting (same Ceph version, but bookworm is affected, and bullseye is not):

https://forum.proxmox.com/threads/ceph-log-file-switched-to-unix-timestamp.138078/

Thanks,
Bryan
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx


_______________________________________________
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