Thanks. It worked
I only had to add vers=1.0 because my NAS (FritzBox) only uses SMB 1.
Best posts made by smilebasti
-
RE: Backup to NAS via SMB
Latest posts made by smilebasti
-
RE: Nextcloud stuck in update queued after Cloudron Update to 7.0
@girish I found this when i clicked update:
Both my apps are running and are accessible.
I now tried stopping the Nextcloud instance and started it.
And it the app the 1 dead app is now 2 alive and 0 dead.
Now i could update normally.Not sure what i missed in the first place but now works.
Thanks for the help
-
RE: Nextcloud stuck in update queued after Cloudron Update to 7.0
@privsec Thanks for the tip. It had enough space and i think the redis service would have restarted with the full reboot.
-
RE: Nextcloud stuck in update queued after Cloudron Update to 7.0
@girish Thanks for the checkin.
Haven't been notified about your reply.No the issue still persists.
-
Nextcloud stuck in update queued after Cloudron Update to 7.0
Hi, i noticed it first after the update of 6 to 7 that my Nextcloud instance is stuck in updating.
I tried having a look into the logs but didn't find anything. Tried rebooting afterwards. I forgot about the issue and now came back to this. Everything is set to auto update.
When i manually click on update now the button disappears after a few seconds, but it only shows update (queued).
Maybe this could have happened because the backup of the Nextcloud instance took to long. (currently working on a solution for that). The Backups are still working normally.
What logs are needed for further help?
Thanks ahead -
Nextcloud Key is duplicated still after Update
Hi,
i got the overnight Update of my Nextcloud. Now i have the following duplicate Key Error:Dec 14 10:59:07 => Applying oc_filecache_extended workaround Dec 14 10:59:07 SELECT 9852 Dec 14 10:59:07 ALTER TABLE Dec 14 10:59:07 ALTER TABLE Dec 14 10:59:07 DROP TABLE Dec 14 10:59:07 Check primary keys. Dec 14 10:59:08 Adding primary key to the filecache_extended table, this can take some time... Dec 14 10:59:09 In AbstractPostgreSQLDriver.php line 51: Dec 14 10:59:09 Dec 14 10:59:09 An exception occurred while executing 'ALTER TABLE oc_filecache_extended AD Dec 14 10:59:09 D PRIMARY KEY (fileid)': Dec 14 10:59:09 Dec 14 10:59:09 SQLSTATE[23505]: Unique violation: 7 ERROR: could not create unique index Dec 14 10:59:09 "oc_filecache_extended_pkey" Dec 14 10:59:09 DETAIL: Key (fileid)=(35050) is duplicated. Dec 14 10:59:09 In PDOConnection.php line 83: Dec 14 10:59:09 Dec 14 10:59:09 SQLSTATE[23505]: Unique violation: 7 ERROR: could not create unique index Dec 14 10:59:09 "oc_filecache_extended_pkey" Dec 14 10:59:09 DETAIL: Key (fileid)=(35050) is duplicated. Dec 14 10:59:09 In PDOConnection.php line 78: Dec 14 10:59:09 Dec 14 10:59:09 SQLSTATE[23505]: Unique violation: 7 ERROR: could not create unique index Dec 14 10:59:09 "oc_filecache_extended_pkey" Dec 14 10:59:09 DETAIL: Key (fileid)=(35050) is duplicated. Dec 14 10:59:09 db:add-missing-primary-keys
I just did the latest update manualy but i didn't fix anything. Also i tried restarting Cloudron with Nextcloud in Recovery Mode as mentioned in a different Issue.
Cloudron is now 6.0.1 and Nextcloud is now 20.0.3 with the Packaged version v4.8.3
Thanks ahead for your help
-
RE: Strange storage usage
@fbartels That's very nice to use. Thanks.
I narrowed it down to /home/yellowtent/appsdata with 53,8 GB but i would not change something here.
The other two huge folders are in /var/lib/docker.
First is /volumes with one large file (53 GB) ending with ...-local-storage. The second (22 GB) is the folder /overlay2.Is it safe to run
docker system prune -a
?
Maybe also-volumes
? Does this mess anything up with Cloudron if my two apps are running? -
RE: Strange storage usage
Thanks for the reply.
The Vm has already 5GB of Ram. Swap is about the same of what i can find.I will have a deeper look.
-
Strange storage usage
Hi,
as shown in the photo my Cloudron is running out of space. But not from Cloudron or its apps.
I have my Backups on an Nas added via SMB.There is nothing else installed on this VM. As it could only be Cloudron creating 120GB i am not sure how to clean them up.
Once i added 100 GB to the VM and formatted it correctly.Thanks ahead for your help
-
RE: Mastodon Terminal not starting
This is the chrome console error
website erased -
RE: Mastodon Terminal not starting
Thats the Error i get when i am starting the terminal
<I deleted the image because it showed the domain name - girish>