Current time: 12-04-2020, 01:04 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
"Sorry, that test location already has too many tests pending" - but not running any
04-13-2017, 09:29 PM (This post was last modified: 04-13-2017 09:38 PM by mangoo.)
Post: #1
"Sorry, that test location already has too many tests pending" - but not running any
I've upgraded webpagetest and wptagent with today's versions from gihub (running them both on Ubuntu 16.04).

I think I didn't set up everything properly, as when I'm trying to start a new test, web interface just displays "Sorry, that test location already has too many tests pending. Pleasy try again later.".

There aren't any tests running, so that's a surprise.


wptagent is polling /work/getwork.php and is receiving HTTP 200.

/var/www/webpagetest/logs/ does not contain any logs (does webpagetest write any logs anywhere?).

Apache error log does not log any errors.

How can I debug this?
Find all posts by this user
Quote this message in a reply
04-14-2017, 03:05 AM
Post: #2
RE: "Sorry, that test location already has too many tests pending" - but not...
I am also facing similar issue after upgrading the server to latest version (3.0.0.348) .
My Agents are on windows 7.

After upgrading my old Agents (I had 6 agents earlier) are running. I added 2 more agents. Everything Ok Only I am not seeing the CPU Utilization for the new Agents in "http://URL/getTesters.php"

When I am trying run a test it is giving the below message.
"Sorry, that test location already has too many tests pending. Pleasy try again later."
Find all posts by this user
Quote this message in a reply
10-09-2020, 04:54 AM (This post was last modified: 10-09-2020 05:26 AM by dimension85.)
Post: #3
RE: "Sorry, that test location already has too many tests pending" - but not running any
I have had the same issue arise, but changed nothing. Tests were running on pre-determined schedule and now they the server just returns this error. The problem is persistent after a reboot so am at a loss as to what has happened.

I have changed nothing Basically my private instance is now down and some real help as to how to fix this would be appreciated

Update after some investigation - resolved

Ok - so relying on WPT issued messages may not be a good thing. The basic message states that the location is already running too many tests, but this is just a default message that is issued if the test cannot be added. A quick look in the logs shows that the server was space constrained so a quick delete of the previous results followed by another reboot has cleared this condition.
Hope this helps others as a potential check if you come across the same message.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)