Something Wrong With Webalizer?

[netsnets]

Hey guys, I use webalizer on my site. All of a sudden, it stopped recording traffic yesterday. In the latest visitors, I just get "googlebot" spiders coming from a 64.68.80.. address over and over? What is going on? Is something wrong on my end, there end?

Anyone ever have this happen to them? I've used webalizer for 3 years or so, and never had anything like this happen. Any ideas?

Here's the results of the latest visitors..

Host: 64.68.80.169 Url: / Http Code : 200
Date: May 30 21:08:19 Http Version: HTTP/1.0" Size in Bytes: 54905
Referer: - Agent: Googlebot/2.1 (+http://www.googlebot.com/bot.html)

Host: 64.68.80.4 Url: / Http Code : 200
Date: May 30 20:37:53 Http Version: HTTP/1.0" Size in Bytes: 54905
Referer: - Agent: Googlebot/2.1 (+http://www.googlebot.com/bot.html)

Host: 64.68.80.185 Url: / Http Code : 200
Date: May 30 20:22:51 Http Version: HTTP/1.0" Size in Bytes: 54905
Referer: - Agent: Googlebot/2.1 (+http://www.googlebot.com/bot.html)

Host: 64.68.80.21 Url: / Http Code : 200
Date: May 30 19:21:58 Http Version: HTTP/1.0" Size in Bytes: 54905
Referer: - Agent: Googlebot/2.1 (+http://www.googlebot.com/bot.html)

Host: 64.68.86.22 Url: / Http Code : 200
Date: May 30 19:06:45 Http Version: HTTP/1.0" Size in Bytes: 54905
Referer: - Agent: Googlebot/2.1 (+http://www.googlebot.com/bot.html)

etc..

[incywincy]

this all looks pretty normal, they are all different incarnations of googlebot on the same c-block requesting your index page. sometimes you can't make rhyme nor reason of the bots behaviour. it may be worth emailing google if this is happening continually.

have you checked to make sure that the process that writes to your access_log (usually the apache user) has sufficient disk quota remaining?

[netsnets]

Thanks for the quick response. I'm not really sure how to go about this though:
<<have you checked to make sure that the process that writes to your access_log (usually the apache user) has sufficient disk quota remaining?>>

A few days ago, the hosting company I used changed my site to a different server. Do you think this could be a reason for it? Maybe the log being recorded is only from the old server and is not recognizing the new