whmcs and directadmin

[sahostking]

I have a server with around 1200 accounts on it. However whenever I terminate via whmcs an account it seems to browser through all accounts before terminating?

 

auth.authenticated

auth.authenticated

User::deny_override:/CMD_API_SHOW_USER_CONFIG: call_level=2, depth1: aborting due to do depth

User::deny_override:/CMD_API_SHOW_USER_CONFIG: call_level=1, depth2: aborting due to do depth

Command::doCommand(/CMD_API_SHOW_USER_CONFIG)

User::deny_override:/CMD_API_SHOW_USER_CONFIG: call_level=2, depth1: aborting due to do depth

User::deny_override:/CMD_API_SHOW_USER_CONFIG: call_level=1, depth2: aborting due to do depth

Command::doCommand(/CMD_API_SHOW_USER_CONFIG)

Command::doCommand(/CMD_API_SHOW_USER_CONFIG) : finished

Command::run: finished /CMD_API_SHOW_USER_CONFIG

Command::doCommand(/CMD_API_SHOW_USER_CONFIG) : finished

Command::run: finished /CMD_API_SHOW_USER_CONFIG

/CMD_API_SHOW_USER_CONFIG

 

 

Now sure why its strange and it takes forever to terminate an account due to this. Any ideas? I assume its a whmcs issue because terminating directly from DA server seems fine.

Edited May 24 by sahostking

[WHMCS John]

Hi @sakamhosting,

The cmd_api_show_user_config API command isn't part of the DirectAdmin's _terminate function, but it is used for collecting Usage Billing metrics and also when importing accounts from a DirectAdmin server using the Sync tool.

The updating of Usage Billing metrics sounds like the most likely case here, as the system will check the Usage Billing when processing an account cancellation to invoice any unbilled usage.

 

1. Do you have Metric Billing configured for the product in question?

2. Is the service in question a reseller or shared hosting account?

3. How is the service being terminated via clicking the Module Command button, or by the system processing a Cancellation Request?

4. Please share the module debug log entries to show the details of the request being made at the time.
In order to see the commands being sent/received between WHMCS and the module, the Configuration > System Log >  Module Debug Log tool can be used.
Please enable it, reproduce the problem, disable it again and then copy the data into this ticket reply for us to review.

For more information on using the Module Debug Log, please see: https://docs.whmcs.com/troubleshooting/logs-in-whmcs/

Note: Please remove any sensitive data before posting it here publicly.