December 13, 201411 yr So my server has been rock solid with my new setup. A couple of MCE's here and there but nothing that really kills the normal operation of the server (in fact i've noticed no ill effects of the MCE's at all). Today I noticed however that my syslog ends on Dec 1. Server has been up fine since then (my daughter is watching Frozen right now, actually). Last reboot was Oct 27/2014 when I upgraded to 5.0.6. Anyone else experience this? Snippet of log, it literally stopped recording mid-way through a log statement. The parity check going on at the time finished just fine as well. Nov 30 20:53:21 Tower kernel: mdcmd (290): spindown 3 Dec 1 00:00:01 Tower kernel: mdcmd (291): check NOCORRECT Dec 1 00:00:01 Tower kernel: Dec 1 00:00:01 Tower kernel: md: recovery thread woken up ... Dec 1 00:00:01 Tower kernel: md: recovery thread checking parity... Dec 1 00:00:01 Tower kernel: md: using 2048k window, over a total of 2930266532 blocks. Dec 1 00:47:04 Tower sSMTP[25631]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=792 Dec 1 01:47:03 Tower sSMTP[27148]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=792 Dec 1 02:47:03 Tower sSMTP[28662]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=792 Dec 1 03:40:01 Tower logger: mover started Dec 1 03:40:01 Tower logger: skipping */ Dec 1 03:40:01 Tower logger: mover finished Dec 1 03:47:03 Tower sSMTP[30182]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=792 Dec 1 04:47:03 Tower sSMTP[31723]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=792 Dec 1 05:47:03 Tower sSMTP[784]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=792 Dec 1 06:47:04 Tower sSMTP[2354]: Sent mail for
Archived
This topic is now archived and is closed to further replies.