OwnCloud 9 Time out error

Hey guys,

I'm using ownCloud 9.0.2.2 for a while. Since 4 days I can't access my owncloud due to timeout errors. I just changed nothing.

I can't access my cloud via browser, desktop-client or app.

See my Desktopclient-Error-Log here

 
03-16 14:11:36:767 0x1802300 TIMEOUT virtual void OCC::CheckServerJob::slotTimeout() 
03-16 14:11:36:767 0x1802300 "Keine Verbindung zu ownCloud auf <a href="https://jansandigsowncloud.spdns.org">https://jansandigsowncloud.spdns.org</a>
Zeitüberschreitung" 
03-16 14:11:36:771 0x1802300 Account "ObiJanKenobi@jansandigsowncloud.spdns.org" disconnected or paused, terminating or descheduling sync folders

Server configuration
Operating system: Resbian
Web server: Apache2 2.4.10
Database:
PHP version:
ownCloud version (see ownCloud admin page): 9.0.2.2
Updated from an older ownCloud or fresh install: fresh
Special configuration (external storage, external authentication, reverse proxy, server-side-encryption): none

ownCloud log (data/owncloud.log)

My apache2.log-File

[Thu Mar 16 06:25:21.449384 2017] [ssl:warn] [pid 884] AH01906: 127.0.1.1:443:0 server certificate is a CA certi$
[Thu Mar 16 06:25:21.449654 2017] [ssl:warn] [pid 884] AH01909: 127.0.1.1:443:0 server certificate does NOT incl$
[Thu Mar 16 06:25:21.451166 2017] [mpm_prefork:notice] [pid 884] AH00163: Apache/2.4.10 (Raspbian) OpenSSL/1.0.1$
[Thu Mar 16 06:25:21.451260 2017] [core:notice] [pid 884] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 16 10:17:18.198776 2017] [ssl:warn] [pid 725] AH01906: 127.0.1.1:443:0 server certificate is a CA certi$
[Thu Mar 16 10:17:18.200636 2017] [ssl:warn] [pid 725] AH01909: 127.0.1.1:443:0 server certificate does NOT incl$
[Thu Mar 16 10:17:19.769336 2017] [ssl:warn] [pid 874] AH01906: 127.0.1.1:443:0 server certificate is a CA certi$
[Thu Mar 16 10:17:19.769555 2017] [ssl:warn] [pid 874] AH01909: 127.0.1.1:443:0 server certificate does NOT incl$
[Thu Mar 16 10:17:19.790781 2017] [mpm_prefork:notice] [pid 874] AH00163: Apache/2.4.10 (Raspbian) OpenSSL/1.0.1$
[Thu Mar 16 10:17:19.791012 2017] [core:notice] [pid 874] AH00094: Command line: '/usr/sbin/apache2'

Some months ago, I had an issue with the storage but now I'm using 77%, so there is some space left.

Do you have any suggestions what I can do? Thank you very mutch Jan!

Hi Jan,

I had a case like that some time ago with zero responsiveness on any way to access the owncloud server. It helped to restart all services which are in my case nginx, php5-fpm and mysql. I would suspect mysql, so try to restart that first.

Best
Robert.

Besides the highly recommended suggestions above it also worth to upgrade this quite too outdated version to a recent one:

If you have a look at [1] you see that you're currently missing six minor versions.

[1] https://owncloud.org/changelog/#latest9.0

Hey guys thanks for the fast reply. Unfortunatly the restart option didn't work for me. I also checked my port-configuration and everything is normal. I'm planing to migrate to NC 11 during my next hollyday but now my OC has to work again =)

So there must be a connection available, cause there is no error -missed page-. But what does is time out error mean?

Regards

Can you call any other resource on that VHost besides your owncloud installation? Some plain HTML or text file or an info.php with <?php phpinfo(); ?> to sort out network and general webserver config issues.

Unfortunately everything I want to call in my browser doesn't work. If I typ in my-dns-server.org/info.php same timeout error but if I do my-dns-server.org/ddd.php (so a file that doesn't exists) there is the same timeout error. So it seems to me that I try to connect but the connection is not possible.

Yes, so that´s not owncloud specific. Try tracing your domain to see if DNS resolves. From console run this command

Mac:
traceroute jansandigsowncloud.spdns.org

Win:
tracert jansandigsowncloud.spdns.org

From my place it looks good, I get:
imacrobert:~ robb$ traceroute jansandigsowncloud.spdns.org
traceroute to jansandigsowncloud.spdns.org (88.72.11.114), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 1.133 ms 0.767 ms 0.864 ms
2 hsi-kbw-109-192-112-001.hsi6.kabel-badenwuerttemberg.de (109.192.112.1) 12.059 ms 14.633 ms 13.845 ms
3 172.30.10.137 (172.30.10.137) 10.180 ms 10.789 ms 11.560 ms
4 84.116.190.21 (84.116.190.21) 16.171 ms 12.575 ms 17.367 ms
5 de-fra01b-ri1-ae0-0.aorta.net (84.116.134.6) 24.056 ms 13.962 ms 14.474 ms
6 ae28-xcr1.fix.cw.net (195.2.22.209) 17.626 ms 15.341 ms 17.475 ms
7 ae1-xcr1.fri.cw.net (195.2.9.237) 13.307 ms 18.641 ms 15.137 ms
8 vodafoned2-gw-xcr1.fri.cw.net (166.63.204.210) 20.339 ms 17.679 ms 14.793 ms
9 188.111.206.213 (188.111.206.213) 42.813 ms 38.851 ms 40.795 ms
10 * * *

My results from my pi. (I m using Linux)

traceroute to jansandigsowncloud.spdns.org (88.72.11.114), 30 hops max, 60 byte packets
 1  fritz.box (192.168.178.1)  0.495 ms  0.540 ms  0.782 ms
 2  dslb-084-059-064-001.084.059.pools.vodafone-ip.de (84.59.64.1)  18.521 ms  18.740 ms  18.714 ms
 3  * * *
 4  188.111.206.213 (188.111.206.213)  20.947 ms  20.923 ms  20.904 ms
 5  dslb-088-072-011-114.088.072.pools.vodafone-ip.de (88.72.11.114)  34.978 ms  35.008 ms  35.496 ms

but running traceroute from my pc gives

traceroute to jansandigsowncloud.spdns.org
to: Zu diesem Hostnamen gehört keine Adresse
Cannot handle "host" cmdline arg `to' on position 1 (argc 1)

Ok, isolated now, right?

  • check if you can access any web resource from your pc
  • check which DNS servers are used by your gateway
  • switch e.g. to Google DNS 8.8.8.8 to test (for privacy only temporarily)
  • if it´s a new subdomain wait a few hours until its propagated everywhere
1 Like

:slight_smile:

Ok thanks guys! I just sensed an error in my dyndns-config. My IP was wrong, so i have to figure out why. Thanks for your help!