In the mean time, Lance you provided a work around that I did not quite catch. You said something about changing the proftpd file so that it didn't split the logs. Can I simply just comment out one of the lines?
/var/log/xferlog {
missingok
prerotate
/usr/local/sbin/ftplog2commonlog < /var/log/xferlog | \
/usr/local/sbin/split_logs ftp
endscript
daily
# ftpd doesn't handle SIGHUP properly
nocompress
}-Rashid
At 19:25 8/28/2003, you wrote:
Thanks for the info Lance,
I confirm that it is while it analyzes ftp logs for me too. Can you tell me what calls the parseReport.pl?
Just in case it might help someone else who is having this problem some day, I fill in the details of my story.
My corrupt file database was a false trail. I deleted the offending directories and redid a updatedb and all looks fine now but the server still crashes.
This morning I sat in front of my terminal session and watched the processes with "top". I guesse the most important information is not that it uses 98% cpu before the crash, but rather that it had used 75 minutes of cpu time.
This moring I tried killing the process with "kill 66253" where 66253 is the process number I found in "top" but it kept coming back with a new process number. Then I realized that it was running as many times as there are logs to be analyzed (by using "ps -66253" for example.) So I waited until it got stuck for at least 10 minutes on the same process and yes, it is while processing ftp logs.
I guesse that it is on the mostRequested.html that it is getting stuck based on dates and times. first crash dates to august 12th. [root ftp]# ls -l total 13 -rw-r--r-- 1 root root 6380 Aug 12 07:19 browser.html -rw-r--r-- 1 root root 0 Aug 29 05:48 mostRequested.html -rw-r--r-- 1 root root 1657 Aug 12 07:19 periodic.html -rwxr-xr-x 1 root root 3487 Aug 29 05:48 webUsage.html
So forthe moment I just kill the process before eating breakfast but, I will keep trying to understand.
Have fun ! David
---------- Original Message ----------- From: "Lance Rushing" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thu, 28 Aug 2003 10:45:35 -0700 Subject: Re: [cobalt-developers] parseReport.pl crash
> I've had problems with parseReport choking when it > analyzes ftp logs I just moved the proftd file out > of /etc/logrotate.d and replaced with one that > doesn't split the logs up, so parseReport.pl never > sees it. > > are you sure it is /usr/admserv/cgi- bin/.cobalt/webUsage/parseReport.pl > causes the crash? (Have you run it by hand). > > If it is, and you can do a little perl hacking > and see what line/command is actually causing the > crash. > > ----- Original Message ----- > From: "ds" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, August 26, 2003 00:37 > Subject: [cobalt-developers] parseReport.pl crash > > > Good morning all, > > > > I have a Raq 4 that is crashing each morning at 8 am when > > running > > > > /usr/admserv/cgi-bin/.cobalt/webUsage/parseReport.pl > > > > I have searched the archives and found that this is > > apparently a script used during the log rotation and or for > > the gui stats in the GUI admin interface, but I found no > > answers about what needs to be done to fix it. > > > > Another strange thing is that just before it crashed and I > > saw that this process was using 99% cpu I did > > "locate parseReport.pl" and got > > /home/sites/site11/users/espaceusr/admserv/cgi- > > bin/.cobalt/webUsage/parseReport.pl > > > > as if the file were located in site11. > > But ofcourse it is not located in site 11. > > > > The server froze and I had to do a hardware reboot. > > > > Last thing is that after it restarted I did an updatedb (I > > guesse this updates the file database) then I did a > > "locate web.log" > > and I got this > > > > ... > > /home/sites/site9/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backupite13/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite16/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite17/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite17/logs/web.log.1.gz > > /home/sites/site11/users/espace- > > sem4/backusite18/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite19/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite19/logs/web.log.1.gz > > /home/sites/site11/users/espace- > > sem4/backusite20/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite22/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite23/logs/web.log > > /home/sites/site11/users/espace- > > sem4/backusite23/logs/web.log.1.gz > > etc... > > > > Again as if there were web.log files in site 11 but there > > are none. > > > > Does anyone have suggestions > > > > Thanks in advance > > > > > > _______________________________________________ > > cobalt-developers mailing list > > [EMAIL PROTECTED] > > http://list.cobalt.com/mailman/listinfo/cobalt- developers > > > > _______________________________________________ > cobalt-developers mailing list > [EMAIL PROTECTED] > http://list.cobalt.com/mailman/listinfo/cobalt-developers ------- End of Original Message -------
_______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
***************************************************************** MuntadaNet Web Hosting and Web Design Services http://www.muntada.com
Sales - [EMAIL PROTECTED] Support - [EMAIL PROTECTED] Billing - [EMAIL PROTECTED]
Hawaii - 808-689-6092 ext 03 Toll Free - (888) 565-7327 ext 03 Fax - (707) 581-1722 *****************************************************************
_______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
