• DHCPCD and CPU


    Within an hour or two after rebooting into a fresh Antergos install, I notice that dhcpcd starts chewing up 60% of one core, and systemd-journal starts chewing up almost 100% of another cpu.

    Digging into the logs, it appears that dhcpcd is receiving a few hundred SIGPIPE signals each second, which gets logged, and of course chews up some processing in dhcpcd. As near as I can find, there’s no other significant entries in the log:

      
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    
    

    This is on a wired network, with no VPN currently enabled.

    Any thoughts on what might be going on? I’ve been using Linux for a long time, but this is my first time using Antergos, and a systemd based release, so I’m kind of muddling through here and there. Any assistance would be great.

  • Within an hour or two after rebooting into a fresh Antergos install, I notice that dhcpcd starts chewing up 60% of one core, and systemd-journal starts chewing up almost 100% of another cpu.

    Digging into the logs, it appears that dhcpcd is receiving a few hundred SIGPIPE signals each second, which gets logged, and of course chews up some processing in dhcpcd. As near as I can find, there’s no other significant entries in the log:

      
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    Dec 03 19:01:56 jupiter dhcpcd[286]: received signal PIPE  
    
    

    This is on a wired network, with no VPN currently enabled.

    Any thoughts on what might be going on? I’ve been using Linux for a long time, but this is my first time using Antergos, and a systemd based release, so I’m kind of muddling through here and there. Any assistance would be great.

  • Also, worth noting, this seems to happen about 2 hours after I reboot. Possibly not coincidentally, the DHCP lease time on my DHCP server is 2 hours.

  • What hardware do you use?

  • I have Antergos now on two computers, one a wired desktop and one wireless laptop, Both were having this error until I switched them to a static IP.

    The DHCP server on my network is a Buffalo WZR-600DHP2 runing the Buffalo build of DD-WRT fully updated to the latest version

    My laptop is an old Acer Aspire with an AMD Phenom II N970. The network adapter on the laptop is a Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)

    My Desktop is an (aging) custom built with an AMD Phenom 9350e. The network adapter on the desktop is a Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller that’s built on to the motherboard.

    The desktop is using a Gnome desktop with NetworkManager, and the Laptop is using XFCE desktop with NetworkManager.

  • Try installing dhclient and restarting NetworkManager.

    edit: I’m sorry, I didn’t realize this was such an old thread.

Posts 6Views 1602
Log in to reply