p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

HUGOMORE42

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`

*Stop Apache*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

HUGOMORE42

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

HUGOMORE42

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`

*Stop Apache*

``

*Rotate the logs manually*

```p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

HUGOMORE42

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

HUGOMORE42

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`

*Stop Apache*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

HUGOMORE42

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.

HUGOMORE42

To fix this problem, you need to perform the following steps:

*Split the logs*

Run the command,

`

*Stop Apache*

``

*Rotate the logs manually*


\*Start Apache\*
  
````p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

`` 

\*Rotate the logs manually\*
  
```p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

`` 

\*Rotate the logs manually\*
  

*Start Apache*


\*Run webalizer\*
  
`````p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

`` 

\*Rotate the logs manually\*
  
```p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

`` 

\*Rotate the logs manually\*
  
``` 

\*Start Apache\*
  
````p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

`` 

\*Rotate the logs manually\*
  
```p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

``p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
`p. Stats on a Cobalt RAQ often stop updating. This is most likely because the Apache log files have grown too large, probably in hundreds of MBs. Under such conditions, the logs don’t rotate cleanly through cron, and obviously webalizer stops working.
  
HUGOMORE42


  
To fix this problem, you need to perform the following steps:

\*Split the logs\*

Run the command,
  
` 

\*Stop Apache\*

`` 

\*Rotate the logs manually\*
  
``` 

\*Start Apache\*
  

*Run webalizer*

`````

You might probably want to write this as a script and run it through cron once every two days or so.