Date:  Wed, 20 Sep 2006 10:47:48 -0600
From:  "Rodrigo Ordonez Licona" <rodrigo (at mark) xnet.com.mx>
Subject:  [coba-e:07124] Re: Weird logs
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARDhjVlX2aEuqbKE5moo4BsKAAAAQAAAAw/8x+Oy1sEOPIhdqROymQQEAAAAA (at mark) xnet.com.mx>
In-Reply-To:  <Pine.LNX.4.63.0609201037410.8849 (at mark) mail.nuonce.net>
X-Mail-Count: 07124

Hi we switched everything back to 

Defaults on /tmp, edited with pico editor
Remove the ./tmp option on crontab

Executed 
/etc/init.d/crond restart
/etc/init.d/httpd restart 

Voila Records appearing on 
/var/log/httpd/access_log

Will wait for Brians Update


In our case the problem seems to be on apache logs, The have 0 bytes,
Webalizer an awstats RUN, but they have 0 records to process.

Somebody had this problem too, 

Phase 1 : First bypass old records, searching new record...
Direct access after last parsed record (after line 59363) Jumped lines in
file: 59363  Found 59363 already parsed records.
Parsed lines in file: 0
 Found 0 dropped records,
 Found 0 corrupted records,
 Found 0 old records,
 Found 0 new qualified records.



 

-----Original Message-----
From: Brian N. Smith [mailto:brian (at mark) nuonce.net] 
Sent: MiñÓcoles, 20 de Septiembre de 2006 08:38 a.m.
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:07116] Re: Weird logs

The one thing I had forgot to mention, the "TMPDIR" variable has been
changed to "force" it to use a new temp directory.  That is what all of the
posts I had read said to do.  Still, no dice?

--
Brian N. Smith
NuOnce Networks, Inc.
=-=-=-=-=-=-=-=-=-=-=
http://www.nuonce.net
P: (321) 574-5227
F: (321) 574-0554
E: brian (at mark) nuonce.net