Nice, there it is. Thanks a lot! On 26.01.2017 09:43, Henrik Korkuc wrote: > just to add to what Pawel said: /etc/logrotate.d/ceph.logrotate > > On 17-01-26 09:21, Torsten Casselt wrote: >> Hi, >> >> that makes sense. Thanks for the fast answer! >> >> On 26.01.2017 08:04, Paweł Sadowski wrote: >>> Hi, >>> >>> 6:25 points to daily cron job, it's probably logrotate trying to force >>> ceph to reopen logs. >>> >>> >>> On 01/26/2017 07:34 AM, Torsten Casselt wrote: >>>> Hi, >>>> >>>> I get the following line in journalctl: >>>> >>>> Jan 24 06:25:02 ceph01 ceph-osd[28398]: 2017-01-24 06:25:02.302770 >>>> 7f0655516700 -1 received signal: Hangup from PID: 18157 task name: >>>> killall -q -1 ceph-mon ceph-mds ceph-osd ceph-fuse radosgw UID: 0 >>>> >>>> It happens every day at the same time which is the cron.daily time. But >>>> there's no cronjob I can relate to ceph in the appropriate folder. >>>> The cluster runs just fine, so it seems it restarts automatically after >>>> the SIGHUP. Still I'm curious why the signal is sent every morning. >>>> >>>> I use Kraken on Debian Jessie systems. Three monitors, 36 OSDs on three >>>> nodes. >>>> >>>> Thanks! >>>> Torsten > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- Torsten Casselt, IT-Sicherheit, Leibniz Universität IT Services Tel: +49-(0)511-762-799095 Schlosswender Str. 5 Fax: +49-(0)511-762-3003 D-30159 Hannover _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |