Fedora Online Forum

Il forum della comunità italiana di Fedora

#1 20-05-2019 10:16:50

skiava
Fedora nel sangue
Da Bari
Registrato: 23-05-2007
Messaggi: 1'909

Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

Ciao a tutti, dopo aver eseguito l'upgrade da Fedora 28 a 29 eseguito con successo mi trovo nel file di log ben 3.9 Gb e vorrei eliminarlo, riporto di seguito l'output di:

[[email protected] skiava]# journalctl --disk-usage
Archived and active journals take up 3.9G in the file system.
[[email protected] skiava]#  journalctl --list-boots --no-pager
-13 15710c5de3bc4fdaadecc5b607ed0fb5 Mon 2019-04-22 18:20:11 CEST—Wed 2019-04-24 08:24:42 CEST
-12 7ac9bc4fd59a4ebe987d8cdadb675523 Wed 2019-04-24 10:26:22 CEST—Wed 2019-04-24 11:01:12 CEST
-11 8a18c9b249ce439e8a068c203754046c Wed 2019-04-24 13:03:14 CEST—Mon 2019-04-29 08:42:11 CEST
-10 af75a0fe934646b5be3e65ee1b6d6710 Mon 2019-04-29 10:43:51 CEST—Mon 2019-04-29 18:03:37 CEST
 -9 eb8e254d86ac43fcb4c22567c574ec83 Thu 2019-05-02 10:19:46 CEST—Thu 2019-05-09 08:31:50 CEST
 -8 ba8031c6fd754b5ca6c4143502a8e3a6 Thu 2019-05-09 10:33:29 CEST—Fri 2019-05-10 13:18:13 CEST
 -7 10eed96e4e2946ba8bc57bb16ae16fc6 Fri 2019-05-10 15:19:55 CEST—Mon 2019-05-13 16:26:15 CEST
 -6 c308bd2b25d843b39f77c640c8204b8c Mon 2019-05-13 18:28:09 CEST—Mon 2019-05-13 17:50:18 CEST
 -5 35f5540c103d4a4594529db161724fd5 Mon 2019-05-13 19:52:26 CEST—Tue 2019-05-14 03:48:04 CEST
 -4 8e68331376bc457aa12bf8298ebc1af4 Tue 2019-05-14 05:50:43 CEST—Tue 2019-05-14 03:52:38 CEST
 -3 a6665cf2195447379950dca048ae9306 Tue 2019-05-14 05:56:23 CEST—Fri 2019-05-17 09:16:48 CEST
 -2 aeee3a4247fa45948cabfe9b46794cde Fri 2019-05-17 12:11:49 CEST—Mon 2019-05-20 09:43:12 CEST
 -1 3a04c3d627cc48dda1d943c99352afcf Mon 2019-05-20 11:44:52 CEST—Mon 2019-05-20 10:54:16 CEST
  0 0556c8212fbc4ed7b6cded8e8d7fd4b6 Mon 2019-05-20 12:55:58 CEST—Mon 2019-05-20 11:01:01 CEST
[[email protected] skiava]# journalctl | head -n 1
-- Logs begin at Mon 2019-04-22 18:20:11 CEST, end at Mon 2019-05-20 11:01:01 CEST. --
[[email protected] skiava]# 

ho trovato in Fol questo post che si era già discusso tempo fa:

https://forum.fedoraonline.it/viewtopic.php?id=25362

ma non ho capito quale data devo inserire alla fine della stringa? ovvero:

# journalctl --vacuum-time [data]

qualcuno mi potrebbe aiutare.
Grazie in anticipo.

Ultima modifica di skiava (20-05-2019 12:22:55)


L I N U X - coming soon on every computer!!

Non in linea

#2 20-05-2019 12:14:41

JackDaniels
Appena sbarcato sul forum
Da Cosenza
Registrato: 04-03-2019
Messaggi: 73

Re: Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

skiava ha scritto:

Ciao a tutti, dopo aver eseguito l'upgrade da Fedora 28 a 29 eseguito con successo mi trovo nel log ben 3.9 Gb e vorrei eliminarlo, riporto di seguito l'output di:

[[email protected] skiava]# journalctl --disk-usage
Archived and active journals take up 3.9G in the file system.
[[email protected] skiava]#  journalctl --list-boots --no-pager
-13 15710c5de3bc4fdaadecc5b607ed0fb5 Mon 2019-04-22 18:20:11 CEST—Wed 2019-04-24 08:24:42 CEST
-12 7ac9bc4fd59a4ebe987d8cdadb675523 Wed 2019-04-24 10:26:22 CEST—Wed 2019-04-24 11:01:12 CEST
-11 8a18c9b249ce439e8a068c203754046c Wed 2019-04-24 13:03:14 CEST—Mon 2019-04-29 08:42:11 CEST
-10 af75a0fe934646b5be3e65ee1b6d6710 Mon 2019-04-29 10:43:51 CEST—Mon 2019-04-29 18:03:37 CEST
 -9 eb8e254d86ac43fcb4c22567c574ec83 Thu 2019-05-02 10:19:46 CEST—Thu 2019-05-09 08:31:50 CEST
 -8 ba8031c6fd754b5ca6c4143502a8e3a6 Thu 2019-05-09 10:33:29 CEST—Fri 2019-05-10 13:18:13 CEST
 -7 10eed96e4e2946ba8bc57bb16ae16fc6 Fri 2019-05-10 15:19:55 CEST—Mon 2019-05-13 16:26:15 CEST
 -6 c308bd2b25d843b39f77c640c8204b8c Mon 2019-05-13 18:28:09 CEST—Mon 2019-05-13 17:50:18 CEST
 -5 35f5540c103d4a4594529db161724fd5 Mon 2019-05-13 19:52:26 CEST—Tue 2019-05-14 03:48:04 CEST
 -4 8e68331376bc457aa12bf8298ebc1af4 Tue 2019-05-14 05:50:43 CEST—Tue 2019-05-14 03:52:38 CEST
 -3 a6665cf2195447379950dca048ae9306 Tue 2019-05-14 05:56:23 CEST—Fri 2019-05-17 09:16:48 CEST
 -2 aeee3a4247fa45948cabfe9b46794cde Fri 2019-05-17 12:11:49 CEST—Mon 2019-05-20 09:43:12 CEST
 -1 3a04c3d627cc48dda1d943c99352afcf Mon 2019-05-20 11:44:52 CEST—Mon 2019-05-20 10:54:16 CEST
  0 0556c8212fbc4ed7b6cded8e8d7fd4b6 Mon 2019-05-20 12:55:58 CEST—Mon 2019-05-20 11:01:01 CEST
[[email protected] skiava]# journalctl | head -n 1
-- Logs begin at Mon 2019-04-22 18:20:11 CEST, end at Mon 2019-05-20 11:01:01 CEST. --
[[email protected] skiava]# 

ho trovato in Fol questo post aperto da me qualche tempo fa e che si era già discusso ma non ho capito il comando da eseguire per l'eliminare il file di log:

https://forum.fedoraonline.it/viewtopic.php?id=25362

credo che la stringa dovrebbe essere la seguente:

# journalctl --vacuum-time [data]

non ricordo la procedura ovvero quale data devo mettere per elimianre il file di log?
qualcuno mi potrebbe aiutare.
Grazie in anticipo.

Non basta eliminare il contenuto della cartella?

 /var/log 

Non in linea

#3 20-05-2019 12:16:15

skiava
Fedora nel sangue
Da Bari
Registrato: 23-05-2007
Messaggi: 1'909

Re: Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

Non so....ma avendo fatto l'upgrade sarebbe opportuno eliminare anche il journal come già eseguito le altre volte.

Ultima modifica di skiava (20-05-2019 12:17:37)


L I N U X - coming soon on every computer!!

Non in linea

#4 20-05-2019 12:19:12

JackDaniels
Appena sbarcato sul forum
Da Cosenza
Registrato: 04-03-2019
Messaggi: 73

Re: Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

skiava ha scritto:

Non so....ma avendo fatto l'upgrade sarebbe opportuno eliminare anche il journal come già eseguito le altre volte.

 --disk-usage            Show total disk usage of all journal files
     --vacuum-size=BYTES     Reduce disk usage below specified size
     --vacuum-files=INT      Leave only the specified number of journal files
     --vacuum-time=TIME      Remove journal files older than specified time

Non in linea

#5 20-05-2019 12:20:56

skiava
Fedora nel sangue
Da Bari
Registrato: 23-05-2007
Messaggi: 1'909

Re: Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

JackDaniels ha scritto:
skiava ha scritto:

Non so....ma avendo fatto l'upgrade sarebbe opportuno eliminare anche il journal come già eseguito le altre volte.

 --disk-usage            Show total disk usage of all journal files
     --vacuum-size=BYTES     Reduce disk usage below specified size
     --vacuum-files=INT      Leave only the specified number of journal files
     --vacuum-time=TIME      Remove journal files older than specified time

quindi quale dei tre dovrei utilizzare, secondo te?
forse il terzo " --vacuum-time=TIME      Remove journal files older than specified time" ma quale data devo inserire?
e' questo il mio dubbio...

Ultima modifica di skiava (20-05-2019 12:25:23)


L I N U X - coming soon on every computer!!

Non in linea

#6 20-05-2019 12:24:57

JackDaniels
Appena sbarcato sul forum
Da Cosenza
Registrato: 04-03-2019
Messaggi: 73

Re: Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

skiava ha scritto:
JackDaniels ha scritto:
skiava ha scritto:

Non so....ma avendo fatto l'upgrade sarebbe opportuno eliminare anche il journal come già eseguito le altre volte.

 --disk-usage            Show total disk usage of all journal files
     --vacuum-size=BYTES     Reduce disk usage below specified size
     --vacuum-files=INT      Leave only the specified number of journal files
     --vacuum-time=TIME      Remove journal files older than specified time

quindi quale dei tre dovrei utilizzare, secondo te?

 --vacuum-time=1 

elimini tutti i log piu vecchi di 1 giorno oppure metti 0 e sei apposto :-P

Non in linea

#7 20-05-2019 12:26:22

skiava
Fedora nel sangue
Da Bari
Registrato: 23-05-2007
Messaggi: 1'909

Re: Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

Riporto di seguito l'output di:

[[email protected] skiava]# journalctl --vacuum-time=1
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]0d7bc2828.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]872204cc957f.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]20683fcb9.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]872333371766.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]334b01483.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]87246206af9f.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]463ca9a38.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]87258fb32b07.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]59157cf85.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]8726bd47340f.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]6bebb1858.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]8727ec5d8f42.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]7edbe083b.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]87291938f2a2.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]91ab716b4.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]872a49fb833c.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]a4b5ef45a.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]872b7a606a8d.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]b7bdd419f.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]872cabe6f577.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]cad2cb8b6.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]872dde3def99.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]ddf7709d1.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]872f11f7ae81.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]f13c008b2.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]87304363b340.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]0450384f9.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]873173fc9e60.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]175aef60a.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]8732a3ef90c5.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]2a5a60003.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]8733d2ae13d7.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]3d4074642.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]87350084d929.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]501db0567.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]87362ed42c11.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]6305f06e8.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]87375ae62f0b.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]75c7609fa.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]873888cd942f.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]88a68578b.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]8739b591850a.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]9b635bb25.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]873ae3c837fd.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]ae569dbbe.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]873c10c8b543.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]c1241bb69.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]873d3f129162.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]d40d5c6f6.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]873e6d9f4c93.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]e6f349d8d.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]~ (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]~ (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]~ (16.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]8742fd51b3c8.journal (16.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]34c0e3ae0.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]1a1d2e694.journal (104.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]29e8f0ae4.journal (24.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]8832a39eb5f7.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]~ (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]~ (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]~ (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]~ (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]104384ae5.journal (8.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]890bc532ea22.journal (128.0M).
Deleted archived journal /var/log/journal/518952f59f2c4516be62a41118962331/[email protected]bcffcea33.journal (8.0M).
Vacuuming done, freed 3.9G of archived journals from /var/log/journal/518952f59f2c4516be62a41118962331.
[[email protected] skiava]# journalctl --disk-usage
Archived and active journals take up 40.0M in the file system.
[[email protected] skiava]#  journalctl --list-boots --no-pager
-3 a6665cf2195447379950dca048ae9306 Fri 2019-05-17 09:15:50 CEST—Fri 2019-05-17 09:16:48 CEST
-2 aeee3a4247fa45948cabfe9b46794cde Fri 2019-05-17 12:11:49 CEST—Mon 2019-05-20 09:43:12 CEST
-1 3a04c3d627cc48dda1d943c99352afcf Mon 2019-05-20 11:44:52 CEST—Mon 2019-05-20 10:54:16 CEST
 0 0556c8212fbc4ed7b6cded8e8d7fd4b6 Mon 2019-05-20 12:55:58 CEST—Mon 2019-05-20 13:21:59 CEST
