docker system prune -a
didn't delete anything
There is only 35 Mb in the /home/yellowtent/platformdata/logs
Any idea what is this docker/overlay2
that is taking all the space in the /var/lib folder ?
I'm going to increase to 80Gb...
docker system prune -a
didn't delete anything
There is only 35 Mb in the /home/yellowtent/platformdata/logs
Any idea what is this docker/overlay2
that is taking all the space in the /var/lib folder ?
I'm going to increase to 80Gb...
I still can't access my server, anyone knows what file I can delete or how I can reclaim those 2Gb of reclaimable docker images ?
Other option is too increase my server to 80Gb but it would cost me $50 and I still would like to understand what is taking all the space
Thx for the script will certainly do that once I get back my server. What does the /var/run/reboot-required
file contains ? Would be nice if this was included in cloudron out of the box
Any idea what files I can delete to get back some space ?
Here are the result I have with those command:
root@4v9c:~# du -hcs /home
18G /home
18G total
root@4v9c:~# docker system df
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 14 14 8.965GB 2.21GB (24%)
Containers 15 14 0B 0B
Local Volumes 46 28 216MB 102MB (47%)
Build Cache 0 0 0B 0B
root@4v9c:~# cloudron-support --troubleshoot
No more space left on /
This is likely the root case of the issue. Free up some space and also check other partitions below:
Filesystem Size Used Avail Use% Mounted on
tmpfs 392M 2.1M 390M 1% /run
/dev/sda2 40G 38G 0 100% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b8a613802b3639564e0604ffb03d10d7ed5fd7a4f1ba7703ee9545290b2a8b2f/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b1c9c97404110f67157fa968a837d455c89b51ff80c9341096dddd19356775b5/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b0f743964f5f3183b89865325a08959d53c4b534102c12c461312139e6090253/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/79817dd38f34c049b390e58630e9009fd798b962302df001f23cf4e4620c2380/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/16837309ee1848202e65f0253aa676090e7c892ba840a5b049c0408b43caa2a7/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b5fe7e94b1a1613ffa654599a1fa91faf4274087817d8ec1df2ad43713869824/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/f65ba77ce0b920234d449ffbf1eccc5ce9fa2e7d24ae57f27c419e87365d4d81/merged
//u378641.your-storagebox.de/backup 1.0T 74G 951G 8% /mnt/volumes/a5fdbaf672ba41589bffb86d6ecd743b
overlay 40G 38G 0 100% /var/lib/docker/overlay2/a466339b5d66fc034568b89f249b1a980a93ea294158d58747a47f7677ae1d3f/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/068993a6f6f82e4b8b5aa70c155fdf5cd4c8476dc03168e3b39e27dfc35cdc97/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/72a2f687181ba18b78fd90b68bac59ec64e7855c90d25498e2ea5ea9b83eb057/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/ae00c782fcf6eafa8a4bded317aa14da88b036ce0b3890f7928c2c729211b059/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/0cef13e4b6a370c8bc6b65685376bfe26672031de38f9958c5799887b2418784/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/d0335e7fb5c9a922c3ef3f6f55b7199025a0ad51751ed4c7aa07194d0a3f24c4/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/e6ea004d2e793c0f545c58c92194eaec781f38ec15539d4264b7ee15b3297bdd/merged
tmpfs 392M 4.0K 392M 1% /run/user/0
not sure to understand more. What is this /var/lib/docker/overlay2
?
Also I see that there is 2GB of reclaimable docker images. Any idea how I can reclaim those ? I tried docker image prune -a
but nothing
Yes I do, but it seems backups doesn't take much space, only 385Mo. But there is 48Go in /var/lib
which is strange as I only have 40Go...
root@4v9c:~# du -d 1 -h /var
4.0K /var/local
48G /var/lib
385M /var/backups
134M /var/cache
36K /var/tmp
133M /var/log
96K /var/snap
4.0K /var/crash
16K /var/spool
4.0K /var/opt
4.0K /var/mail
12K /var/www
48G /var
What files or folder can safely be deleted in the /var/backups
?
root@4v9c:~# ls -la /var/backups/
total 2100
drwxrwxrwx 14 root root 4096 Feb 1 00:00 .
drwxr-xr-x 14 root root 4096 Nov 11 11:13 ..
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 10 23:01 2024-01-10-230139-835
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 15 23:00 2024-01-15-230042-376
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 19 23:01 2024-01-19-230103-885
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 21 23:01 2024-01-21-230152-107
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 27 23:02 2024-01-27-230000-928
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 27 23:02 2024-01-27-230203-539
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 29 23:02 2024-01-29-230000-860
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 30 03:00 2024-01-30-030006-856
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 30 05:00 2024-01-30-050001-020
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 31 01:00 2024-01-31-010003-349
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 31 03:00 2024-01-31-030000-827
-rw-r--r-- 1 root root 51200 Jan 5 00:00 alternatives.tar.0
-rw-r--r-- 1 root root 2646 Dec 22 00:00 alternatives.tar.1.gz
-rw-r--r-- 1 root root 2635 Dec 16 00:00 alternatives.tar.2.gz
-rw-r--r-- 1 root root 2636 Dec 12 00:00 alternatives.tar.3.gz
-rw-r--r-- 1 root root 2623 Nov 12 00:00 alternatives.tar.4.gz
-rw-r--r-- 1 root root 2358 Sep 15 2022 alternatives.tar.5.gz
-rw-r--r-- 1 root root 33665 Jan 27 06:08 apt.extended_states.0
-rw-r--r-- 1 root root 3641 Dec 12 06:20 apt.extended_states.1.gz
-rw-r--r-- 1 root root 3640 Nov 23 06:48 apt.extended_states.2.gz
-rw-r--r-- 1 root root 3643 Nov 11 11:18 apt.extended_states.3.gz
-rw-r--r-- 1 root root 3054 Sep 16 2022 apt.extended_states.4.gz
-rw-r--r-- 1 root root 3119 Sep 15 2022 apt.extended_states.5.gz
-rw-r--r-- 1 root root 3973 Sep 15 2022 apt.extended_states.6.gz
-rw-r--r-- 1 root root 0 Feb 1 00:00 dpkg.arch.0
-rw-r--r-- 1 root root 32 Jan 28 00:00 dpkg.arch.1.gz
-rw-r--r-- 1 root root 32 Jan 25 00:00 dpkg.arch.2.gz
-rw-r--r-- 1 root root 32 Jan 19 00:00 dpkg.arch.3.gz
-rw-r--r-- 1 root root 32 Jan 17 00:00 dpkg.arch.4.gz
-rw-r--r-- 1 root root 32 Jan 13 00:00 dpkg.arch.5.gz
-rw-r--r-- 1 root root 32 Jan 5 00:00 dpkg.arch.6.gz
-rw-r--r-- 1 root root 268 Sep 15 2022 dpkg.diversions.0
-rw-r--r-- 1 root root 140 Sep 15 2022 dpkg.diversions.1.gz
-rw-r--r-- 1 root root 140 Sep 15 2022 dpkg.diversions.2.gz
-rw-r--r-- 1 root root 140 Sep 15 2022 dpkg.diversions.3.gz
-rw-r--r-- 1 root root 140 Sep 15 2022 dpkg.diversions.4.gz
-rw-r--r-- 1 root root 140 Sep 15 2022 dpkg.diversions.5.gz
-rw-r--r-- 1 root root 140 Sep 15 2022 dpkg.diversions.6.gz
-rw-r--r-- 1 root root 100 Apr 23 2020 dpkg.statoverride.0
-rw-r--r-- 1 root root 120 Apr 23 2020 dpkg.statoverride.1.gz
-rw-r--r-- 1 root root 120 Apr 23 2020 dpkg.statoverride.2.gz
-rw-r--r-- 1 root root 120 Apr 23 2020 dpkg.statoverride.3.gz
-rw-r--r-- 1 root root 120 Apr 23 2020 dpkg.statoverride.4.gz
-rw-r--r-- 1 root root 120 Apr 23 2020 dpkg.statoverride.5.gz
-rw-r--r-- 1 root root 120 Apr 23 2020 dpkg.statoverride.6.gz
-rw-r--r-- 1 root root 741412 Jan 31 07:00 dpkg.status.0
-rw-r--r-- 1 root root 185249 Jan 27 06:08 dpkg.status.1.gz
-rw-r--r-- 1 root root 185145 Jan 24 06:40 dpkg.status.2.gz
-rw-r--r-- 1 root root 185144 Jan 18 06:10 dpkg.status.3.gz
-rw-r--r-- 1 root root 185145 Jan 16 06:43 dpkg.status.4.gz
-rw-r--r-- 1 root root 185146 Jan 12 06:14 dpkg.status.5.gz
-rw-r--r-- 1 root root 185141 Jan 4 06:27 dpkg.status.6.gz
drwxr-xr-x 2 yellowtent yellowtent 4096 Jan 31 03:00 snapshot
Hello,
It appears my disk is full and I can't access Cloudron dashboard anymore, nor any other app.
I can ssh into the server through.
I would like to clear up some spaces at least to restart the dashboard and check what is taking the space cause I don't store much on the server so this should not happen.
Can you help me regain access to my server ? What files could I safely delete ?
I tried docker prune image -a
as suggested in a post but didn't cleared any space
Filesystem Size Used Avail Use% Mounted on
tmpfs 392M 2.1M 390M 1% /run
/dev/sda2 40G 38G 0 100% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b8a613802b3639564e0604ffb03d10d7ed5fd7a4f1ba7703ee9545290b2a8b2f/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b1c9c97404110f67157fa968a837d455c89b51ff80c9341096dddd19356775b5/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b0f743964f5f3183b89865325a08959d53c4b534102c12c461312139e6090253/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/79817dd38f34c049b390e58630e9009fd798b962302df001f23cf4e4620c2380/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/16837309ee1848202e65f0253aa676090e7c892ba840a5b049c0408b43caa2a7/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/b5fe7e94b1a1613ffa654599a1fa91faf4274087817d8ec1df2ad43713869824/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/f65ba77ce0b920234d449ffbf1eccc5ce9fa2e7d24ae57f27c419e87365d4d81/merged
//u378641.your-storagebox.de/backup 1.0T 74G 951G 8% /mnt/volumes/a5fdbaf672ba41589bffb86d6ecd743b
overlay 40G 38G 0 100% /var/lib/docker/overlay2/a466339b5d66fc034568b89f249b1a980a93ea294158d58747a47f7677ae1d3f/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/068993a6f6f82e4b8b5aa70c155fdf5cd4c8476dc03168e3b39e27dfc35cdc97/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/72a2f687181ba18b78fd90b68bac59ec64e7855c90d25498e2ea5ea9b83eb057/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/ae00c782fcf6eafa8a4bded317aa14da88b036ce0b3890f7928c2c729211b059/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/0cef13e4b6a370c8bc6b65685376bfe26672031de38f9958c5799887b2418784/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/d0335e7fb5c9a922c3ef3f6f55b7199025a0ad51751ed4c7aa07194d0a3f24c4/merged
overlay 40G 38G 0 100% /var/lib/docker/overlay2/e6ea004d2e793c0f545c58c92194eaec781f38ec15539d4264b7ee15b3297bdd/merged
tmpfs 392M 4.0K 392M 1% /run/user/0
Thx for your answer.
@nebulon said in New User and default Library access:
Those things would have to get fixed upstream, so feel free to create an issue for this at the upstream project
what is the upstream project ? How do I create an issue for that ?
additional question:
When I delete a user from Cloudron User management, the user is not delete from Jellyfin and still have access
( but maybe I should open a new topic for this one?)
also, I tried creating a new user without restarting Jellyfin (when the EnableAllFolders
config is still there) and it works, new user have access to all librairies
The issue is now only that at restart this config got removed from the config file
I tried adding the line <EnableAllFolders>true</EnableAllFolders>
but when I restart the app the config is restored to the original version without the line.
I saved the file, I can see the line is there when I close / open the file, but after restarting the app the LDAP-Auth.xml
is somehow restored
Not sure it's a setting, I didn't find anything in the doc at least. It's more something you have to do in the user creation process: enter user name, then select library he can access.
Not sure if it is something Cloudron can do. How does Couldron create user ? Is it using an API from Jellyfin ?
When you create a user in Jellyfin, you have to manually select what library he can access.
So when you create a new user in Cloudron, this new user when login into Jellyfin will have access to none of the library. The admin has to login and manually give access to the libraries.
IMO, it would make more sense to give access to all librairies by default when you create a user via Cloudron. Otherwise it is simpler to create the user directly in Jellyfin.
Or is there already an option when you create the user Cloudron so that he can access all librairies ?
nevermind, port 25 is block on time4vps server
Hello,
I keep having this error:
foo.com
PTR DNS record (PTR) did not match.
Hostname: 195.xxx.xxx.xx
Expected: my.foo.com
Actual: xxxx.l.time4vps.cloud
Relay error: Connect to port25check.cloudron.io timed out. Check if port 25 (outbound) is blocked
Email Status is checked every 30 minutes. See the troubleshooting docs for more information.
And I can't send email, for instance when inviting new users.
I'm using AWS route 53 and it works well to auto create subdomains when I install a new app
Any idea what I should do to get the email working ?
I changed the setting directly in the UI, when going to "edit preferences" in the burger menu.
I checked in my config/settings.json
and in there indeed the folders are not the one I choosed in the UI. This might explain that it has been reseted.
So I changed the json as well and hopefully it will be fine now. Thanks
Is it the expected behaviour of Transmission ? That changes to preferences are not persisted on disk ? It seems quite wrong...
For some reason the configuration of my Transmission app have changed but not by my doing. It happened twice already.
My settings are :
And today the settings were:
The first time I thought it was because of an update (see this post) but it happened again today so it must something else.
Any idea ?
oh ok I thought I had to use https://firefly-importer.{my-domain.tld}
but it actually is https://{my-lamp-subdomain}.{my-domain.tld}
my bad
so it's actually working just fine thx
@girish said in Transmission + Jellyfin:
I thought I had preserved the old configuration for user's in older versions but maybe I made some mistake.
Ok I understand better now, I was surprised my config had changed. I will update my config back to what it was
Thanks for your help
@JLX89 said in Data Importer Tool:
- Restart the LAMP App and you can access the interface at: https://firefly-importer.domain.tld
Many thanks for this, very helpful !
However after doing all this configuration, I cannot access to the data-importer at https://firefly-importer.{my-domain.tld}
I have a DNS error.
I don't see in the .env
where the URL is set ? Also, I guess I need to create manually add an entry to my DNS record for the firefly-importer
sub domain ?
Yeah that pretty much what I did: adding a volume and mounting in both apps. I also had the issue with torrent disapearing in transmission and had to change a config as said in this post: https://forum.cloudron.io/topic/5811/torrents-are-removed-from-transmission-upon-completion/5
--> I think the default post processing script is not working and should be removed (https://docs.cloudron.io/apps/transmission/#post-processing-script)
So, couple of question: I see that Transmission package in my Cloudron have been updated to 2.3.0 which changed the configuration:
The working config I did in my Transmission was:
I don't see how the new config use a share volume ? Is the /app/data/files/Downloading/
a shared volume with Jellyfin? How do I read this volume from Jellyfin ? In the volume list in my cloudron I only see the one I created. Is it normal ?