Hundreds of Ajax access logs for 3 hours run up CPU

Hi,

Was a backup running at the time?
If so, please could you send us a copy of that backup log?

The contents will be too long to post here directly, but you can use an extgernal service such as Pastebin and post the link here.

Hi @dnutbourne
No, no backup running at the time .

Here is the link:
https://pastebin.com/5DEy7vef

Sorry, I’m not sure if this logs is what you need, if there is any information I can provide, please let me know.

Thank You.

Hi,

Were any backups run on the 18th (or morning of the 19th depending on your timezone)?
The ajax calls mainly appear to be regarding the check the UpdraftPlus settings page makes when tracking an ongoing backup (to update the logs and status).

Has running a backup caused a similar issue in the past, or has the issue occurred again since the other day?

Hi @dnutbourne
Thanks For your reply.

In the logs from 18/Aug/2020:19:32:32 +00 to 18/Aug/2020:21:09:52 +00 , I run backup manually on 21:26 +00,and it finished in 1-2 min.
But the logs seems began from 19:32 , and ended on 21:09 , I did not backup during that period.

Here is complete log again which occured today:
https://pastebin.com/D2ZAviPP

The Ajax occurred on 2020/08/20 ,from 20:28:18 +0 to 21:47:01 +0
But my backup run manually from 20:28:18 +0, and finished in 1-2 min as always.
I have no idea why the logs run until 21:47:01 +0.

In the past, when backup run, it did consume CPU, but not take so long time and so many logs.

• This reply was modified 4 years, 7 months ago by 温唯.
• This reply was modified 4 years, 7 months ago by 温唯.

Hi,

Apologies for the delay.

I have checked with our developers, and the backup status is polled whenever the UpdraftPlus settings page is open on the Backup/Restore or Clone/Migrate tabs, so it is likely that he settings page was left open for the 3 hours these messages are logged.

Does CPU uasage spike if you open the UpdraftPlus settings Backup/Restore tab and leave it in the browser for 10-20 minutes?

Hi @dnutbourne

Thanks for your reply and all your work.

To be correct, as of now 2020/8/24 21:57:37 +0000, this problem has only occurred on 8/18 and 08/20.
Even though I continued to manually backup every day, this did not happen on other days.

In addition, in response to your question, I often leave Backup/Restore tab in the browser for several hours, especially after each manual backup is over , and CPU usage did not spike due to this.

I don’t know why there were so many AJAX in those two days.

> I often leave Backup/Restore tab in the browser for several hours, especially after each manual backup is over

It’s often possible to detect that a tab is *open* but not *active*. Polling is reduced or suppressed when not active (since there’s no user able to actually see any results of it).

David