Cloudron Forum

Paperless can take a while to process a large PDF. But I noticed in the resource monitor it never uses more than one CPU core even though I allow it to use 97% of 16 cores in the settings. I know paperless has several sub services installed with it. Is it possible that the sub services are limited to one core even though I allow more for the main app?

@seanmahrt I'm having the same issue. How did you fix the port 80 forwarding?

Yes, please. Minetest instead of Minecraft.

I'm getting out of memory warnings in Cloudron about paperless. In the resource monitor it never uses more than 4.5gb of memory even though I allow it to use 6gb in the settings. I know paperless has several sub services installed with it. Is it possible that the sub services are limited to less memory than the main app? Or maybe the resource monitor only knows the memory usage of the main app and not the sub services?

My external email is on the root domain while my cloudron is on a sub domain. In the email settings of each app, I can only select cloudron domains and can not enter my external email domain.

I have an old slow NAS for doing network drives (SMB/AFP/NFS). Is there an app on Cloudron for network drives?

@ovny Could you make a guide on how to do this? I think it would help with the port 25 issue, among other things.

@girish If I want to clear out that old backups folder, do I just sudo rm -r the whole thing? Or is there something in there that should be kept? (something that isn't just a backup, like maybe the backup settings)

Yes that is what I'm asking.

@girish I'm pinging you because the git history shows you as the main author of all the code files involved.

So the problem is that the disk usage data is still cached in a file (https://git.cloudron.io/cloudron/box/-/blob/master/src/system.js?ref_type=heads line 260) from checking before the 2 ghost volumes were removed.

So simply forcing a recheck should fix it. But that can't be done because the button is disabled.

So I force enabled the button in my browser, clicked it, and now it is working fine.

So the issue seems to be, that the cache file is not invalidated when a volume is removed. (maybe it is normally but failed for me)

For a simple solution, I would propose enabling the recheck button as soon as the api call returns before executing the handling of the data. So that way if there is an error processing the data, the button is enabled.

See https://git.cloudron.io/cloudron/box/-/blob/master/dashboard/src/views/system.js?ref_type=heads

Of course check into the disk usage cache file invalidation, too. I assume that "normally" when you remove a volume, the file is invalidated. But there seems to be an edge case where it does not always.

Edit: I just had a look over volumes.js and mounts.js and it look like the cache file is never invalidated by the del/remove action.

@Recliner2042 said in Disk Usage Stuck:

Including those two ghosted volumes, I have a total of 4 volumes (not all in the same disk) and all are missing the name field.

After reading the code closer, I see that the name field is not actually supposed to be there in the API call. It finds the name from the volume map from the volumes api call.

But the 2 ghosted volumes, are not returned by the volume api call.

(above: only the two valid volumes returned by volumes call)

And so their name can't be found when they are looped over after the disk_usage api call.

So the question is: why is the disk_usage API call picking up ghost volumes that the volumes API call is not picking up?

Possibly related. I have these 2 ghost volumes. By that I mean I had properly removed them but they are still listed.

Including those two ghosted volumes, I have a total of 4 volumes (not all in the same disk) and all are missing the name field.

But on the Volumes screen, the names do come through. It is only on the Disk Usage screen that they don't. (also the ghost volumes don't show on the Volumes screen)

@murgero That did not help.

But, I did some more debugging. I see in the code that it is indeed looking for the volume name.

See https://git.cloudron.io/cloudron/box/-/blob/master/dashboard/src/views/system.js?ref_type=heads for the context of that code.

And in the API the volume name is not coming through.

As of today, the Disk Usage under System Info never stops the spinner to show the results. In the browser's network debug tab, the api call completes as 304 Not Modified and has a lot of data in the response. In the console there is an error in the angular code TypeError: Cannot read properties of undefined (reading 'name')
So it seems the Disk Usage UI was expecting a value that was not there. Of course, the console error could be from something else and not the Disk Usage.

@girish When the cache is invalid, it causes a runtime error, and the error prevents the refresh button from getting enabled. I'm asking for the refresh button to immediately enable in the handler, so if there is an error in the handler from invalid data, one may still click the refresh button.

Trying to change the storage path always errors with:

An error occurred during the data migration operation: External Error: Error migrating data directory: moveDataDir exited with code 1 signal null

@girish Well, it wasn't exactly a problem. I was just asking an important question, and wanted a confirmation that I guessed the right answer.

I noticed a lot of people using Minio. It seems most are using it for backups. Looking at their website it is really confusing what it actually does / is meant for. What is your use case? And if backups, what makes it better than doing backups without Minio?

@jdaviescoates In my limited experience, I've thought of S3 as being for static site hosting (i.e. the front end of any web app). What are some other "lots of things" that use S3?