Comments on: SysAdmins are like Auto Mechanics http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/ Sudi and Steven's Blog Fri, 20 Aug 2010 19:31:38 -0700 http://wordpress.org/?v=2.9 hourly 1 By: Dan http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/comment-page-1/#comment-90 Dan Fri, 17 Mar 2006 06:23:08 +0000 http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/#comment-90 But that would make too much sense. :-) But that would make too much sense. :-)

]]> By: Mark http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/comment-page-1/#comment-89 Mark Fri, 17 Mar 2006 05:54:53 +0000 http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/#comment-89 If you don't run log analyzers, why don't you turn off general loging? Just keep the error log. Also, might look into some log rotate utilities. You can probably find an RPM for one. As for Dan's situation, he has a cron which empties the /tmp directory. So I just appended that cron with a line that recreated the link. On second thought, I should have modified the command to sipmly omit the link. If you don’t run log analyzers, why don’t you turn off general loging? Just keep the error log.

Also, might look into some log rotate utilities. You can probably find an RPM for one.

As for Dan’s situation, he has a cron which empties the /tmp directory. So I just appended that cron with a line that recreated the link. On second thought, I should have modified the command to sipmly omit the link.

]]> By: Steven http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/comment-page-1/#comment-87 Steven Thu, 16 Mar 2006 18:52:23 +0000 http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/#comment-87 It actually wasn't my error log, it was my digitalart.org log. When it reached 2 GB (I think) my error_log started filling up with messages saying my da.o log reached its limit. This happens every month or so and I really should setup a cronjob to keep things in check every now and then. I don't run any log analyzers, which usually clean this stuff up on their own. It actually wasn’t my error log, it was my digitalart.org log. When it reached 2 GB (I think) my error_log started filling up with messages saying my da.o log reached its limit. This happens every month or so and I really should setup a cronjob to keep things in check every now and then. I don’t run any log analyzers, which usually clean this stuff up on their own.

]]> By: Dan http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/comment-page-1/#comment-86 Dan Thu, 16 Mar 2006 17:55:43 +0000 http://www.sudste.com/2006/03/16/sysadmins-are-like-auto-mechanics/#comment-86 That sucks. You know, I used to have the /tmp/mysql.sock missing link problem. Mark helped me with it and it turns out some service designed to clean up old temp files or something was deleting my /tmp/mysql.sock link. So we added a cron job which recreates the link every day. So it never gets old and it never gets deleted anymore. LOL. 2GB for a LOG???!!!??? WOW. Filled with what? 2 billion lines of the same error? You don't suppose someone is trying to attack your server do you? Now go wash off that grease of your hands, don't wana get your keyboard all gunky. That sucks. You know, I used to have the /tmp/mysql.sock missing link problem. Mark helped me with it and it turns out some service designed to clean up old temp files or something was deleting my /tmp/mysql.sock link. So we added a cron job which recreates the link every day. So it never gets old and it never gets deleted anymore. LOL.

2GB for a LOG???!!!??? WOW. Filled with what? 2 billion lines of the same error? You don’t suppose someone is trying to attack your server do you?

Now go wash off that grease of your hands, don’t wana get your keyboard all gunky.

]]>