-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Android client: System Status view returns HTTP error #32
Comments
@alager, some followup questions: a) How often does this occur? thx |
a) It's only happened once that I've noticed |
Here are the syslogs
and here are the zmNinja logs
Just to complete the picture I have apache configured for 4 processes. |
So the previous comment should have said I had 4 apache processes running. |
Interesting. So Apache dropped that API HTTP request then? I see in your logs that it got a "daemonCheck" and then it got a "getLoad" but never received a "diskStatus" and my app returned an error, so does that mean the apache process just dropped that connection? Is that how Apache's limit works? I thought it would queue it up. The fact that you increased these limits and the problem is not recurring implies its not the app browser that is causing this issue, then. |
running 6 apache processes, I see an odd behavior here.
Even though the time stamp is within 1 second of the above two rows, these two rows below don't show up in the access log until almost 40 seconds later, and that is the moment that the page changes from "loading..." to 588.6GB for disk usage.
|
Now running 11 processes, the delay between those two sets is now about 3 seconds wall clock time, as is the update for the disk usage, but the logs still indicate about 1 second. Also of note, I have to exit zmNinja each time to test this, as the swipe down to refresh does not appear to refresh when the number of processes was 6 or less. |
@alager a large delay for disk status is normal - mine takes 15s - zm executes a Unix dF that takes a long time spending on number of events files. |
is this still a problem @alager ? |
no, once I increased the number of apache processes, these issues went away. |
@alager reports that when viewing the "System Status" screen, the HTTP APIs return an "error" like ZM returned nothing. However, he looked at logs of ZM and the request does not get there.
My hypothesis is this:
Chrome has a limit of 6 concurrent connections to one domain - when you view System Status, it shoots off 4 APIs in parallel (4 HTTP connections). In the event there are other HTTP connections that have not yet terminated in zmNinja, this may be resulting in a hang state.
In the past I've observed when you hit this limit, Chrome (the web view the client is using) does not recover well from this. In addition, I make HTTP timeouts for the system status requests long. I don't know if this adds to the issue.
This issue will track this problem as I take @alager's help to characterize this better
The text was updated successfully, but these errors were encountered: