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
[Windows] [1.8nightly 4759] No connection after resume of PC #2899
Comments
Thanks for the log! It shows that the client regularly runs a CheckServerJob which comes back with RemoteHostClosedError. It doesn't look like a client error... I'll try to reproduce it. |
Hm, I can't suspend or hibernate my Windows VM, someone else will need to try to reproduce this. |
Note: when i close the client (Exit) and start it again it works! So i think it might be a client bug. I also was checking the owncloud.log. No specific errors in there. |
Maybe dicannect from network and reconnect after some time could simulate it in the vm? |
@MegaV0lt Disconnecting and reconnecting the network works fine. |
@ckamm just for reference, you can restrospectively enable hibernate: http://www.giannistsakiris.com/2009/04/08/how-to-enable-hibernate-in-windows-xp/ |
went out for shopping. standby was about one hour. client working normal. maybe a "overnight" issue ore time/date related? |
Ok, today after aprox. 3 hours standby: |
From the logs, as ckamm already said: the client is querying to status.php to know if the server is there. But we get an error ( NetworkError::RemoteHostClosedError ) That's strange. Why would the server closes new connections after we resume from sleep? And why would it work again when one restart the client. |
the owncloud.log on teh server does not show any access at the time... maybe the request did not even leave the clientpc? Othe rnetworking apps still work normal at the same time (eg. dropbox, ff, tb, webradio). Must be something with the client in my poor opinion |
Also no TCP-Connection to see in Process Explorer: |
And if you wait for 10 minutes? does it still not work? |
I try next time |
As expected: Nothing after 15 minutes... Sharing is also not working, because of teh no connection problem, so it is a dropbox-link |
The logfile shows this lines:
That means that we do NOT start the ETag job because the AccountState is Network Error rather than Connected. |
And other lines:
In the normal case, a succeeding CheckServerJob would reset the AccountState to Connected, and as a result the ETagJob from above would start. The CheckServerJob is actually started, but it fails reporting "Verbindung beendet". This job just tries to access status.php. Is it possible that there is any problem in your setup causing this? |
What should this be? I have a local network-connection with the oc-server (sheevaplug). I use my self created ssl-certs. On my laptop is still version 1.7 of the client but usese dyndns as adress of course what info ddo you need? |
Mybe. At least the effect described in #2973 i also had one time with 1.8beta2. Today i installed the final 1.8 client. I give new feedback here, when it occurs next time. |
…loud#2973 The QNetworkAccessManager is reset when we are disconnected, just before attempting to fetch the server's status.php. This may help fix the problem described in various issues where we get 'Connection closed' or timeout errors after the OS has woken from sleep.
@MegaV0lt I just pushed a possible workaround. Could you try again with tomorrow's build from http://download.owncloud.com/desktop/daily/ ? |
Of course i will test. Feedback follows as soon i have a result |
We got a built that includes the maybe-fix early: http://download.owncloud.com/desktop/daily/ownCloud-1.8.0.4850-nightly20150319-setup.exe |
Ok, i install 4850 now ;) |
Since the #4850 build. Seems working now. Thanks... |
Great, thanks for testing! |
Again with occlient 4893: |
@MegaV0lt Have you seen my comment here: #3969 (comment) |
usualy i only set my pc to power save mode. After resume on the next day the oc client does not connect:
When i exit oc client and start it again it is workinkg again
in 1.7.1 version that was working
The text was updated successfully, but these errors were encountered: