This I noticed after updating the cpanel/webhost manager to v 11.x
There are not 2 copies of the access log, both updating live, the first one which was always there is at
/usr/local/apache/domlogs/account.com
and the second one at:
/usr/local/apache/domlogs/account/account.com
Does anyone know why there is a need to keep and update 2 log files and how I can go back 1 access log?
I have a problem with Fedora linux server. I have two copies of PHP installed.
Now I have problems with modules, which are compiling with new version:
Quote:
[20-Nov-2007 03:27:30] PHP Warning: PHP Startup: json: Unable to initialize module
Module compiled with module API=20060613, debug=0, thread-safety=0
PHP compiled with module API=20050922, debug=0, thread-safety=0
These options need to match
in Unknown on line 0
I've already removed all paths from bash and set only path to new version:
path=/usr/local/bin
Old version is in /usr/bin/
When I do phpinfo() after this change, I get old version info...
I wonder what should I do? Will removing both PHP and installing newest version will be a good idea or I can get more trouble?
I want to close this /usr/local/apache/domlogs/ logs for all domain how can I do?
I 'just ordered a dedi server; they rung me to confirm the order and told me my server would be ready in few hours, but later asked me send copies of my debit card and passport which I refused to do as i never did this before, especially, here, in the UK
Is this common in th US?
to delete and reset the domlogs files from Apache server, as they have become too large, but I want to keep a record of the past few years website stats.
I could download the domlogs files (they look like MS-DOS applications) but once I have I am not sure how to read them, is there some off server application that could open these files? I currently view stats in awstats from cPanel, but the size of the files is causing problems with updating now.
The only thing I can think of doing is taking screenshots of the relevant stats that I want to keep, before deleting the files, but was thinking there must be a better solution than that.
i have a little issue with the domlogs folder.
I should empty this files but i don't know if it is possible to do without reboot Apache.
a) how can i setup logrotate to rotate domlogs?
And if it is possible:
b) how can i setup logrotate to rotate domlogs without restart apache?
I have already setup whm-> tweak settings to delete old domain's access logs after stats run and the whm is setup to generate statistics every 20 hours.
But every day the site is slowly because the domlogs are too big.
I've been trying to get the domlogs to rotate and be held for 7 days but have been unsuccessful. Someone came up with this code a while back but it goes a little funky and creates backups of backups domain.com.1.gz.1.gz.1.gz etc. Does anyone know whats wrong with this rotate script?
Code:
/usr/local/apache/domlogs/* {
daily
compress
missingok
rotate 7
sharedscripts
postrotate
/etc/init.d/httpd restart > /dev/null
endscript
}
thewird
Is there any way to rotate apache domlog files but only keep them for 7 days?
View 11 Replies View Relatedso after successfully installing and testing litespeed last night along on alternate port 1080 on my cpanel setup, I try to look at my cpanel's awstats this morning and:
Error: Couldn't open server log file "/usr/local/apache/domlogs/example.net" : Permission denied
(awstats has worked fine for 5 weeks now)
Googling for this shows other people with similar problem in the past but unfortunately no answers
I tried chmod -R 644 /usr/local/apache/domlogs
and looks like the owners are still correct
I'm at a loss and really screwed if I can't easily fix soon... any ideas?
(as a side note, litespeed has stopped working properly too but I've killed it for now)