[Solved] Tommy HTTP Access Logs Stopped

[Computer Nerd Kev]

Hello,

 

The access logging for the domains on my account stopped on the 11th.

 

I think this happened once before after Tommy's /var became full.

[Krydos]

Please post the following information:

• Your cPanel username
• Your main domain

[Flaze]

1. cnk

2. http://computernerdkev.heliohost.org

 

Don't worry about how I got his cPanel username. Randomly guessed it based off his forum username.

[Krydos]

You're right, Tommy is pretty behind on processing logs. Probably because the load has been so high lately. I manually ran your stats, and did a few things that might unstick the processing of everyone else's logs.

[Computer Nerd Kev]

Thanks, the log progress hadn't moved much for at least a week. It has jumped forwards now and hopefully it will keep on marching.

[Computer Nerd Kev]

The logs have stopped again - they've been at 21st of May for a few days now, possibly since my last post.

[Krydos]

They actually didn't stop; they're just that far behind on everyone else. The way they work is they process whoever is the furthest behind next. I ran logs on your account manually. That puts your account at the bottom of the list to have logs run next, and the server was trying to get caught up on the thousands of other accounts first before running logs on your account again. I once again ran logs manually on your account.

[Sn1F3rt]

They actually didn't stop; they're just that far behind on everyone else. The way they work is they process whoever is the furthest behind next. I ran logs on your account manually. That puts your account at the bottom of the list to have logs run next, and the server was trying to get caught up on the thousands of other accounts first before running logs on your account again. I once again ran logs manually on your account.

Krydos check your PM please.

[Computer Nerd Kev]

They actually didn't stop; they're just that far behind on everyone else. The way they work is they process whoever is the furthest behind next. I ran logs on your account manually. That puts your account at the bottom of the list to have logs run next, and the server was trying to get caught up on the thousands of other accounts first before running logs on your account again. I once again ran logs manually on your account.

 

Ah, thanks. I'll be more patient with it for now then.