You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! First of all, I want to express my appreciation for your add-on – it's fantastic. However, I've encountered a problem. When the add-on performs CRON operations, it leads to a timeout on the web server. This issue becomes apparent particularly because I have around 1.1K server threads. Once a timeout occurs, it prevents the remaining unprocessed queries from updating server information.
Steps to Reproduce
Allow the CRON tasks to run automatically or trigger them manually through the Admin Control Panel (ACP).
Observe the web server behavior, particularly focusing on the occurrence of a timeout during the CRON task execution.
Expected Behavior
The expected behavior is that the add-on completes its CRON tasks without causing the web server to timeout, ensuring all server queries are processed and server information is updated accordingly.
Actual Behavior
The web server times out during the execution of CRON tasks by the add-on, leading to incomplete query processing and outdated server information.
The text was updated successfully, but these errors were encountered:
I understand you, but I didn't think it was possible to have such an active server threads.
You can temporarily change your server or php settings. Currently, this plugin is actively used in the mc-tr.com forum, but we did not encounter any timeout problems. If you are stuck with the API limit, you should contact the API owner.
I may bring a feature for this problem in the future.
Environment
Issue
Hello! First of all, I want to express my appreciation for your add-on – it's fantastic. However, I've encountered a problem. When the add-on performs CRON operations, it leads to a timeout on the web server. This issue becomes apparent particularly because I have around 1.1K server threads. Once a timeout occurs, it prevents the remaining unprocessed queries from updating server information.
Steps to Reproduce
Expected Behavior
The expected behavior is that the add-on completes its CRON tasks without causing the web server to timeout, ensuring all server queries are processed and server information is updated accordingly.
Actual Behavior
The web server times out during the execution of CRON tasks by the add-on, leading to incomplete query processing and outdated server information.
The text was updated successfully, but these errors were encountered: