Comment on Issue: The limits of the cloud?
pepecyb@hub.hubzilla.hu@hub.hubzilla.hu 2 weeks ago That’s what I’d suspected at first, too. But what sort of ‘configuration error’ could be responsible for files from certain directories suddenly timing out when referenced? I pushed my hub even further tonight (until it crashed with the error message). And it’s reproducible: files newly added to certain directories cause the timeout error. Older files already present in precisely these directories do not cause the error, even when reused in a post. The files that caused the problem do not trigger the error if I upload them to new directories (including sub-, sub-sub-… directories) or to other sub-directories that have existed for a long time, and then use them in posts.
If this error were to occur generally, that assumption would make sense, but as it only happens in a few specific directories – and only with newly added files (which, by contrast, cause no problems in other directories) – I no longer necessarily assume it is down to a misconfiguration. I have currently identified the problem in two directories…
Pepes pic (41.6 MiB, 208 files, 1 subfolder)
Artikelbilder (39.0 MiB, 120 files, 10 subfolders)
The channel’s entire cloud: 233.1 MiB, 1,118 files, 92 subfolders.
If this error were to occur generally, that assumption would make sense, but as it only happens in a few specific directories – and only with newly added files (which, by contrast, cause no problems in other directories) – I no longer necessarily assume it is down to a misconfiguration. I have currently identified the problem in two directories…
Pepes pic (41.6 MiB, 208 files, 1 subfolder)
Artikelbilder (39.0 MiB, 120 files, 10 subfolders)
The channel’s entire cloud: 233.1 MiB, 1,118 files, 92 subfolders.
Just a wild guess: new files are being fetched by all receivers, old files might already be cached and will not be fetched in the same extend as new ones.
Example:
I upload the image A.png (a completely new image) to the “Artikelbilder” folder and embed it in a post: after a short while, the hub freezes and displays the error message in the log.
After rebooting, I delete the post and the image.
Then I upload the image A.png again to a different directory and use it in a post: no error occurs.
I upload a completely new image, B.png, to a different directory and use it in a post: no error occurs.
I upload the image B.png to “Artikelbilder” and use it in a post: after a short while, the hub freezes and displays the error message in the log.
Reboot, delete…
I move the image B.png from the other directory to “Artikelbilder” and use it for a post: after a short while, the hub freezes and displays the error message in the log.
The only thing that might explain this is that the issue does not occur with older images already present in the critical directories.
Nor did the method of referencing in the source code (i.e. <HUB>/photos/<HASH_FILENAME> or <HUB>/cloud/<CHANNEL_NAME>/<REAL_FILENAME>) make any difference. New images from the two problematic subdirectories caused the system to freeze, whilst images from other directories did not. I’ve now simply stopped using those two directories for new uploads… but that's obviously just treating the symptoms.
I’ll get back to you as soon as I have the results.