Monthly stats not resetted

[prale]

We noticed that yesterdays bandwith usage was higher as normal.
(see attachment for the detailed view from a user)

The reason seems to be that the stats where not updated for 1week .
And the biggest problem is that the stats are not resetted on 1juli (for all of our customers on this server) so without any quick action some users get suspended for over-usage.

Any advice how to fix this is welcome, thanks.

[edit]
Hmmz, Google search works better then forum search, sorry for this post it's already fixed with:
echo "action=reset&value=all" >> /usr/local/directadmin/data/task.queue
[/edit]

 

[jackc]

yah, no idea why but we do see this happen from time to time. it would be nice if DA can do a double-check to make sure resetting bandwidth.

 

[LawsHosting]

Make sure the DA cron is running as it should be.

 

[DirectAdmin Support]

Hello,

We've been adding more and more logging to the reset to try and nail down where it's being skipped. I've never been able to duplicate it for any system I've checked.

For anyone who didn't get their reset, to avoid losing all of the current months data, use the "cleanreset" instead of the full "reset".
http://www.directadmin.com/features.php?id=618

If you've got 1.36.0, the reset log entries should be looking something like:

2010:07:11-19:10:37: Reset all command Received
2010:07:11-19:10:37: Reset admin type:3
2010:07:11-19:10:37: Reset admin done
2010:07:11-19:10:37: Reset user1 type:1
2010:07:11-19:10:37: Reset user1 done
2010:07:11-19:10:37: Reset user2 type:1
2010:07:11-19:10:37: Reset user2 done
2010:07:11-19:10:37: Reset reseller1 type:2
2010:07:11-19:10:37: Reset reseller1 done
2010:07:11-19:10:37: Reset user3 type:1
2010:07:11-19:10:37: Reset user3 done
etc...
2010:07:11-19:10:37: Reset all command : done

The "type" flags are 1 for User, 2 for Reseller, 3 for Admin.

The function reads the /usr/local/directadmin/data/users directory for each username, and resets based on that. No list files are used to get the list of Users. But the first thing we'd be looking for is the reset entry in the /var/log/cron, and the "Reset all command Received" in the /var/log/directadmin/system.log.

John