DEAR TRIGGER HAPPY MODS:
BEFORE CLOSING TOPICS IN THIS FORUM YOU SHOULD BE ABSOLUTELY SURE, THAT THE ISSUE DESCRIBED IS NOT CAUSED BY UNRAID! YOU'RE HOSTING A PRODUCT AND I HAVE STILL 18 DAYS TIME TO DECIDE IF YOUR BEHAVIOR IS THE WAY I WANT TO BE HANDLED AS A FUTURE CUSTOMER! I'M TRYING TO GET UNRAID WORKING TO RUN NEXTCLOUD, NOT RESEARCHING NEXTCLOUD'S FUNCTIONALITY!

------------------------------------------------------------------

Hey!
 

I'm experiencing the following:

in the Photos section, many previews are not generated on demand and will not be updated, even if i throw

docker exec -it nextcloud occ preview:generate-all -vvv

at them. The result is seen in the screenshot given.
 

• In the Nextcloud app on my phone, entering the photo view works for about 100 images, after that the app stutters and freezes, heating up the phone in a terrible way. When doing this, missing previews are displayed.
   
• I have about 600 images in the folder, all of them are normal sized JPGs, no RAW images or anything exotic. The file sizes of the images is about 2-3 MB each.
   
• My nextcloud-data is stored in my array as secondary location, the first is an cache nvme and mover taking care of nightly transfers.
   
• My default directory for container appdata is /mnt/cache/appdata
   
• I am really confused about where the exact location of the preview files is. I have one at /mnt/user/nextcloud/app_[id] and one at /mnt/cache/nextcloud/app_[id]. If i move the cache preview folder and do a rescan, no new preview folder will be created. If i move the one in the user folder, occ preview:generate-all quits with 'can't create folder'.

Can anyone help me understand, what's going on? Is this explainable with the cache/array setting?
When clicking on an image with a bad preview, it takes about 6 seconds to open, files with a good preview open instantly. So i'm convinced it is an unraid thing failing to host a nextcloud instance. Can anyone help me pointing in the right direction?

terra-diagnostics-20240729-2235.zip

9 minutes ago, Gekko said:

Can anyone help me pointing in the right direction?

There are MANY different implementations of nextcloud, each with somewhat unique environments and quirks. You need to post in the specific support thread for the container you are using, not start new threads randomly.

 

If you click on the nextcloud icon on Unraid's GUI, the dropdown has a "support" item. That should take you to the correct area to get support for that container. Note, not all containers are supported here, some container authors choose to support their containers on discord, or on their github.

 

This general support area is for issues with the core structure of Unraid, not community supported applications.

Yeah, there are many implementations of nextcloud, i know - thanks for your help.

 

After trying to let nextcloud recreate the previews folder by using

docker exec -it nextcloud occ preview:generate-all -vvv

i stepped into an error:

[OCP\Files\NotPermittedException]                                            
Could not create folder "/appdata_[MyInstanceID]/preview/4/1/0/0/9/0/5/82634"

 

So i moved the content of my photos from a synced remote directory on a windows machine out of nextcloud's reach and wiped the whole preview directory with

rm -r /mnt/user/nextcloud/app_[MyInstanceID]/preview

logged into mariadb via

docker exec -it mariadb mysql -h [MyMariaDBDockerContainerIP] -P 3306 --protocol=tcp -u root -p nextcloud

provided the root password for mariaDB and inserted the following line:

DELETE FROM oc_filecache WHERE path LIKE "appdata\_[MyInstanceID]/preview/%";

 

After that, i moved the photos folder back into the synced directory, let Nextcloud do it's magic and after having synced the content, i dropped

docker exec -it nextcloud occ files:scan --all

docker exec -it nextcloud occ preview:generate-all -vvv

to rebuild the preview pictures.

 

Now, the photos section not only works again, but is incredibly fast as well - it never performed so well during the whole installation.

 

I wrote this down here in unraid forums to include it the way other users can reproduce this solution if they step into the weird behavior or experience the error mentioned above. I'm hosting this installation for me and my girlfriend, so i had not to worry about a huge user population.

As far as i'm concerned, nothing was specifically unraid related regarding the origins of the weird behavior. Every command displayed here shows the way how the solution can be handled using unraid's terminal and docker logic.

 

Good luck,

Gekko

 

[Edit: spelling]

Edited July 30, 20241 yr by Gekko

1 hour ago, Gekko said:

I wrote this down here in unraid forums to include it the way other users can reproduce this solution if they step into the weird behavior or experience the error mentioned above.

This thread will get lost in the noise in a matter of days.

 

If you really care to help others, post this in the support thread for the container in question, that way your post will be read by others seeking support for that container.