In effect this results in significant drop of CPU/RAM resources consumed by Apache, which leaves your server with more available resources for other tasks. In short if you have performance issue with your c Panel server engintron is a good solution.
And the good news is that once you set up engintron is there no need for further maintenance, you are set to go just like that.
You may need to use and option called "create" to create a new log file if you do not have a postrotate script in the rotate configuration file that you are creating. Some softwares or services may not generate a new log file if one does not exist.
Hello, I have a cpanel server in which the /usr partition is 95% full.
/usr/bin/python import sys, os raw Data = sys.stdin.readlines() hookdata = eval(raw Data.replace(':null', ': None')) data = hookdata['data'] username = data['user'] if not exists('/home/%s/tmp/awstats' % username): os.makedirs('/home/%s/tmp/awstats' % username) f = open('/home/%s/tmp/awstats/include' % username, 'w') f.write('Log Format="%host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot %extra1"\n') f.write('Extra Section Name1="Time to serve requests (seconds)"\n') f.write('Extra Section Code Filter1=""\n') f.write('Extra Section First Column Title1="Number of seconds to serve the request"\n') f.write('Extra Section First Column Values1="extra1,(.*)"\n') f.write('Extra Section Stat Types1="H"\n') f.write('Extra Tracked Rows Limit=100000\n') f.close() if exists('/home/%s/tmp/awstats' % username): os.system('chown -R %s:%s /home/%s/tmp/awstats' % (username, username, username)) The code reads stdin, replaces :null with : None.
Now you guys might be wondering how to find a permanent fix for your high traffic server. Some of you might even think that we should quit all Favourite c Panel and move to other control panels that support other web servers. Nginx acts as a web traffic proxy, directly serving all static assets like CSS, JS, images etc by default, instead of Apache. instead of your actual web server, thus lowering the load and RAM usage.
The other major usage is in the /usr/local/cpanel/whostmgr/docroot/cgi/fantastico directory which I have mentioned earlier. I don't think it keeps the logs, but everything else, as far as I recall, remains in-tact in the event a rollback is needed.[email protected] [/usr]# du -h --max-depth=1 /usr 12K /usr/etc 2.8G /usr/local 262M /usr/bin 34M /usr/include 940M /usr/share 76K /usr/doc 24K /usr/X11R6 47M /usr/sbin 16K /usr/lost found 21M /usr/libexec 608M /usr/lib 91M /usr/src 8.0K /usr/games 116K /usr/man 1.6M /usr/kerberos 4.8G /usr The above shows 4.8 GB is the usage in /usr directory. Check for apache logs like error_log, access_log , suexec_log in /usr/local/apache/logs .
Scenario: We all know that c Panel is the leading hosting control panel worldwide.
Unless it is in some backup directory that is the fanstatico install files that are used when a client installs an app.
The apache dir is about 1Gb, that is probably error_logs and domlogs. c Panel check the logs directories and possibly for core dump files (core.xx) The cpanel-rollback is just so you can go back to an older version, most don't need it.