topic title: HUGE /var/log and DCHP messages on startup
Posts: 41
tanian
Joined: 10 Dec 2011
#1
Hello again !
Since the last update, a month ago, I noticed some DCHP calls on startup, before X. At the time I didn't take much importance to those lines (dont remember exactly line-by-line what they said) but apparently the system thought I always was connected to the internet, which in reality I dont, and the system was something like"readying" the ethernet connection (and something like DCHP lines - sorry but I'm not very familiar in networking). This process made longer the startup time since.
And now, when I'm wanting to update some programs, I'm left with messages that say"not enought disk space","cannot write to output", the like. So I searched for the bloated directory, and that was /var/log.

Code: Select all

root@tan2:/home/tan2# tail /var/log/syslog
Jun 10 13:36:16 tan2 kernel: [ 1358.774858] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=287 PROTO=2 
Jun 10 13:38:22 tan2 kernel: [ 1483.893923] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=288 PROTO=2 
Jun 10 13:40:26 tan2 kernel: [ 1608.672959] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=289 PROTO=2 
Jun 10 13:42:32 tan2 kernel: [ 1733.791974] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=290 PROTO=2 
Jun 10 13:42:49 tan2 dbus[1889]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
Jun 10 13:42:49 tan2 dbus[1889]: [system] Successfully activated service 'org.freedesktop.UDisks'
Jun 10 13:44:13 tan2 kernel: [ 1835.545886] lo: Disabled Privacy Extensions
Jun 10 13:44:37 tan2 kernel: [ 1858.910976] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=329 PROTO=2 
Jun 10 13:46:41 tan2 kernel: [ 1983.709936] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=380 PROTO=2 
Jun 10 13:48:47 tan2 kernel: [ 2108.828923] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=389 PROTO=2 
root@tan2:/home/tan2#

This file syslog is 1.4 GiB (while syslg.1 has the same value but in MiB)
The kern.log in the same directory is also that huge:

Code: Select all

root@tan2:/home/tan2# tail /var/log/kern.log
Jun 10 13:50:52 tan2 kernel: [ 2233.967882] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=400 PROTO=2 
Jun 10 13:52:56 tan2 kernel: [ 2358.746824] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=402 PROTO=2 
Jun 10 13:57:07 tan2 kernel: [ 2608.984652] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=443 PROTO=2 
Jun 10 13:59:12 tan2 kernel: [ 2733.813552] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=472 PROTO=2 
Jun 10 14:01:17 tan2 kernel: [ 2858.932434] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=475 PROTO=2 
Jun 10 14:03:21 tan2 kernel: [ 2983.711324] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=482 PROTO=2 
Jun 10 14:05:27 tan2 kernel: [ 3108.890192] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=484 PROTO=2 
Jun 10 14:07:32 tan2 kernel: [ 3233.949055] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=516 PROTO=2 
Jun 10 14:09:36 tan2 kernel: [ 3358.737924] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=519 PROTO=2 
Jun 10 14:11:42 tan2 kernel: [ 3483.876777] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1d:6a:00:10:89:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=522 PROTO=2 
root@tan2:/home/tan2#
My temporal workaround for this is to simply delete those big files, that are of no real use for me - well, although it really helped me to confirm my suspecting explained early in this post.
But I fear that the same thing will strike me on the near future. And I also want those DCHP messages at startup to be gone for good, should these messages add to those or some other log files, effectively draining usable disk space.
Please help, are there any permanent solutions for this, and how do I do it??
Thanks in advance.

Acclaration in correction: It happens I really don't know if those lines of code I put here has anything to do with the problem. Anyway, those two files are 2.8 GiB total - thats' the problem.
Posts: 765
rust collector
Joined: 27 Dec 2011
#2
When I had the delay while booting because of dhcpdiscover, I just commented out every line in my /etc/network/interfaces
And that did it for me, and network still worked fine (I use wicd, if that matters)

If you look in the sid part of the forum, there is a post made today about an update to ifupdown... That fixed the issue for me, and I was able to uncomment the /etc...blablabla... and it still works great!

I don't think deleting log files will hurt anything either, ...unless you have to look for something in them...
Posts: 609
dark-D
Joined: 02 Jun 2008
#3
why did you make 3 topics with the same question? is your internet dropping? my suggestion is to install ifupdown from unstable. after reboot, the files will be created again, have a look if the bloat reappears.

edit: the forum is acting up. that's why i think you had 3 topics the same.