Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a number of Soekris boxes running Debian Squeeze. They were installed through an automated process consisting of using deboostrap and copying it unto a Compact Flash card. We use puppet to manage the configuration of all these boxes.

Before Debian Squeeze, they were running Voyage Linux which is just a "lighter" version of Debian. Since we have switched, we're seeing the /lib/udev/net.agent process take up an aweful lot of CPU. We have so far been unable to find any clue as to what this really does and why it's taking up some much CPU time.

In htop we see the following :

htop show net.agent cpu usage

We are seeing absolutly no syslog messages related to this process so we're a bit lost... So, I am looking for pointers as to what this process does in general and what could be the potential cause of such CPU usage.

EDIT :

My /etc/network/interfaces is the following :

auto eth0
iface eth0 inet dhcp
       up iptables-restore < /etc/iptables.conf

auto br0
iface br0 inet static
       address 192.168.51.1
       netmask 255.255.255.0
       network 192.168.51.0
       broadcast 192.168.51.255
       bridge_ports eth1 eth3

EDIT2 :

After doing a bit more investigation, this issue only comes up after somewhere around 6 days and is solved for another 6 days by just rebooting the system. Now it makes even less sense. I would like to avoid scheduling a reboot every few days as this doesn't sound like a decent solution.

EDIT3 :

This doesn't seem to happen on a regular frequency as it just happened after 3 days.

share|improve this question
add comment

2 Answers

up vote 4 down vote accepted

I think that's because you have no lo device. Add the following in /etc/network/interfaces

auto lo
iface lo inet loopback

then do

ifup lo
share|improve this answer
    
That's one very good piece of advice, I'll try it out –  Antoine Benkemoun Jun 21 '12 at 10:48
    
That is indeed correct, the script hardcodes the requirement for an lo interface "wait_for_interface lo" –  Antoine Benkemoun Jun 22 '12 at 9:16
    
I have these lines in /etc/network/interfaces, but for some reason my lo interface just disappeared. 'ifup lo' did not work, 'ifconfig lo up' did. –  konrad May 14 '13 at 15:20
add comment

In /etc/network/interfaces replace the line allow-hotplug eth0 by auto eth0. Reboot. Enjoy.

share|improve this answer
    
No such thing in my /etc/network/interfaces... –  Antoine Benkemoun Nov 12 '11 at 10:25
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.