Thanks for info. -Dhiraj From: haosdent <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, 19 April 2016 3:46 pm To: user <[email protected]<mailto:[email protected]>> Subject: Re: Log with warning filling "disk user.log.WARNING.20160416"
>Why doesn't it log all log info under 1 log file? At least for same day? Actually there are from different processes, google glog library use this filename format in log. ``` <program name>.<hostname>.<user name>.log.<severity level>.<date>.<time>.<pid> ``` Unfortunately, google glog didn't provide flags to config this format. On Tue, Apr 19, 2016 at 6:02 PM, Dhiraj Thakur <[email protected]<mailto:[email protected]>> wrote: Ok So we need to rotate these log through log rotate? I thought there would be a log rotate option within Mesos. Btw why mesos is creating so many files of same type like INFO? Why doesn't it log all log info under 1 log file? At least for same day? -Dhiraj From: haosdent <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, 19 April 2016 3:27 pm To: user <[email protected]<mailto:[email protected]>> Subject: Re: Log with warning filling "disk user.log.WARNING.20160416" Have you try use logrotate to manage mesos log? https://github.com/deric/mesos-deb-packaging/blob/master/debian/logrotate On Tue, Apr 19, 2016 at 5:49 PM, Dhiraj Thakur <[email protected]<mailto:[email protected]>> wrote: Hi, Mesos is creating quite a lot warning log file under /var/log/mesos/archive and it is filling up disk. -rw-r--r-- 1 root root 3128 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163811.16879.1 -rw-r--r-- 1 root root 3128 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163756.16849.1 -rw-r--r-- 1 root root 3056 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163751.16830.1 -rw-r--r-- 1 root root 3128 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163740.16795.1 -rw-r--r-- 1 root root 3056 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163735.16776.1 -rw-r--r-- 1 root root 3056 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163705.16727.1 -rw-r--r-- 1 root root 3128 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163655.16703.1 -rw-r--r-- 1 root root 3056 Apr 19 00:00 mesos-fetcher.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160418-163635.16649.1 -rw-r--r-- 1 root root 1280386 Apr 19 00:00 mesos-slave.i**-**-**-*ec2.internal.invalid-user.log.WARNING.20160416-182536.4557.1 -rw-r--r-- 1 root root 940234 Apr 19 00:00 mesos-slave.i**-**-**-*ec2.internal.invalid-user.log.INFO.20160416-182536.4557.1 -rw-r--r-- 1 root root 1058180 Apr 19 00:00 mesos-slave.i**-**-**-*ec2.internal.invalid-user.log.ERROR.20160416-182536.4557.1 Is there any way to configure log? I wonder why it is creating so many log files of similar log type? -Dhiraj -- Best Regards, Haosdent Huang -- Best Regards, Haosdent Huang
