[Tecnica] Xubuntu con HD pieno di LOG

Freeze NorthPole freeze a siena.linux.it
Mar 11 Set 2012 12:29:29 BST


Ciao a tutti
un rapido update:

ho controllato con il comando
ps ax|grep cron

e il CRON sembra esserci  anche se era in Sleep

ho lanciato  un logrotate -vf logtotate.con > file.txt

stasera controllo se ho avuto miglioramenti,
se fosse il logrotate "emozionato" come lo ripristino?


Grazie a tutti
Freeze
2012/9/9 Freeze NorthPole <freeze782 a gmail.com>:
> Perfetto grazie mille, ora studio per capire se e` attivo
> nel mentre che stuido qualcuno ci ha capito nulla di quel log? non ho
> quel livello di conoscenza per poterlo leggere
>
> Grazie ancora a tutti :)
>
> Davide
>
>
> 2012/9/7 roberto <roberto.volpini a valdelsa.net>:
>> ciao per quello che riguarda cron.....non ricordo come va configurato....per
>> cui qui sotto il link di riferimento.....
>>
>> http://wiki.ubuntu-it.org/AmministrazioneSistema/Cron
>>
>> a presto e spero che possa esserti di aiuto :-)
>>
>>
>>
>> Il 06/09/12 21.48, Freeze NorthPole ha scritto:
>>
>>> Ciao,
>>> ho fatto quanto mi hai suggerito
>>> ma non ci ho capito nulla per cui abuso della vostra cortesia e vi
>>> posto qui stralci del risultato, stralci perche` quando provavo a fare
>>> tail -n100>  log_mio.txt mi dava errore
>>>
>>> @ROberto CRON e` presente...
>>>
>>>
>>> Grazie a tutti
>>> Freeze
>>>
>>>
>>> -- inizio log--
>>> Sep  6 21:04:38 xx kernel: [    0.100283] pci 0000:00:01.0:   bridge
>>> window [mem 0xf4000000-0xf5dfffff]
>>> Sep  6 21:04:38 xx kernel: [    0.100292] pci 0000:00:01.0:   bridge
>>> window [mem 0xf5f00000-0xf7ffffff pref]
>>> Sep  6 21:04:38 xx kernel: [    0.100347] pci 0000:02:0b.0:
>>> [1516:0803] type 0 class 0x000200
>>> Sep  6 21:04:38 xx kernel: [    0.100373] pci 0000:02:0b.0: reg 10:
>>> [io  0xd800-0xd8ff]
>>> Sep  6 21:04:38 xx kernel: [    0.100388] pci 0000:02:0b.0: reg 14:
>>> [mem 0xf3800000-0xf38003ff]
>>> Sep  6 21:04:38 xx kernel: [    0.100441] pci 0000:02:0b.0: reg 30:
>>> [mem 0x00000000-0x0000ffff pref]
>>> Sep  6 21:04:38 xx kernel: [    0.100468] pci 0000:02:0b.0: supports D1
>>> Sep  6 21:04:38 xx kernel: [    0.100474] pci 0000:02:0b.0: PME#
>>> supported from D1 D3hot D3cold
>>> Sep  6 21:04:38 xx kernel: [    0.100483] pci 0000:02:0b.0: PME# disabled
>>> Sep  6 21:04:38 xx kernel: [    0.100525] pci 0000:00:1e.0: PCI bridge
>>> to [bus 02-02] (subtractive decode)
>>> Sep  6 21:04:38 xx kernel: [    0.100535] pci 0000:00:1e.0:   bridge
>>> window [io  0xd000-0xdfff]
>>> Sep  6 21:04:38 xx kernel: [    0.100544] pci 0000:00:1e.0:   bridge
>>> window [mem 0xf3800000-0xf3ffffff]
>>> Sep  6 21:04:38 xx kernel: [    0.100554] pci 0000:00:1e.0:   bridge
>>> window [mem 0xf5e00000-0xf5efffff pref]
>>> Sep  6 21:04:38 xx kernel: [    0.100561] pci 0000:00:1e.0:   bridge
>>> window [io  0x0000-0xffff] (subtractive deco
>>> de)
>>> Sep  6 21:04:38 xx kernel: [    0.100568] pci 0000:00:1e.0:   bridge
>>> window [mem 0x00000000-0xffffffff] (subtract
>>> ive decode)
>>> Sep  6 21:04:38 xx kernel: [    0.100589] pci_bus 0000:00: on NUMA node 0
>>> Sep  6 21:04:38 xx kernel: [    0.100600] ACPI: PCI Interrupt Routing
>>> Table [\_SB_.PCI0._PRT]
>>> Sep  6 21:04:38 xx kernel: [    0.100707] ACPI: PCI Interrupt Routing
>>> Table [\_SB_.PCI0.PCI1._PRT]
>>> Sep  6 21:04:38 xx kernel: [    0.100774] ACPI: PCI Interrupt Routing
>>> Table [\_SB_.PCI0.PCI2._PRT]
>>> Sep  6 21:04:38 xx kernel: [    0.103054] ACPI: PCI Interrupt Link
>>> [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
>>> Sep  6 21:04:38 xx kernel: [    0.103209] ACPI: PCI Interrupt Link
>>> [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
>>> Sep  6 21:04:38 xx kernel: [    0.103324] ACPI: PCI Interrupt Link
>>> [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, d
>>> isabled.
>>> Sep  6 21:04:38 xx kernel: [    0.103460] ACPI: PCI Interrupt Link
>>> [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
>>> Sep  6 21:04:38 xx kernel: [    0.103574] ACPI: PCI Interrupt Link
>>> [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, d
>>> isabled.
>>> Sep  6 21:04:38 xx kernel: [    0.103690] ACPI: PCI Interrupt Link
>>> [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, d
>>> isabled.
>>> Sep  6 21:04:38 xx kernel: [    0.105197] usbcore: registered new
>>> interface driver hub
>>> Sep  6 21:04:38 xx kernel: [    0.105288] usbcore: registered new
>>> device driver usb
>>> Sep  6 21:04:38 xx kernel: [    0.105610] wmi: Mapper loaded
>>> Sep  6 21:04:38 xx kernel: [    0.105619] PCI: Using ACPI for IRQ routing
>>> Sep  6 21:04:38 xx kernel: [    0.105632] PCI: pci_cache_line_size set
>>> to 64 bytes
>>> Sep  6 21:04:38 xx kernel: [    0.105710] reserve RAM buffer:
>>> 000000000009fc00 - 000000000009ffff
>>> Sep  6 21:04:38 xx kernel: [    0.105719] reserve RAM buffer:
>>> 000000001fffc000 - 000000001fffffff
>>> Sep  6 21:04:38 xx kernel: [    0.106002] NetLabel: Initializing
>>> Sep  6 21:04:38 xx kernel: [    0.106009] NetLabel:  domain hash size =
>>> 128
>>> Sep  6 21:04:38 xx kernel: [    0.106017] NetLabel:  protocols =
>>> UNLABELED CIPSOv4
>>> Sep  6 21:04:38 xx kernel: [    0.106046] NetLabel:  unlabeled traffic
>>> allowed by default
>>> Sep  6 21:04:38 xx kernel: [    0.124748] AppArmor: AppArmor Filesystem
>>> Enabled
>>> Sep  6 21:04:38 xx kernel: [    0.124849] pnp: PnP ACPI init
>>> Sep  6 21:04:38 xx kernel: [    0.124901] ACPI: bus type pnp registered
>>> Sep  6 21:04:38 xx kernel: [    0.125133] pnp 00:00: [mem
>>> 0x00000000-0x0009ffff]
>>> Sep  6 21:04:38 xx kernel: [    0.125142] pnp 00:00: [mem
>>> 0x000f0000-0x000fffff]
>>> Sep  6 21:04:38 xx kernel: [    0.125149] pnp 00:00: [mem
>>> 0x00100000-0x1fffffff]
>>> Sep  6 21:04:38 xx kernel: [    0.125156] pnp 00:00: [mem
>>> 0xfec00000-0xfec000ff]
>>> Sep  6 21:04:38 xx kernel: [    0.125162] pnp 00:00: [mem
>>> 0xfee00000-0xfee00fff]
>>> Sep  6 21:04:38 xx kernel: [    0.125293] system 00:00: [mem
>>> 0x00000000-0x0009ffff] could not be reserved
>>> Sep  6 21:04:38 xx kernel: [    0.125303] system 00:00: [mem
>>> 0x000f0000-0x000fffff] could not be reserved
>>> Sep  6 21:04:38 xx kernel: [    0.125312] system 00:00: [mem
>>> 0x00100000-0x1fffffff] could not be reserved
>>> Sep  6 21:04:38 xx kernel: [    0.125321] system 00:00: [mem
>>> 0xfec00000-0xfec000ff] could not be reserved
>>> Sep  6 21:04:38 xx kernel: [    0.125329] system 00:00: [mem
>>> 0xfee00000-0xfee00fff] has been reserved
>>> Sep  6 21:04:38 xx kernel: [    0.125340] system 00:00: Plug and Play
>>> ACPI device, IDs PNP0c01 (active)
>>> Sep  6 21:04:38 xx kernel: [    0.125826] pnp 00:01: [bus 00-ff]
>>> Sep  6 21:04:38 xx kernel: [    0.125835] pnp 00:01: [io  0x0cf8-0x0cff]
>>> Sep  6 21:04:38 xx kernel: [    0.125841] pnp 00:01: [io  0x0000-0x0cf7
>>> window]
>>> Sep  6 21:04:38 xx kernel: [    0.125848] pnp 00:01: [io  0x0d00-0xffff
>>> window]
>>> Sep  6 21:04:38 xx kernel: [    0.126086] pnp 00:02: [mem
>>> 0xfff80000-0xffffffff]
>>> Sep  6 21:04:38 xx kernel: [    0.126092] pnp 00:02: [mem
>>> 0xffb80000-0xffbfffff]
>>> Sep  6 21:04:38 xx kernel: [    0.126200] system 00:02: [io
>>> 0xe400-0xe47f] has been reserved
>>> Sep  6 21:04:38 xx kernel: [    0.126209] system 00:02: [io
>>> 0xe800-0xe81f] could not be reserved
>>> Sep  6 21:04:38 xx kernel: [    0.126218] system 00:02: [io
>>> 0xec00-0xec3f] has been reserved
>>> Sep  6 21:04:38 xx kernel: [    0.126227] system 00:02: [mem
>>> 0xfff80000-0xffffffff] could not be reserved
>>> Sep  6 21:04:38 xx kernel: [    0.126236] system 00:02: [mem
>>> 0xffb80000-0xffbfffff] has been reserved
>>> Sep  6 21:04:38 xx kernel: [    0.126245] system 00:02: Plug and Play
>>> ACPI device, IDs PNP0c02 (active)
>>> Sep  6 21:04:38 xx kernel: [    0.126312] pnp 00:03: [io  0x0010-0x001f]
>>> Sep  6 21:04:38 xx kernel: [    0.126319] pnp 00:03: [io  0x0022-0Sep
>>> 6 21:04:48 xx kernel: [   24.350272] [drm]
>>>   nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0)
>>> Sep  6 21:04:48 xx kernel: [   24.350287] [drm] nouveau 0000:01:00.0:
>>> Output VGA-1 is running on CRTC 0 using out
>>> put A
>>> Sep  6 21:04:48 xx kernel: [   25.003732] audit_printk_skb: 6
>>> callbacks suppressed
>>> Sep  6 21:04:48 xx kernel: [   25.003741] type=1400
>>> audit(1346958288.899:14): apparmor="STATUS" operation="profil
>>> e_replace" name="/usr/lib/cups/backend/cups-pdf" pid=1096
>>> comm="apparmor_parser"
>>> Sep  6 21:04:48 xx kernel: [   25.009707] type=1400
>>> audit(1346958288.907:15): apparmor="STATUS" operation="profil
>>> e_replace" name="/usr/sbin/cupsd" pid=1096 comm="apparmor_parser"
>>> Sep  6 21:04:49 xx kernel: [   25.370444] EXT4-fs (sda1): re-mounted.
>>> Opts: errors=remount-ro,commit=0
>>> Sep  6 21:04:50 xx kernel: [   26.759948] usb 2-2.1: usbfs: interface
>>> 0 claimed by usblp while 'usb' sets config
>>> #1
>>> Sep  6 21:04:50 xx kernel: [   27.000034] eth0: no IPv6 routers present
>>> Sep  6 21:04:57 xx kernel: [   33.595148] EXT4-fs (sda1): re-mounted.
>>> Opts: errors=remount-ro,commit=0
>>> Sep  6 21:05:07 xx kernel: [   43.135437] cfg80211: Found new beacon
>>> on frequency: 2472 MHz (Ch 13) on phy0
>>> Sep  6 21:06:08 xx kernel: [  104.905058] firefox[1657]: segfault at 4
>>> ip 00931496 sp bf9933b0 error 4 in nouveau
>>> _vieux_dri.so[91a000+34000]
>>> Sep  6 21:15:26 xx kernel: [  662.513047] handle_rx_packet: invalid,
>>> small RX packet : 1
>>> Sep  6 21:16:23 xx kernel: [  719.283571] handle_rx_packet: invalid,
>>> small RX packet : 1
>>>
>>>
>>>
>>> 2012/9/4 Martino di Filippo<puntodifuga a gmail.com>:
>>>>
>>>> Userei `tail -n100 /var/log/kern.log` per controllare cosa 
>>>> effettivamente
>>>> presente nei log. Dovrebbe essere facile risalire alla causa dei messaggi
>>>> e
>>>> sistemarla.
>>>>
>>>> Ciao!
>>>>
>>>> On Sep 4, 2012 8:19 PM, "Freeze NorthPole"<freeze a siena.linux.it>  wrote:
>>>>>
>>>>> Ciao a tutti,
>>>>> ho un amico con il seguente problemino
>>>>>
>>>>> il pc in questione ha 40 GB di HD da qualche giorno sta riscontrando
>>>>> dei problemi dovuti all HD pieno al 100%
>>>>>
>>>>> ieri sera ho spostato la cartella di thunderbird che occupava circa 11
>>>>> GB
>>>>> oggi dopo aver fatto della semplice navigazione, vedo che sono liberi
>>>>> solo 874 MB
>>>>> --- estrazione dati comando --
>>>>> xxx a XX:/var/log$ df -h
>>>>> File system            Dim. Usati Disp. Uso% Montato su
>>>>> /dev/sda1              38G   35G  874M  98% /
>>>>> none                  242M  684K  241M   1% /dev
>>>>> none                  249M  116K  248M   1% /dev/shm
>>>>> none                  249M  436K  248M   1% /var/run
>>>>> none                  249M     0  249M   0% /var/lock
>>>>> /dev/sdc1              85G  8,3G   77G  10% /media/AE981DE8981DAFB7
>>>>> --- fine estrazione dati comando --
>>>>>
>>>>> lanciando il comando :  sudo du -h --max-dept=1
>>>>>
>>>>> ho visto che la cartella VAR  quella che occupa pi di tutto
>>>>> --- estrazione dati comando --
>>>>> XX a xx:/$ sudo du -h --max-dept=1
>>>>> 14M     ./etc
>>>>> 4,0K    ./srv
>>>>> 4,0K    ./mnt
>>>>> 4,0K    ./cdrom
>>>>> 292K    ./tmp
>>>>> 31G     ./var
>>>>> --- fine estrazione dati comando --
>>>>>
>>>>>
>>>>>
>>>>> --- estrazione dati comando --
>>>>> XXXXXX a XX:/var$ sudo du -h --max-dept=1
>>>>> 3,7M    ./backups
>>>>> 16K     ./tmp
>>>>> 140M    ./cache
>>>>> 4,0K    ./local
>>>>> 12K     ./games
>>>>> 4,0K    ./crash
>>>>> 436K    ./run
>>>>> 0       ./lock
>>>>> 149M    ./lib
>>>>> 2,1M    ./spool
>>>>> 4,0K    ./opt
>>>>> 30G     ./log
>>>>> 4,0K    ./mail
>>>>> 31G     .
>>>>> --- fine estrazione dati comando --
>>>>>
>>>>> eseguendo un ls -lsSh
>>>>>
>>>>> vedo che ci sono log  enormi che non mi spiego, anche perch  un pc
>>>>> uso ufficio non server
>>>>>
>>>>> --- estrazione dati comando --
>>>>>
>>>>> xxxxx a xxx:/var/log$ ls -lsSh
>>>>> totale 30G
>>>>>   11G -rw-r----- 1 syslog            adm   11G 2012-09-04 20:19 kern.log
>>>>> 7,8G -rw-r----- 1 syslog            adm  7,8G 2012-09-03 10:03
>>>>> kern.log.1
>>>>> 5,7G -rw-r----- 1 syslog            adm  5,7G 2012-09-04 08:01 syslog.1
>>>>> 4,6G -rw-r----- 1 syslog            adm  4,6G 2012-09-04 20:19 syslog
>>>>> 409M -rw-r----- 1 syslog            adm  409M 2012-07-30 10:01
>>>>> kern.log.4.gz
>>>>> 363M -rw-r----- 1 syslog            adm  363M 2012-08-10 09:04
>>>>> kern.log.3.gz
>>>>> 302M -rw-r----- 1 syslog            adm  302M 2012-08-29 20:25
>>>>> syslog.6.gz
>>>>> 302M -rw-r----- 1 syslog            adm  302M 2012-08-29 20:44
>>>>> kern.log.2.gz
>>>>> 226M -rw-r----- 1 syslog            adm  226M 2012-09-01 07:35
>>>>> syslog.3.gz
>>>>> 155M -rw-r----- 1 syslog            adm  155M 2012-08-31 09:28
>>>>> syslog.4.gz
>>>>>   29M -rw-r----- 1 syslog            adm   29M 2012-09-03 09:47
>>>>> syslog.2.gz
>>>>> 884K -rw-r----- 1 syslog            adm  882K 2012-08-30 09:23
>>>>> syslog.5.gz
>>>>>   40K -rw-rw-r-- 1 root              utmp 286K 2012-09-04 19:36 lastlog
>>>>> --- fine estrazione dati comando --
>>>>>
>>>>> avete suggerimenti da darmi per capire che succede e come posso
>>>>> risolvere il problemino?
>>>>>
>>>>>
>>>>> ecco i dettagli sul sistema operativo montato
>>>>>
>>>>> --- inzio dettagli --
>>>>> xxxx a xxx:/var/log$ lsb_release -a
>>>>> No LSB modules are available.
>>>>> Distributor ID: Ubuntu
>>>>> Description:    Ubuntu 11.04
>>>>> Release:        11.04
>>>>> Codename:       natty
>>>>> ---fine dettagli --
>>>>>
>>>>>
>>>>> Grazie Mille a tutti
>>>>> Freeze
>>>>> _______________________________________________
>>>>> Tecnica mailing list
>>>>> Tecnica a liste.siena.linux.it
>>>>> http://liste.siena.linux.it/cgi-bin/mailman/listinfo/tecnica
>>>>
>>>>
>>>> _______________________________________________
>>>> Tecnica mailing list
>>>> Tecnica a liste.siena.linux.it
>>>> http://liste.siena.linux.it/cgi-bin/mailman/listinfo/tecnica
>>>>
>>> _______________________________________________
>>> Tecnica mailing list
>>> Tecnica a liste.siena.linux.it
>>> http://liste.siena.linux.it/cgi-bin/mailman/listinfo/tecnica
>>
>>
>> _______________________________________________
>> Tecnica mailing list
>> Tecnica a liste.siena.linux.it
>> http://liste.siena.linux.it/cgi-bin/mailman/listinfo/tecnica


Maggiori informazioni sulla lista Tecnica