Skip to main content ↑ ↓
Topic: Keeping losing the network (Read 2039 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Keeping losing the network

Ever since this last upgrade I keep losing my dhcpdcd connection and it doesn't return

Dec  1 08:02:01 flatbush dhcpcd[21381]: eno1: carrier lost
Dec  1 08:02:01 flatbush kernel: e1000e: eno1 NIC Link is Down
Dec  1 08:02:01 flatbush dhcpcd[21381]: eno1: deleting address fe80::73fe:b2c7:dd6b:1a9b
Dec  1 08:02:01 flatbush dhcpcd[21381]: eno1: deleting default route via 10.0.0.37
Dec  1 08:02:01 flatbush dhcpcd[21381]: eno1: deleting route to 10.0.0.0/24
Dec  1 08:02:03 flatbush ntpd[2783]: Deleting interface #14 eno1, fe80::73fe:b2c7:dd6b:1a9b%2#123, interface stats: received=0, sent=0, dr
opped=0, active_time=27651 secs
Dec  1 08:02:03 flatbush ntpd[2783]: Deleting interface #15 eno1, 10.0.0.62#123, interface stats: received=98, sent=118, dropped=0, active
_time=27648 secs
Dec  1 08:02:03 flatbush ntpd[2783]: 162.210.111.4 local addr 10.0.0.62 -> <null>
Dec  1 08:02:03 flatbush ntpd[2783]: 208.75.88.4 local addr 10.0.0.62 -> <null>
Dec  1 08:02:03 flatbush ntpd[2783]: 40.85.153.82 local addr 10.0.0.62 -> <null>
Dec  1 08:02:03 flatbush ntpd[2783]: 69.164.213.136 local addr 10.0.0.62 -> <null>
Dec  1 08:02:04 flatbush dhcpcd[29303]: sending commands to master dhcpcd process
Dec  1 08:02:04 flatbush dhcpcd[21381]: control command: /usr/bin/dhcpcd -k eno1
Dec  1 08:02:04 flatbush dhcpcd[21381]: eno1: removing interface
Dec  1 08:02:04 flatbush kernel: e1000e: eno1 NIC Link is Down
Dec  1 08:02:04 flatbush kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Dec  1 08:02:07 flatbush kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Dec  1 08:02:07 flatbush kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready


This workstation has been connected to  the local network for 4 years until this last upgrade.  I'm getting so fustrated.

Re: Keeping losing the network

Reply #1 –
Can you do rc-status and see if your network service is up? If not, then try doing: "rc-service your-network-service restart" and post the output.

Re: Keeping losing the network

Reply #2 –
Quote from: gavin17 – on
Can you do rc-status and see if your network service is up? If not, then try doing: "rc-service your-network-service restart" and post the output.


it is up.  It has always been up.   It has some keepalive heartbeat somewhere in the hardware which is now failing and when the connection starts and restarts, dhcpcd is removing the connection but it doesn't bring it back of .  I though Ahavi was the problem but I removed that and it is still unstable.

Re: Keeping losing the network

Reply #3 –
Code: [Select]
Runlevel: default
 syslog-ng                                                                                                                                                                                        [  started  ]
 acpid                                                                                                                                                                                            [  started  ]
 dbus                                                                                                                                                                                             [  started  ]
 dhcpcd                                                                                                                                                                                           [  started  ]
 wicd                                                                                                                                                                                             [  started  ]
 unbound                                                                                                                                                                                          [  stopped  ]
 netmount                                                                                                                                                                                         [  stopped  ]
 xdm                                                                                                                                                                                              [  started  ]
 alsasound                                                                                                                                                                                        [  started  ]
 cronie                                                                                                                                                                                           [  started  ]
 cupsd                                                                                                                                                                                            [  stopped  ]
 ntpd                                                                                                                                                                                             [  started  ]
 sshd                                                                                                                                                                                             [  started  ]
 local                                                                                                                                                                                            [  started  ]
 agetty.tty3                                                                                                                                                                 [  started 1 day(s) 04:05:04 (0) ]
 agetty.tty5                                                                                                                                                                 [  started 1 day(s) 04:05:04 (0) ]
 agetty.tty1                                                                                                                                                                 [  started 1 day(s) 04:05:04 (0) ]
 agetty.tty2                                                                                                                                                                 [  started 1 day(s) 04:05:04 (0) ]
 agetty.tty6                                                                                                                                                                 [  started 1 day(s) 04:05:04 (0) ]
 agetty.tty4                                                                                                                                                                 [  started 1 day(s) 04:05:04 (0) ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
 modules-load                                                                                                                                                                                     [  started  ]
 xdm-setup                                                                                                                                                                                        [  started  ]
Dynamic Runlevel: manual
 net-online                                                                                                                                                                                       [  started  ]
 net.eno1     

 

Re: Keeping losing the network

Reply #4 –
If this happened after a kernel update (and reboot), then something changed in the kernel module code. See modinfo e1000e for possible options to tweak (SmartPowerDownEnable seems like a good candidate. If it was dhcpcd then downgrade it.

If you updated kernel and haven't rebooted, then iptables might not work well and block packets to your DHCP serving box. Is that assigning a static IP to your box? If so, it might need a reboot. Try removing "option rapid_commit" from /etc/dhcpcd.conf.

Does dhclient behave the same?

Re: Keeping losing the network

Reply #5 –
Code: [Select]
Usage: lsmod
[www3 ~]# lsmod |grep e1000e
e1000e                229376  0
ptp                    20480  1 e1000e
[www3 ~]# mod
modinfo   modprobe  modutil   
[www3 ~]# modinfo 
modinfo: ERROR: missing module or filename.
[www3 ~]# modinfo e1000e
modinfo: ERROR: Module alias e1000e not found.


weird

Re: Keeping losing the network

Reply #6 –
oh another kernel upgrade.

Re: Keeping losing the network

Reply #8 –
it might seem like that but that is how the education process works.   Since 11-11 there has been 5 kernel upgrades

Code: [Select]
autodetect
[2017-11-05 12:48] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2017-11-11 09:30] [ALPM] upgraded linux-lts (4.9.60-1 -> 4.9.61-1)
[2017-11-11 09:30] [ALPM] upgraded linux-lts-docs (4.9.60-1 -> 4.9.61-1)
[2017-11-11 09:30] [ALPM] running '90-linux-lts.hook'...
[2017-11-11 09:30] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2017-11-11 09:30] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2017-11-11 09:30] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2017-11-11 09:30] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2017-11-11 09:30] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2017-11-11 09:30] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2017-11-22 15:26] [ALPM] upgraded linux-lts (4.9.61-1 -> 4.9.64-1)
[2017-11-22 15:26] [ALPM] upgraded linux-lts-docs (4.9.61-1 -> 4.9.64-1)
[2017-11-22 15:26] [ALPM] running '90-linux-lts.hook'...
[2017-11-22 15:26] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2017-11-22 15:26] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2017-11-22 15:26] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2017-11-22 15:26] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2017-11-22 15:26] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2017-11-22 15:26] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2017-11-26 19:53] [ALPM] upgraded linux-lts (4.9.64-1 -> 4.9.65-1)
[2017-11-26 19:53] [ALPM] upgraded linux-lts-docs (4.9.64-1 -> 4.9.65-1)
[2017-11-26 19:53] [ALPM] running '90-linux-lts.hook'...
[2017-11-26 19:53] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2017-11-26 19:53] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2017-11-26 19:53] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2017-11-26 19:53] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2017-11-26 19:53] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2017-11-26 19:53] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2017-11-29 22:39] [PACMAN] Running 'pacman -S linux-lts'
[2017-11-29 22:39] [ALPM] reinstalled linux-lts (4.9.65-1)
[2017-11-29 22:39] [ALPM] running '90-linux-lts.hook'...
[2017-11-29 22:39] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2017-11-29 22:39] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2017-11-29 22:39] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2017-11-29 22:39] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2017-11-29 22:39] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2017-11-29 22:39] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2017-12-01 17:51] [ALPM] upgraded linux-lts (4.9.65-1 -> 4.9.66-1)
[2017-12-01 17:51] [ALPM] upgraded linux-lts-docs (4.9.65-1 -> 4.9.66-1)
[2017-12-01 17:51] [ALPM] running '90-linux-lts.hook'...
[2017-12-01 17:51] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2017-12-01 17:51] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2017-12-01 17:51] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2017-12-01 17:51] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2017-12-01 17:51] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2017-12-01 17:51] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img


I didn't reboot the last one, but I doubt it will have an impact on the problem.  This particular machine is a gateway and webserver.  It is not really possible to reboot it weekly in any event, which is one of the reasons I was asking if there is documentation as to the reasons for package changed.  I will need to exclude automatic upgrades to certain packages and access when to upgrade them by hand.

Re: Keeping losing the network

Reply #9 –
An offer of gratitude for the help that you have received & combined with an apology for wasting people's time may be thought appropriate by some...

Re: Keeping losing the network

Reply #11 –
Quote from: nous – on

Does dhclient behave the same?


I haven't used it.  It has historically been a problem ap in my experice and vixies DHCP rock solid.  I'm getting troubles with ssh cryptogrraphy as well with a poxy tunnel.  It is adding up to hardware check sum troubles.  I need to reboot that server with the new kernel and see if it continues.  If so, then do as you suggest and try options on the card.

I have made changes to the client side that has stabliezed the dhcpd connection, including giving it a static ip address, added /etc/init.d/net.eno1 and making config changes

[ruben@flatbush ~]$ cat /etc/conf.d/net|grep -v '#' |grep -v '^$'
config_eno1="10.0.0.62/24"
config_eno1="dhcp"