[[email protected] skiava]# journalctl | head -n 1
-- Logs begin at Fri 2019-05-17 09:15:50 CEST, end at Mon 2019-05-20 13:21:59 CEST. --
[[email protected] skiava]# exit

quindi ho cancellato quasi tutto lasciando quelli dal 17/5/19 e al 21/05/19 ma, scusami, se metto (--vacuum-time=0) invece di "1" e si cancella tutto che succede?

[[email protected] skiava]# journalctl --disk-usage
Archived and active journals take up 136.0M in the file system.
[[email protected] skiava]# journalctl --vacuum-time=1
Vacuuming done, freed 0B of archived journals from /var/log/journal/518952f59f2c4516be62a41118962331.
[[email protected] skiava]# journalctl --disk-usage
Archived and active journals take up 136.0M in the file system.
[[email protected] skiava]#  journalctl --list-boots --no-pager
-5 a6665cf2195447379950dca048ae9306 Fri 2019-05-17 09:15:50 CEST—Fri 2019-05-17 09:16:48 CEST
-4 aeee3a4247fa45948cabfe9b46794cde Fri 2019-05-17 12:11:49 CEST—Mon 2019-05-20 09:43:12 CEST
-3 3a04c3d627cc48dda1d943c99352afcf Mon 2019-05-20 11:44:52 CEST—Mon 2019-05-20 10:54:16 CEST
-2 0556c8212fbc4ed7b6cded8e8d7fd4b6 Mon 2019-05-20 12:55:58 CEST—Mon 2019-05-20 16:08:42 CEST
-1 910b42e081084101aa27a934efc37499 Mon 2019-05-20 18:15:36 CEST—Tue 2019-05-21 11:16:19 CEST
 0 00fdae8bc5984298bd57f6671fb83d1a Tue 2019-05-21 13:18:01 CEST—Tue 2019-05-21 11:33:12 CEST
[[email protected] skiava]# journalctl | head -n 1
-- Logs begin at Fri 2019-05-17 09:15:50 CEST, end at Tue 2019-05-21 11:33:12 CEST. --
[[email protected] skiava]# 

mi rimane 136 Mb che devo fare?
lasciarlo cosi o cancellare tutto?

Ultima modifica di skiava (21-05-2019 10:49:13)


L I N U X - coming soon on every computer!!

Non in linea

#8 21-05-2019 11:46:19

JackDaniels
Appena sbarcato sul forum
Da Cosenza
Registrato: 04-03-2019
Messaggi: 73

Re: Dopo Upgrade da 28 a 29 mi trovo con 3.9 Gb nel log del journal

Se metti 0 dovrebbe eliminare tutto ma in ogni caso se vai in /var/log/journal/ trovi i file

qui spiegano

quindi in linea di massima:

 sudo rm -rf /var/log/journal/* && sudo systemctl restart systemd-journald.service 

Ultima modifica di JackDaniels (21-05-2019 11:58:24)

Non in linea

Piè di pagina