Bandwidth Tally and Shared IP Question/Problem

[Nekoman]

Hello,

A little background info before I go into the problem/question I recently Installed WHMCS Billing and management system to control clients on a new server. Before that I had AWBS billing and management system. I also updated Directadmin to the newest version 1.31.2 at about the same time so im not sure if its an update problem or the previous software so im giving some extra info just in case. I will move one of my hosted domains to a manually created directadmin account to see if the problem still exists. I just thought I would post and see if anyone could help me out in the mean time.

First Problem - Users are created correctly with the correct package that was set up, but their bandwidth is not tallied at all. The disk usage data is correctly tallied though.

I get the following error message when you try to view bandwidth data


Error while breaking down the bandwidth.tally file

Details

Unable to read ./data/users/(user name - edited out)/bandwidth.tally : No such file or directory

I checked the users data directory and sure enough there is no bandwidth.tally or bandwidth.tally.cache

It has been over 5 days since the accounts were created and the bandwidth is set to tally every night at midnight

My other accounts which I created Directly within Directadmin have a bandwidth tally file and work perfectly. This was pre-directadmin update version 1.31.2 when I manually created the accounts.


Second Question - Shared IP
how do I get new sign ups to use the ip I designated for Shared use?
there is no option to set the shared ip in the reseller packages that I could find. I can manually set ip usage per account if I edit them directly, but that would be time consuming.

I did set the ip to shared using the ip management function under admin.

when a new account is created it defaults to the main server ip for some reason instead of the designated shared ip address.


Any info or help regarding the above issues would be greatly appreciated and thanks in advance.

 

[MortyDot]

Same problem here,

When I create a new account it seems that there is no bandwidth.tally created,
Error:

Error while breaking down the bandwidth.tally file

Details

Unable to read ./data/users/( User name )/bandwidth.tally : No such file or directory

To be honest, whe I use "cd ./data/users" the patch does not exist!
It seems to me that DirectAdmin is looking on the wrong place fore the bandwidth.tally file, But I don't know where it normally is located or where to change the default path.

This problem is something of the last month and was not there a month ago. (Only new users show this problem)

Can anyone help?
Kinds Regards
Sven Lohuis

 

[nobaloney]

Bandwidth tally files are located in this path:

/usr/local/directadmin/data/users

Whenever using a path that starts with anything other than a slash, be sure you're in the right directory before you start.

The bandwidth.tally file may not exist until after the first 24 hours after the site is created. I'm not sure, and I didn't check.

Jeff

 

[MortyDot]

The bandwidth.tally file may not exist until after the first 24 hours after the site is created. I'm not sure, and I didn't check.

Jeff

You are completely right, the results are there after a few hours, that it whas a bug, Good to know!

Thanks!
Kinds regards

 

[goody]

Bandwidth tally files are located in this path:

/usr/local/directadmin/data/users

Whenever using a path that starts with anything other than a slash, be sure you're in the right directory before you start.

The bandwidth.tally file may not exist until after the first 24 hours after the site is created. I'm not sure, and I didn't check.

Jeff

I have waited 24 hours after the user created,and there no bandwidth infomation still.
Also there are the problem

Error while breaking down the bandwidth.tally file

Unable to read ./data/users/woody/bandwidth.tally : No such file or directory


I don't know where is the wrong.

 

[nobaloney]

Start by making sure your cron daemon is running:

$ ps waux | grep crond

Then try running the DirectAdmin set_permission.sh script to see if that enables the write (wait until the next morning).

Perhaps someone else with some ideas will respond to this thread.

Otherwise if you don't have the skills required to troubleshoot you might want to contact DirectAdmin Support if you bought DirectAdmin from them. Note that permanent licenses are not entitled to continuing support.

If you get your license with a dedicated server rental than your hosting company should be able to help you. Your last step would be to hire a third-party support company (see my siglines below) but we should be the last resort; we're not cheap.

Jeff

 

[goody]

thanks very much
I deal it now