OK good you also noticed

I accessed it and found it was rebooted this morning
reboot   system boot  3.2.0-4-amd64    Sun May  8 04:25   still running

after SEVERAL OOM kills of rsync :/

the last OOM kill is this

May 7 19:50:06 files kernel: [8375607.300994] Killed process 31397 (rsync) total-vm:23224kB, anon-rss:3676kB, file-rss:92kB


after this just cron, silence

then a boot at 4:25

May 8 04:25:51 files rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="1400" x-info="http://www.rsyslog.com"] start


I think this is some DDOS or maybe a wrong setting of some mirror.


the service is restored now
we need some sort of load balancing for rsync