Update installs error message

Fleggy · 1. Dezember 2023

Been getting error messages when performing updates. The updates seem to work but I get an error each time.

After a recent hard drive issue, I have been redownloading most of my media but haven't really done anything with OMV, it's all been media downloads

To not exceed the character limit, I have removed some of the lines that repeat the message "dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device"

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::="--force-confold" dist-upgrade 2>&1' with exit code '100': Reading package lists...

Building dependency tree...

Reading state information...

Calculating upgrade...

The following packages will be upgraded:
  libnghttp2-14 openmediavault
Preconfiguring packages ...
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/2485 kB of archives.
After this operation, 7168 B of additional disk space will be used.
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 41943 files and directories currently installed.)
Preparing to unpack .../libnghttp2-14_1.43.0-1+deb11u1_amd64.deb ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Unpacking libnghttp2-14:amd64 (1.43.0-1+deb11u1) over (1.43.0-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Preparing to unpack .../openmediavault_6.9.9-1_all.deb ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Unpacking openmediavault (6.9.9-1) over (6.9.8-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up openmediavault (6.9.9-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Creating configuration database ...
Migrating configuration database ...
Setting up Salt environment ...
Processing system modifications ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up libnghttp2-14:amd64 (1.43.0-1+deb11u1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for rsyslog (8.2102.0-2+deb11u1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for libc-bin (2.31-13+deb11u7) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for openmediavault (6.9.9-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Restarting engine daemon ...
Updating workbench configuration files ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
E: Write error - ~LZMAFILE (28: No space left on device)

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::="--force-confold" dist-upgrade 2>&1' with exit code '100': Reading package lists...

Building dependency tree...

Reading state information...

Calculating upgrade...

The following packages will be upgraded:
  libnghttp2-14 openmediavault
Preconfiguring packages ...
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/2485 kB of archives.
After this operation, 7168 B of additional disk space will be used.
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 41943 files and directories currently installed.)
Preparing to unpack .../libnghttp2-14_1.43.0-1+deb11u1_amd64.deb ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Unpacking libnghttp2-14:amd64 (1.43.0-1+deb11u1) over (1.43.0-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Preparing to unpack .../openmediavault_6.9.9-1_all.deb ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Unpacking openmediavault (6.9.9-1) over (6.9.8-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up openmediavault (6.9.9-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Creating configuration database ...
Migrating configuration database ...
Setting up Salt environment ...
Processing system modifications ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Setting up libnghttp2-14:amd64 (1.43.0-1+deb11u1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for rsyslog (8.2102.0-2+deb11u1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for libc-bin (2.31-13+deb11u7) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Processing triggers for openmediavault (6.9.9-1) ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
Restarting engine daemon ...
Updating workbench configuration files ...
dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device
E: Write error - ~LZMAFILE (28: No space left on device) in /usr/share/openmediavault/engined/rpc/apt.inc:226
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): Engined\Rpc\Apt->Engined\Rpc\{closure}('/tmp/bgstatusEc...', '/tmp/bgoutputKe...')
#1 /usr/share/openmediavault/engined/rpc/apt.inc(229): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: Engined\Rpc\Apt->upgrade(NULL, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('upgrade', NULL, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Apt', 'upgrade', NULL, Array, 1)
#6 {main}

Alles anzeigen

chente · 1. Dezember 2023

It looks like your system drive is full.

Thema

[How-To] Fix full OS filesystem - GUI login loop

Symptoms

When you try to login to the GUI of OMV you are not being logged in, but the login page shows up again

Check, if a full root filesystem is the problem
ssh into your server (check the new user guide on how to ssh into your server) and run following command
df df will show you the usage of each filesystem
the output of df will look like this:
(Quelltext, 19 Zeilen)

The filesystem dev/sda1 which is mounted on "/" is the OS filesystem. The use of that filesystem is 100% --> the OS filesystem is…

macom

23. Juli 2020

Fleggy · 3. Dezember 2023

Zitat von chente

It looks like your system drive is full.

Thema

[How-To] Fix full OS filesystem - GUI login loop

Symptoms

When you try to login to the GUI of OMV you are not being logged in, but the login page shows up again

Check, if a full root filesystem is the problem
ssh into your server (check the new user guide on how to ssh into your server) and run following command
df df will show you the usage of each filesystem
the output of df will look like this:
(Quelltext, 19 Zeilen)

The filesystem dev/sda1 which is mounted on "/" is the OS filesystem. The use of that filesystem is 100% --> the OS filesystem is…

macom

23. Juli 2020

Code

 9.9 GiB [##########] /var
    2.8 GiB [##        ] /usr
  156.5 MiB [          ] /boot
    6.8 MiB [          ] /etc
    1.8 MiB [          ] /srv
  132.0 KiB [          ] /root
   16.0 KiB [          ] /opt
e  16.0 KiB [          ] /lost+found
    8.0 KiB [          ] /media
    8.0 KiB [          ] /export
    8.0 KiB [          ] /.cache
e   4.0 KiB [          ] /mnt
e   4.0 KiB [          ] /home
    4.0 KiB [          ]  .cloudcmd.json
@   0.0   B [          ]  initrd.img.old
@   0.0   B [          ]  initrd.img
@   0.0   B [          ]  vmlinuz.old
@   0.0   B [          ]  vmlinuz
@   0.0   B [          ]  libx32
@   0.0   B [          ]  lib64
@   0.0   B [          ]  lib32
@   0.0   B [          ]  sbin
@   0.0   B [          ]  lib
@   0.0   B [          ]  bin
>   0.0   B [          ] /tmp
>   0.0   B [          ] /sys
>   0.0   B [          ] /run
>   0.0   B [          ] /proc
>   0.0   B [          ] /dev

Alles anzeigen

This is what I get using the NCDU tool. My OS drive is a 128Gb SSD that is only using 12Gb - not sure how it can be full

macom · 3. Dezember 2023

Please post the output of df -h

Soma · 3. Dezember 2023

Zitat von Fleggy

dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device

This usually means your folder2ram is full, NOT the OS drive.

Search - openmediavault

How much memory do you have on your system?

Specs of the system?

Are you using the flash-memory plugin?

If yes, go to the Services-> Flashmemory and click sync all

Then try on CLI and post the output of:

sudo apt --list-upgradable

sudo omv-upgrade

chente · 3. Dezember 2023

Zitat von Soma

This usually means your folder2ram is full, NOT the OS drive.

I think you're right, this thread explains it. Why am I seeing all these "no space left on device" entries in the syslog?

Zitat von Soma

If yes, go to the Services-> Flashmemory and click sync all

What I don't understand is how sync all can help. As far as I know what it does is only copy the RAM to the disk. Or have I missed something else?

Soma · 3. Dezember 2023

Zitat von chente

As far as I know what it does is only copy the RAM to the disk.

The way I understand it, sync will release that space on RAM leaving it free again to other data.

Or not,

chente · 3. Dezember 2023

Zitat von Soma

The way I understand it, sync will release that space on RAM leaving it free again to other data.
Or not,

This is what I found:

Zitat von macom

That writes the ram to the drive, but does not free ram.

Fleggy · 3. Dezember 2023

Zitat von macom

Please post the output of df -h

Code

Filesystem                                  Size  Used Avail Use% Mounted on
udev                                        7.7G     0  7.7G   0% /dev
tmpfs                                       1.6G  151M  1.4G  10% /run
/dev/sdc2                                   109G   13G   90G  13% /
tmpfs                                       7.8G     0  7.8G   0% /dev/shm
tmpfs                                       5.0M     0  5.0M   0% /run/lock
/dev/sdb1                                   3.6T  978G  2.7T  27% /srv/dev-disk-                                                                                                             by-uuid-e009d604-e386-41f3-b38c-e5a2b78fab0b
/dev/sdf1                                   3.6T  1.1T  2.6T  30% /srv/dev-disk-                                                                                                             by-uuid-133a17c5-b885-4b45-ba92-29a07e02f3be
tmpfs                                       7.8G  5.2M  7.8G   1% /tmp
/dev/sdc1                                   511M  152K  511M   1% /boot/efi
folder2ram                                  7.8G  7.8G     0 100% /var/log
/dev/sda1                                   2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe
folder2ram                                  7.8G     0  7.8G   0% /var/tmp
folder2ram                                  7.8G  1.8M  7.8G   1% /var/lib/openm                                                                                                             ediavault/rrd
folder2ram                                  7.8G   24K  7.8G   1% /var/spool
folder2ram                                  7.8G   43M  7.7G   1% /var/lib/rrdca                                                                                                             ched
folder2ram                                  7.8G   12K  7.8G   1% /var/lib/monit
folder2ram                                  7.8G   28K  7.8G   1% /var/cache/sam                                                                                                             ba
192.168.1.252:/data/Documents                11T  5.8T  5.2T  53% /srv/remotemou                                                                                                             nt/documents
192.168.1.252:/data/Videos                   11T  5.8T  5.2T  53% /srv/remotemou                                                                                                             nt/FleggyNAS
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/689f54d41befc94d                                                                                                             d3b3b79000a12540278a478b9be87623b51f2498e9a6db08/merged
/dev/sde1                                   3.6T  2.2T  1.5T  60% /srv/dev-disk-                                                                                                             by-uuid-b774b14e-1d86-4200-b8d4-ae8806ffc6a2
Media:bcca7fce-b189-4760-b65f-39162d237790   11T  4.2T  6.7T  39% /srv/mergerfs/                                                                                                             Media
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/43bca4dac33514df                                                                                                             3a1b57efd99c42d9c54f2721a62baa63dec9e7cd0666ece1/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/238f8c7a5c06fbbd                                                                                                             8210b3d2b2b88bb34d339f5c02f3abba4e64f6165df103e7/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/11b90a32c9904236                                                                                                             b52dc8b074c28abd4a476b0e2774dd8e617510ca917e3085/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/4e862a25421b1c15                                                                                                             8e42ace7d3d33428ebd19aa58814d18b3bcf1534adf8ff57/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/2fdca26c0926fe0d                                                                                                             f9fc16b4a4ed894cdf159fe0079ac64221d29aa8e46ba48f/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/986e56f100f7db9a                                                                                                             9f8cb4bda5fa73f3d9f29b6382bfd1e29c89859b61b2a5b9/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/f77f815d5c435556                                                                                                             a15230840bdfc5cee6d0a7583a5bcfff0f076fd01d0926ef/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/67c9859b64b8446a                                                                                                             6b9337e54e50f9565ce47a72432a13a9e167ce24f235d14d/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/38913ccd03370d6e                                                                                                             1a31ffa0409387930e5efcd1c47a09e916a00f008bf9461d/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/b34d9a4e58132d0c                                                                                                             114da7312d5f8fa062dfd40769b4c2b7d414e81757f12c22/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/965d333a7d8489e4                                                                                                             5921c373f94670af5a05a332858cd36b58302211e594ed27/merged
overlay                                     2.7T  246G  2.5T   9% /srv/dev-disk-                                                                                                             by-uuid-68b6b54d-7eda-4545-b0cb-0100bff5f4fe/newdocker/overlay2/f63e2c7e4a9d1475                                                                                                             8e42e0e0f4b39e1be683d9852eabea92ad888cc1b907e473/merged

Alles anzeigen

Fleggy · 3. Dezember 2023

Zitat von Soma

This usually means your folder2ram is full, NOT the OS drive.
Search - openmediavault

How much memory do you have on your system?
Specs of the system?

Are you using the flash-memory plugin?
If yes, go to the Services-> Flashmemory and click sync all

Then try on CLI and post the output of:
sudo apt --list-upgradable
sudo omv-upgrade

Alles anzeigen

System is an i9-10900K with 16GB of RAM. I have done a sync all but it didn't change the log file size

Code

root@fleggyomv:~# sudo apt --list-upgradable
E: Command line option --list-upgradable is not understood in combination with the other options
root@fleggyomv:~# sudo omv-upgrade
Get:1 file:/var/cache/openmediavault/archives  InRelease
Ign:1 file:/var/cache/openmediavault/archives  InRelease
Get:2 file:/var/cache/openmediavault/archives  Release
Ign:2 file:/var/cache/openmediavault/archives  Release
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Hit:5 http://deb.debian.org/debian bullseye InRelease
Get:6 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:7 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:8 https://download.docker.com/linux/debian bullseye InRelease
Hit:9 https://openmediavault-plugin-developers.github.io/packages/debian shaitan InRelease
Hit:10 https://openmediavault.github.io/packages shaitan InRelease
Get:11 http://httpredir.debian.org/debian bullseye-backports InRelease [49.0 kB]
Hit:12 http://packages.openmediavault.org/public shaitan InRelease
Fetched 141 kB in 4s (39.5 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Alles anzeigen

Soma · 3. Dezember 2023

Zitat von Fleggy

I have done a sync all but it didn't change the log file size

I probably gave you a wrong apt command.

Writing from memory and on phone is not easy.

Well, at least, you have no error this time on the omv-upgrade.

Your /var/log is showing full and a 7.8Gb size.

You need to dig down and see which log is filling it.

Fleggy · 3. Dezember 2023

Zitat von Soma

I probably gave you a wrong apt command.
Writing from memory and on phone is not easy.

Well, at least, you have no error this time on the omv-upgrade.

Your /var/log is showing full and a 7.8Gb size.
You need to dig down and see which log is filling it.

Alles anzeigen

Using ncdu -x, this is as far as I can drill down

Code

--- /var/folder2ram/var/log -----------------------------------------------------------------------------------------------------------------------------------------------------------------
                         /..
    2.3 GiB [##########]  syslog
    2.3 GiB [######### ]  kern.log
    1.0 GiB [####      ]  syslog.1
    1.0 GiB [####      ]  kern.log.1
  640.0 MiB [##        ] /journal
  425.4 MiB [#         ]  messages
  188.7 MiB [          ]  messages.1
   22.8 MiB [          ]  daemon.log.1
   14.4 MiB [          ] /installer
    9.0 MiB [          ]  daemon.log
    1.9 MiB [          ]  syslog.4.gz
    1.4 MiB [          ]  syslog.2.gz
    1.4 MiB [          ]  daemon.log.4.gz
  832.0 KiB [          ]  daemon.log.2.gz
  752.0 KiB [          ] /nginx
  680.0 KiB [          ]  syslog.3.gz
  448.0 KiB [          ]  messages.4.gz
  444.0 KiB [          ]  daemon.log.3.gz
  428.0 KiB [          ]  kern.log.4.gz
  412.0 KiB [          ]  kern.log.2.gz
  304.0 KiB [          ]  messages.2.gz
  272.0 KiB [          ]  auth.log.1
  144.0 KiB [          ]  messages.3.gz
  128.0 KiB [          ]  auth.log

Alles anzeigen

Soma · 3. Dezember 2023

See the size of syslog and kern.log

They are big.

You can get some free space by deleting the .1 versions but you need to figure out what is spamming those files.

Update installs error message

votdev 2. Dezember 2023

Jetzt mitmachen!

Ähnliche Themen

How to install additional packages in Docker container?

Migrated existing drives to a new system, one full drive won't mount but is listed in disks and can ssh to it