• [6.7-RC2] eth0: failed to renew DHCP, rebinding

    wgstarks

    By wgstarks

      • Solved

    I'm not sure if this is associated with RC2 but never saw this behavior before installing the RC's. For the past week or so I've been having issues with random lose of contact to my server. I checked the logs after the most recent event and found this entry which coincides to the lose of contact-  

    Jan 29 04:46:10 Brunnhilde dhcpcd[1767]: eth0: failed to renew DHCP, rebinding
Jan 29 04:47:59 Brunnhilde kernel: mdcmd (135): set md_write_method 1
Jan 29 04:47:59 Brunnhilde kernel: 
Jan 29 04:57:59 Brunnhilde kernel: mdcmd (136): set md_write_method 0
Jan 29 04:57:59 Brunnhilde kernel: 
Jan 29 05:01:10 Brunnhilde dhcpcd[1767]: eth0: DHCP lease expired
Jan 29 05:01:10 Brunnhilde avahi-daemon[13759]: Withdrawing address record for 10.0.1.20 on eth0.
Jan 29 05:01:10 Brunnhilde avahi-daemon[13759]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.20.
Jan 29 05:01:10 Brunnhilde avahi-daemon[13759]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 29 05:01:10 Brunnhilde dhcpcd[1767]: eth0: deleting route to 10.0.1.0/24
Jan 29 05:01:10 Brunnhilde dhcpcd[1767]: eth0: deleting default route via 10.0.1.1
Jan 29 05:01:10 Brunnhilde dhcpcd[1767]: eth0: soliciting a DHCP lease
Jan 29 05:01:10 Brunnhilde dhcpcd[1767]: eth0: offered 10.0.1.20 from 10.0.1.1
Jan 29 05:01:10 Brunnhilde dhcpcd[1767]: eth0: probing address 10.0.1.20/24
Jan 29 05:01:12 Brunnhilde ntpd[1879]: Deleting interface #25 eth0, 10.0.1.20#123, interface stats: received=18, sent=18, dropped=0, active_time=7200 secs
Jan 29 05:01:12 Brunnhilde ntpd[1879]: 10.0.1.1 local addr 10.0.1.20 -> <null>
Jan 29 05:01:16 Brunnhilde dhcpcd[1767]: eth0: leased 10.0.1.20 for 7200 seconds
Jan 29 05:01:16 Brunnhilde dhcpcd[1767]: eth0: adding route to 10.0.1.0/24
Jan 29 05:01:16 Brunnhilde dhcpcd[1767]: eth0: adding default route via 10.0.1.1
Jan 29 05:01:16 Brunnhilde avahi-daemon[13759]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.1.20.
Jan 29 05:01:16 Brunnhilde avahi-daemon[13759]: New relevant interface eth0.IPv4 for mDNS.
Jan 29 05:01:16 Brunnhilde avahi-daemon[13759]: Registering new address record for 10.0.1.20 on eth0.IPv4.
Jan 29 05:01:17 Brunnhilde ntpd[1879]: Listen normally on 26 eth0 10.0.1.20:123
Jan 29 05:01:17 Brunnhilde ntpd[1879]: new interface(s) found: waking up resolver

    I see this event repeated quite often in the system log and it doesn't always result in lose of connections from other computers, but it does look like all of the lost connections have coincided with the failed DHCP renewals.

     

    Full diagnostics are also attached.

     

    brunnhilde-diagnostics-20190129-1758.zip

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    wgstarks

    After a little more investigating I have discovered that this only happens if a second ethernet port is enabled ( eth2 in my case). If I “Port Down” eth2 I no longer get any lease renewal errors.

     

    SafariScreenSnapz150.thumb.jpg.e9b81053bfa4e753a57d9ba4177d44a0.jpg

    Link to comment
    bonienl

    Connecting both eth0 (10.0.1..20) and eth2 (10.0.1.159) to the same network causes network routing problems. This setup is not recommendad.

     

    If you want to use both interfaces, you have the following options:

    1. Create a bonded interface with eth0 and eth2 as members. Only use active-standby mode (because of speed differences between eth0 and eth2)
    2. Keep eth2 as separate interface and make sure it is part of a different network (your router and switch must be configured accordingly)

     

    Link to comment
    wgstarks
    29 minutes ago, bonienl said:

    Connecting both eth0 (10.0.1..20) and eth2 (10.0.1.159) to the same network causes network routing problems. This setup is not recommendad.

     

    If you want to use both interfaces, you have the following options:

    1. Create a bonded interface with eth0 and eth2 as members. Only use active-standby mode (because of speed differences between eth0 and eth2)
    2. Keep eth2 as separate interface and make sure it is part of a different network (your router and switch must be configured accordingly)

     

    Thanks. It was actually an accident that eth2 was not ported down. I never intended it to be used. Was just reporting what appeared to be an issue.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.