running out of SD cards.
You need to make sure you extended the sd card to take full size. You can do it from Settings - Internal memory. Otherwise you will run out of disk space very quickly.
But how can I remove the nextcloud from terminal? There is no “remove” in the UI. It shows only install after it breaks. But I guess some files still remain.
maybe it is not installed then, check this command:
snap list
snap remove nextcloud
Check disk space
df -h
Expand sd
/snap/platform/current/bin/boot_extend.sh
Filesystem Size Used Avail Use% Mounted on
udev 1.5G 0 1.5G 0% /dev
tmpfs 371M 24M 347M 7% /run
/dev/mmcblk0p2 30G 8.5G 20G 31% /
tmpfs 1.9G 1.1M 1.9G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
should be ok. Problem is, that at some point, installation from store is not going any further…
Access through untrusted domain Please contact your administrator. If you are an administrator, edit the “trusted_domains” setting in config/config.php like the example in config.sample.php
if I edit the config file manually and insert my subdomain as trusted, I can login into nextcloud, but while the installer is running. Then it runs into a timeout that says its not possible to load the default config and then installation process breaks and the app can not be opened (502)
I get even during installing:
snap run nextcloud.occ status
- installed: true
- version: 30.0.4.1
- versionstring: 30.0.4
- edition:
- maintenance: false
- needsDbUpgrade: false
- productname: Nextcloud
- extendedSupport: false
Again you should not edit any files, if you have to edit some files that means something is broken and we need to understand what.
So just to confirm this is fresh install of latest Nextcloud is not finishing?
Can you send logs from Settings - Support and check include support?
Alright, I just wanted to test what is broken, but I will avoid editing in future.
Yes, I started with fresh Syncloud SD Card following the steps in Device migration · syncloud/platform Wiki · GitHub
I did one mistake, as I tried to restore from backup before installing. This failed. But to install now from Store (not from Backup) also fails. I never made it to any state where installation finished yet.
I think it always stops at the same point. Maybe the installation sees some nextcloud files in the external storage that is confusing? I could also detach external storage and try to install from store. Would I be able then to enable storage again and restore from backup (which had external storage)?
I just sent logs yesterday while doing it. I can reforward again.
Send logs again and let me know here right away please
I think I was / I’m facing several issues.
Regarding my last post, I found out, that the SD card was a problem, as it was formatted as ExFat. So it looks like that the SD card is not completly formatted during flashing with Etcher and it makes a difference, how the SD card is formatted before flashing.
It looks like that not every SD card / Device Hardware fits every formatting type. So this SD card or Odroid HC4 was not able to deal with ExFat.
root@syncloud:~# dmesg | tail -100
EXT4-fs error (device mmcblk0p2) in ext4_free_inode:358: Corrupt filesystem
So I bought a new SD Card and I’ve seen that this was using ext4 format or at least after flashing with Syncloud image. As I was facing more issues, I had to flash several times and retry things. For every flashing I had to format the new SD card to ext4 again, as I’m not able to flash the Syncloud image on a SD card that has already the Syncloud image.
So ext4 seems to work for me, as I was able to install apps and also restore my nextcloud app to v30.
The issue I was facing was to try to install syncthing. Either the Odroid HC4 has not enough RAM or there is another reason:
Out of memory: Killed process 7917 (syncthing) total-vm:1650292kB, anon-rss:359244kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:816kB oom_score_adj:0
Anyway, I’m ok to not have syncthing now, as I didn’t used it before. But I still have some rights problems:
When I install Calibre, Installation works. However, I’m not able to upload something. Logs:
UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use.
Also I’m not able to restore Calibre App, logs say:
Settings database is not writeable. Exiting...
and same with Nextcloud. I’m able to read the data, but I can’t upload anything. The UI says something like “Operation is blocked by access control”.
Just sent logs with “Send a copy to support” = true. Email says:
Thank you for sharing Syncloud device error info, Syncloud support will get back to you shortly.
If you need to add more details just reply to this email.
Well something is wrong, never had to do it in my life.
Before etcher when I was using dd tool OS could mount and prevent me from having image written correctly. With Etcher it never happened.
Are you flashing on Ubuntu pc? what version of Ubuntu and Etcher are you using?
Have you enabled validation in Etcher? What kind of SD cards are you using?
Filesystem and partitions are destroyed after a successful image write, if not you have some issues writing the image.
I think gramps is using a lot of memory, try removing it
Yes, you are right. Just removed gramps and 2 GB of RAM are free.
But I have a state now, which works and Syncloud device is reachable also after one night. So I just need to fix the writing rights to database issue (calibre, nextcloud) and everything is fine.
If you have any idea which command could help to get more information or to fix it, I would be happy.
Ok, fixed for Syncloud with:
sudo chown -R nextcloud:nextcloud /data/nextcloud
Just need to find out for Calibre
Usually install of the app should do it for you, try reinstalling calibre.
Ok recent changes in backup broke permissions during the backup restore inside /var/snap/[app] the fix is coming today or tomorrow untill then needs a manual chown.
Permissions in storage dir /data/[app] are not broken but changing permission an a huge collection of files takes a lot of time so there is a limit there. If amount of files in /data/[app] is more than 1000 permissions are not fixed. The fix is also coming here, probably just removal of the limit.