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

Tenant timeout loading #419

Closed
alarido opened this issue Aug 3, 2016 · 3 comments
Closed

Tenant timeout loading #419

alarido opened this issue Aug 3, 2016 · 3 comments
Labels
type: bug A confirmed report of unexpected behavior in the application

Comments

@alarido
Copy link

alarido commented Aug 3, 2016

I have a big tenant thousands of IP addresses, hundreds of prefixes, vrfs, connections, devices, ... when I go to the tenant view it timeouts:

https://netbox.server/tenancy/tenants/MYBIGTENANT/

I have been increasing timeout from default to several minutes, but it does not load anyways, it always timeouts, database and netbox server load is low:

Apache proxy error:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /tenancy/tenants/MYBIGTENANT/.

Reason: Error reading from remote server

supervisord netbox log error:

2016-08-03 09:28:33 [37301] [ERROR] WORKER TIMEOUT (pid:37306)

@jeremystretch jeremystretch added the type: bug A confirmed report of unexpected behavior in the application label Aug 3, 2016
jeremystretch added a commit that referenced this issue Aug 3, 2016
@jeremystretch
Copy link
Member

@alarido I suspect that the way we're annotating stats for the tenant in a single query is causing a database performance issue. I've rewritten the view to use a simple, discrete COUNT() for each statistic now. Could you try pulling down the develop branch and seeing if it solves the issue for you?

@jeremystretch
Copy link
Member

Should be fixed in v1.4.1 but please let me know if you still experience the problem.

@alarido
Copy link
Author

alarido commented Aug 4, 2016

It is fixed, thanks.

if-fi pushed a commit to if-fi/netbox that referenced this issue Oct 1, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants