Server Administrators need to have the ability to select which domains logging may occur on or which items may be logged with apache. Minimizing the need to log data increases server performance because less disk writes are required.
By default, everything is logged including random requests from robots as well as potential hackers which in turn slows the server down.
I like this idea 
Thanks so much for your feedback! In your mind is this something that would be defined solely by server administrators, or would it be something you would want Resellers and cPanel users to be able to define as well?
Thanks so much for your feedback! In your mind is this something that would be defined solely by server administrators, or would it be something you would want Resellers and cPanel users to be able to define as well?
How would you tell the difference between, robot, hacker, visitor ? Also, most people use the logs to see how a hacker got in.
How would you tell the difference between, robot, hacker, visitor ? Also, most people use the logs to see how a hacker got in.
and cpanelbenny, This is something I believe is good for any level, but the options should be overridden by the top system administrator.
and cpanelbenny, This is something I believe is good for any level, but the options should be overridden by the top system administrator.
Dear friends, I think the ability to disable domlogs at any level would be an outstanding idea.
Given today's (and yesterday's) ever faster servers, its really easy for a domlog to grow too large in just a few hours. This will cause any server to crash, probably at a completely unexpected time, whenever the domlog gets too big. This absent feature of cPanel has caused us countless hours of downtime, lost revenues, and way too many hours of our time, our technician's time, and cPanel support's time. Its almost absurd how such a small missing feature has caused us so many problems. We have had this exact cPanel domglog issue for years now, so think that I know what I'm talking about.
Secondly, the workaround the cPanel currently suggests, but commenting out all instances of CustomLog in local copies of templates, is a flawed solution. The idea of making local templates in itself is a poor idea in my experience, because as soon as cPanel is updated the default templates will change, but any modified server will be left with potentially obsolete templates. I had just that problem recently. I modified my templates just a few months ago, but suddenly after updating to cPanel 60 my already out of date templates were causing Apache to crash when I wanted to change my PHP configuration.
Thirdly, yes I know domlogs are processed, and rotated or deleted regularly. But imagine high traffic, processing statistics can overload a server because huge domlogs just take too long to process. A cheap server these days could easily cause the domlogs to grow so large that they crash the server in just minutes or a few hours, even before the stats run gets to them. And imagine the stats run causes too much load and isn't able to finish before the next stats run, or before the domlogs grow too large.
Just a little background, no my server is not some giant machine. We are a tiny company that just runs normal PHP websites. That is all, nothing fancy. We have one VPS with 4 CPU cores. Yes our server gets millions of Apache hits in a few hours which cause the domlogs to fill up in less than one day, crashing the server every time. I don't see anything special about our configuration. In my opinion every single cPanel server would crash if they would ever get any serious traffic due to the domlogs getting to big. Its just the nature of technology these days, servers are ever more capable, and I hope that cPanel will make domlog accommodations for the higher capabilities of today's machines.
Thank you for your kind help!
Dear friends, I think the ability to disable domlogs at any level would be an outstanding idea.
Given today's (and yesterday's) ever faster servers, its really easy for a domlog to grow too large in just a few hours. This will cause any server to crash, probably at a completely unexpected time, whenever the domlog gets too big. This absent feature of cPanel has caused us countless hours of downtime, lost revenues, and way too many hours of our time, our technician's time, and cPanel support's time. Its almost absurd how such a small missing feature has caused us so many problems. We have had this exact cPanel domglog issue for years now, so think that I know what I'm talking about.
Secondly, the workaround the cPanel currently suggests, but commenting out all instances of CustomLog in local copies of templates, is a flawed solution. The idea of making local templates in itself is a poor idea in my experience, because as soon as cPanel is updated the default templates will change, but any modified server will be left with potentially obsolete templates. I had just that problem recently. I modified my templates just a few months ago, but suddenly after updating to cPanel 60 my already out of date templates were causing Apache to crash when I wanted to change my PHP configuration.
Thirdly, yes I know domlogs are processed, and rotated or deleted regularly. But imagine high traffic, processing statistics can overload a server because huge domlogs just take too long to process. A cheap server these days could easily cause the domlogs to grow so large that they crash the server in just minutes or a few hours, even before the stats run gets to them. And imagine the stats run causes too much load and isn't able to finish before the next stats run, or before the domlogs grow too large.
Just a little background, no my server is not some giant machine. We are a tiny company that just runs normal PHP websites. That is all, nothing fancy. We have one VPS with 4 CPU cores. Yes our server gets millions of Apache hits in a few hours which cause the domlogs to fill up in less than one day, crashing the server every time. I don't see anything special about our configuration. In my opinion every single cPanel server would crash if they would ever get any serious traffic due to the domlogs getting to big. Its just the nature of technology these days, servers are ever more capable, and I hope that cPanel will make domlog accommodations for the higher capabilities of today's machines.
Thank you for your kind help!
Domlogs "nolog" option should be optionally disabled at users level. It's a must! We have a high visiting site that generates ("dummy") logs quite fast.
Domlogs "nolog" option should be optionally disabled at users level. It's a must! We have a high visiting site that generates ("dummy") logs quite fast.
Yes! Yes! Yes! I turn off domlogs for one user by hand-commenting-it-out via httpd.conf because that's what the server hosts advised. This lasts less than two days before it is replaced and within 3-4 days of it coming back on, the server lags massively so I am reminded to go and do it again. It's essentially a chat-site run on php/AJAX. My site has suffered for years from this.
It doesn't make sense that anything, like logging, should be compulsory anyway, but irrespective of that, it is essential that it can be safely turned-off!
(pretty pleeease with cherries on top)
Yes! Yes! Yes! I turn off domlogs for one user by hand-commenting-it-out via httpd.conf because that's what the server hosts advised. This lasts less than two days before it is replaced and within 3-4 days of it coming back on, the server lags massively so I am reminded to go and do it again. It's essentially a chat-site run on php/AJAX. My site has suffered for years from this.
It doesn't make sense that anything, like logging, should be compulsory anyway, but irrespective of that, it is essential that it can be safely turned-off!
(pretty pleeease with cherries on top)
We really need this feature! It will really speed up servers and lower load. Good for the environment!
The current cPanel-recommended method of creating .local files for each Apache configuration file, and commenting out each instance of "CustomLog" is a stability and security risk because it leaves many servers with outdated configuration files after cPanel updates.
Additionally many high load servers with logging disabled through straightforward modification of the default templates might ** crash ** from too much load after cPanel's automatic Apache configuration file rewrites suddenly and unexpectedly turns on logging. This is because for many servers the logging itself might cause more load that actual page serving, and the servers simply can not handle log processing due to massive logs. Also for many high load servers the log files will become larger than the maximum possible log file size, even if log files are processed every hour, causing a fatal Apache crash. And of course these kinds of crashes seem to happen at 3 AM. :)
We really need this feature! It will really speed up servers and lower load. Good for the environment!
The current cPanel-recommended method of creating .local files for each Apache configuration file, and commenting out each instance of "CustomLog" is a stability and security risk because it leaves many servers with outdated configuration files after cPanel updates.
Additionally many high load servers with logging disabled through straightforward modification of the default templates might ** crash ** from too much load after cPanel's automatic Apache configuration file rewrites suddenly and unexpectedly turns on logging. This is because for many servers the logging itself might cause more load that actual page serving, and the servers simply can not handle log processing due to massive logs. Also for many high load servers the log files will become larger than the maximum possible log file size, even if log files are processed every hour, causing a fatal Apache crash. And of course these kinds of crashes seem to happen at 3 AM. :)
Replies have been locked on this page!