Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

curl_exec: Operation timed out after 10000 milliseconds #8099

Closed
roddyofchina opened this issue Jun 12, 2015 · 3 comments
Closed

curl_exec: Operation timed out after 10000 milliseconds #8099

roddyofchina opened this issue Jun 12, 2015 · 3 comments
Labels
answered For when a question was asked and we referred to forum or answered it. Bug For errors / faults / flaws / inconsistencies etc.
Milestone
Long term

Comments

@roddyofchina
Copy link

curl_exec: Operation timed out after 10000 milliseconds with 7193 bytes received. Hostname requested was: plugins.piwik.org

my piwik version's is 2.13.1 .

Nginx error:
1880#0: *114 FastCGI sent in stderr: "PHP message: Error in Piwik: <title>Piwik › Error</title>

An error occurred

curl_exec: Operation timed out after 10000 milliseconds with 43193 bytes received. Hostname requested was: plugins.piwik.org

Go Back | Go to Piwik | Login

  • <a rel="noreferrer" target="_blank" href="" while reading response header from upstream, client: x.x.x.x, server: localhost, request: "GET /index.php?module=CorePluginsAdmin&action=browsePlugins&idSite=18&period=day&date=today&activated=&sort= HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "s", referrer: "
@mattab
Copy link
Member

mattab commented Jun 16, 2015

Hi @roddyofchina

Thanks for the report. 10000 milliseconds with 7193 bytes means your server downloads from the marketplace at about 1 kb/s. This is very slow internet connection unfortunatley.... your Piwik is trying to download the JSON file of list of plugins that weights 350Kb. it could take 350 seconds. that's very long time to wait. I'm wondering what is our best option?

  • increasing timeout from 10s to 400s does not seem a good idea? (having user wait 400 second is maybe as bad user experience as showing the above error message)
  • maybe we could pre-cache the marketplace response (eg. a scheduled task downloads the JSON file)
  • even if we display the marketplace very fast (eg. with pre-caching) it will be slow or broken to install / update third party plugin (assuming user downloads at 1kb/s)... so i'm not sure what is the best thing we could do.

refs #7280

@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Jun 16, 2015
@roddyofchina
Copy link
Author

Thank you very much! Now I use planning task to download plugins.

@mattab
Copy link
Member

mattab commented Jun 16, 2015

@roddyofchina what do you mean by "Now I use planning task to download plugins." ?

@mattab mattab reopened this Jun 16, 2015
@mattab mattab added this to the Mid term milestone Jun 16, 2015
mattab referenced this issue Aug 12, 2015
@mattab
Fixes #8553Increases timeout for core updater as reported
caea9b1
@mattab mattab closed this as completed Aug 12, 2015
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Oct 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it. Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Milestone
Long term
Development

No branches or pull requests
2 participants
@mattab @roddyofchina