[linux] Runtime journal is 27.7M, max 24.6M, 0B free.

[Geert Stappers]

On Sun, Aug 05, 2018 at 06:47:46PM +0200, Geert Stappers wrote:
> Hoi,
> 
> systemd-journald vind dat een bovengrens heeft van 24MB,
> gaat daar wel overheen en meldt 0 free.
> 
> Op die bovengrens op te vragen als die nog niet bereikt is?
} Hoe die bovengrens op te vragen als die nog niet bereikt is?
 
Sorry

> 
> <screenshot>
> $ systemctl status systemd-journald.service | cat
> * systemd-journald.service - Journal Service
>    Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled)
>    Aug 05 16:11:53 ardee systemd-journald[8105]: Journal started
> aug 05 16:11:53 ardee systemd-journald[8105]: Runtime journal (/run/log/journal/2bec7967cda2a874c8452dea0248e768) is 27.7M, max 24.6M, 0B free.
> ctive: active (running) since Sun 2018-08-05 16:11:53 UTC; 24min ago
>      Docs: man:systemd-journald.service(8)
>            man:journald.conf(5)
>  Main PID: 8105 (systemd-journal)
>    Status: "Processing requests..."
>    Memory: 760.0K
>    CGroup: /system.slice/systemd-journald.service
>            +- /lib/systemd/systemd-journald
> 
> aug 05 16:11:53 ardee systemd-journald[8105]: Journal started
> aug 05 16:11:53 ardee systemd-journald[8105]: Runtime journal (/run/log/journal/2bec7967cda2a874c8452dea0248e768) is 27.7M, max 24.6M, 0B free.
> </screenshot>
>            


Het opvragen disk gebruik lukt:

| $ du -h /run/log/journal/
| 28M	/run/log/journal/2bec7967cda2a874c8452dea0248e768
| 28M	/run/log/journal/
| $ journalctl --disk-usage
| Archived and active journals take up 27.7M in the file system.
| stappers op ardee:/etc/systemd


Zetten van "vacuum size" lukt, 
| $ sudo journalctl --vacuum-size 30M
| Vacuuming done, freed 0B of archived journals from /run/log/journal/2bec7967cda2a874c8452dea0248e768.


Maar hoe de bovengrens op te vragen??

<screenshot>
$ systemctl status systemd-journald.service | cat
* systemd-journald.service - Journal Service
   Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled)
   Active: active (running) since Sun 2018-08-05 16:11:53 UTC; 49min ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 8105 (systemd-journal)
   Status: "Processing requests..."
   Memory: 892.0K
   CGroup: /system.slice/systemd-journald.service
           +- /lib/systemd/systemd-journald

aug 05 16:11:53 ardee systemd-journald[8105]: Journal started
aug 05 16:11:53 ardee systemd-journald[8105]: Runtime journal (/run/log/journal/2bec7967cda2a874c8452dea0248e768) is 27.7M, max 24.6M, 0B free.
</screenshot>


En na een herstart
<screenshot>
stappers op ardee:/etc/systemd
$ sudo systemctl restart systemd-journald.service
stappers op ardee:/etc/systemd
$ systemctl status systemd-journald.service | cat
? systemd-journald.service - Journal Service
   Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled)
   Active: active (running) since Sun 2018-08-05 17:02:37 UTC; 3s ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 8696 (systemd-journal)
   Status: "Processing requests..."
   Memory: 540.0K
   CGroup: /system.slice/systemd-journald.service
           +- 8696 /lib/systemd/systemd-journald

aug 05 17:02:37 ardee systemd-journald[8696]: Journal started
aug 05 17:02:37 ardee systemd-journald[8696]: Runtime journal (/run/log/journal/2bec7967cda2a874c8452dea0248e768) is 27.7M, max 24.6M, 0B free.
</screenshot>

Waar komt de kunstmatige bovengrens van 24.6M  vandaan??



Groeten
Geert Stappers
-- 
Leven en laten leven