How to force PBA-S to update statistics from Plesk server immediately

Created:

2016-11-16 12:38:49 UTC

Modified:

2017-08-16 15:54:04 UTC

0

Was this article helpful?


Have more questions?

Submit a request

How to force PBA-S to update statistics from Plesk server immediately

Applicable to:

  • Plesk 11.x for Linux

Symptoms

In the default installation PBA-S 4.3 is performing update of statistics for every single Plesk server registered in PBA-S once a 12 hours . This period of time is hardcoded and cannot be changed.

You may run periodic task 'Update Plesk nodes stats info' in hope that it will update all nodes immediately, however the task will check when every node was updated last time and will not update a Plesk node if less than 12 hours passed since the last update. Such behavior allows to decrease load on both PBA-S and Plesk servers.

Resolution

To force PBA-S to update statistics for a specific Plesk server you may set the field 'pnode_curr_stat.timestamp' for the needed Plesk server in PBA-S database to 0 and run the periodic task 'Update Plesk nodes stats info' .

This will make PBA-S to update statistics for Plesk server immediately.

You may use the action below to achieve the goal:

  • Log into PBA-S server by SSH as root
  • Connect to PBA-S database:

    ~# hspc-sql
  • Update the table 'pnode_curr_stat' for the needed Plesk server:

    mysql> BEGIN; UPDATE pnode_curr_stat SET timestamp=0 WHERE hw_id=$NODE_ID;
    mysql> COMMIT;
  • Run the periodic task 'Update Plesk nodes stats info' in PBA-S PCC at

    Top > Configuration Director > Logging and Errors > Action Log

Replace $NODE_ID with actual ID of Plesk server which you may find in PBA-S PCC at

    Top > Service Director > Plesk Manager > Nodes
Have more questions? Submit a request
Please sign in to leave a comment.