Apache Error Log

[AdPatron]

Anyone know how to turn this off for good? I've commented it out in the conf file, but it still comes back and gets overloaded with messages.

[Lassitor]

Send it to > DEV NULL

[AdPatron]

Send it to > DEV NULL

Can you you give me the command I would use to achieve this?

[AdPatron]

ErrorLog /dev/null ?

[AdPatron]

I went ahead and used this ^^^ since that is what most people say when I looked it up on google. Thanks! Seems to be working.

[CodeR70]

Anyone know how to turn this off for good? I've commented it out in the conf file, but it still comes back and gets overloaded with messages.

Maybe you should try to fix the errors. Ignoring them can be a very bad idea.

[rob04]

Maybe you should try to fix the errors. Ignoring them can be a very bad idea.

Agreed, if it's taking up too much space or logging too much you change the level of logging if the errors aren't realistic to fix.

[fatfoo]

JoesTraffic is good quality traffic. No doubt. I used to get 250%+ productivity from it. But, that was a few years ago.

[AdPatron]

Maybe you should try to fix the errors. Ignoring them can be a very bad idea.

They're not errors. Most of the messages are just missing files like favicon.ico.

I however have fixed this problem by pointing the error log to dev null.

[AdPatron]

Agreed, if it's taking up too much space or logging too much you change the level of logging if the errors aren't realistic to fix.

As I said in my first post, the error log was still recording even though I turned it off. It shouldn't have been logging any messages at all.

[maxprohost]

Try setting the error log to clear itself every so often in the cron. prevents the log from bloating, but still keeps it around just in case.

[AdPatron]

Try setting the error log to clear itself every so often in the cron. prevents the log from bloating, but still keeps it around just in case.

It was suppose to be set to off, which is what the problem was.... it wouldn't turn off.

[CodeR70]

It was suppose to be set to off, which is what the problem was.... it wouldn't turn off.

Joe, I know these things can be very annoying, but there are times when you really need the error log. Switching it on when you need it might be too late to really try to track down an issue.

Another thing which is a good option is to rotated your logs. This can be based on size or based on a time period. You can also do this with your access log or other log files. In this way you avoid having the logs grow and grow but you still keep the advantage of having them around when you need to. In addition you can have your inactive logs compressed so they don't eat your drive space. All this is a fully automated process. So you or your admins have to set it up once and after that you never have to worry about them anymore.

If you notice something in your log file you think is fixable but you dont know how then maybe post some log lines here. If it PHP related or such then maybe I can help.

Anyway, just a few thoughts. Feel free to drop me a line private if you prefer.

[AdPatron]

Joe, I know these things can be very annoying, but there are times when you really need the error log. Switching it on when you need it might be too late to really try to track down an issue. Another thing which is a good option is to rotated your logs. This can be based on size or based on a time period. You can also do this with your access log or other log files. In this way you avoid having the logs grow and grow but you still keep the advantage of having them around when you need to. In addition you can have your inactive logs compressed so they don't eat your drive space. All this is a fully automated process. So you or your admins have to set it up once and after that you never have to worry about them anymore. If you notice something in your log file you think is fixable but you dont know how then maybe post some log lines here. If it PHP related or such then maybe I can help. Anyway, just a few thoughts. Feel free to drop me a line private if you prefer.

I have it taken care of, I've been a web developer since '94 (C/C++, Perl, PHP, etc). This is however the first time the error log has refused to turn itself off when I needed it to. In the past, I've always left it on so I could debug my code. However, my system (which I coded) is extremely stable and if there is a problem, I'll know how to fix since I code everything long hand.

[CodeR70]

I have it taken care of, I've been a web developer since '94 (C/C++, Perl, PHP, etc). This is however the first time the error log has refused to turn itself off when I needed it to. In the past, I've always left it on so I could debug my code. However, my system (which I coded) is extremely stable and if there is a problem, I'll know how to fix since I code everything long hand.

Weird, it's a real mystery to my that you want to switch it off especially knowing your experience now. Anyway, you know best. ;)

[AdPatron]

Weird, it's a real mystery to my that you want to switch it off especially knowing your experience now. Anyway, you know best. ;)

I'm not ignoring my own issues, you can't expect people to do the same thing as you.

[CodeR70]

I'm not ignoring my own issues, you can't expect people to do the same thing as you.

True, but a 26 years experience developer who want to switch of an overloaded error log and then claims to have a stable system and know how to fix issues is not really convincing to me.

[AdPatron]

True, but a 26 years experience developer who want to switch of an overloaded error log and then claims to have a stable system and know how to fix issues is not really convincing to me.

You basically just said the same thing to me, but with different words. Why are you wasting your time on this?

[CodeR70]

You basically just said the same thing to me, but with different words. Why are you wasting your time on this?

Yeah, I wondering myself as well. The thing is, if you had spend 10 seconds on Google you would not have wasted all our time. People tried to help you in this thread but your ego did not like it very much.