The panel reports three statistics related to memory consumption:
real memory usage is considered RAM that cannot be used by other processes, as it has been reserved by the current process.
cache takes into consideration things like dirty pages and other transient items in your RAM. These pages can be cleared upon request by the kernel if an application requests to use more RAM.
real + cache
It's likely that your freshly installed machine simply has a high
cache usage but low
real usage. If this is the case (but
physical still reads 99%), you have nothing to worry about -- this is simply Linux performing a it should. If, instead, your
real usage is consuming the majority of your RAM, you do have problems. Consider using a program such as
htop to help you narrow down and identify the rogue application.
swizzin hasn't used the space, don't worry. By default, when using the ext4 partition format, the disk reserves 5% of the space in the partition for the potential scenario whereby the disk runs out of space. If this happens, and your whole server is formatted under a root partition scheme (i.e. no separate /home directory), your server will still have some space reserved to perform essential tasks such as (but not limited to): system updates, logging and various other things, such as bash auto(tab)-completion (crazy, right?).
Since the reservation is percentage based, the larger your partition, the higher the reserved space.
You can remove the reserved space on the partition
sda3 with the following command:
sudo tune2fs -m 0 /dev/sda3
You can also enter other non-zero values to customize the reserved space:
sudo tune2fs -m 1 /dev/sda3
Will reserve 1% instead.
It's unlikely that the partition on your server is sda3, so you'll need to use the command
lsblk to determine which partition exactly to modify.
Did you install the
quota package? You need to use the
setdisk script to define the limits per user. The default quota is undefined, which is the source of this error.
If you just installed every package just because and you don't actually need quotas, feel free to remove the package with
box remove quota
Please see the chapter above.
Please consult the Troubleshooting guide for more information.
You cannot run Swizzin in a docker. The way docker works does not mix well with the amount of different resources swizzin relies on that are present in a standard Debian/Ubuntu Installation.
Swizzin installs all applications in their non-containerized, bare-metal form. This for performance and maintainability reasons.