Announcement

Collapse
No announcement yet.

Lost network connection

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Lost network connection

    My server has been running for a long time without problems. All of a sudden yesterday it cannot connect to the network anymore. Co-incidentally I also got a new router (Synology RT2600). But it connected fine to it for the last few days. After I did a firmware upgrade on the router I noticed that vortexbox wasn't connected anymore.

    I have done a lot of internet searching but found no solution. It seems to be related to eth0 not initializing properly... I also looked for duplicate MAC addresses. Error messages I have encountered are when "systemctl start/restart network":
    bringing up interface eth0: ERROR
    network failed to start lsb
    Device eth0 does not seem to be present, delaying initialization



    > systemctl status network
    ● network.service - LSB: Bring up/down networking
    Loaded: loaded (/etc/rc.d/init.d/network)
    Active: inactive (dead)
    Docs: man:systemd-sysv-generator(8)


    > after restarting network
    > systemctl status network
    ● network.service - LSB: Bring up/down networking
    Loaded: loaded (/etc/rc.d/init.d/network)
    Active: failed (Result: exit-code) since Tue 2018-12-04 07:45:18 PST; 39s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 4718 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
    CGroup: /system.slice/network.service
    └─4541 /sbin/dhclient -H vortexbox -q -lf /var/lib/dhclient/dhclient--eth1.lease -pf /var/run/dhclient-eth1.pid eth1

    Dec 04 07:45:18 vortexbox network[4718]: RTNETLINK answers: File exists
    Dec 04 07:45:18 vortexbox network[4718]: RTNETLINK answers: File exists
    Dec 04 07:45:18 vortexbox network[4718]: RTNETLINK answers: File exists
    Dec 04 07:45:18 vortexbox network[4718]: RTNETLINK answers: File exists
    Dec 04 07:45:18 vortexbox network[4718]: RTNETLINK answers: File exists
    Dec 04 07:45:18 vortexbox network[4718]: RTNETLINK answers: File exists
    Dec 04 07:45:18 vortexbox systemd[1]: network.service: Control process exited, code=exited status=1
    Dec 04 07:45:18 vortexbox systemd[1]: Failed to start LSB: Bring up/down networking.
    Dec 04 07:45:18 vortexbox systemd[1]: network.service: Unit entered failed state.
    Dec 04 07:45:18 vortexbox systemd[1]: network.service: Failed with result 'exit-code'.



    If I do an "ifconfig" eth0 does not always show up. But sometimes it does. My router is at 192.168.1.1..., so different from the broadcast IP below:
    > ifconfig
    eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    inet 192.168.1.89 netmask 255.255.255.0 broadcast 192.168.1.255
    ether 00:e0:66:6e:16:e4 txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1 (Local Loopback)
    RX packets 193 bytes 18379 (17.9 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 193 bytes 18379 (17.9 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    > ifup eth0
    Determining IP information for eth0... failed.

    So not sure what is going on.... At the ethernet port the lights (green/yellow) do blink, so it looks to be active. I swapped ethernet cables as well.

    I have no clue how to troubleshoot this any more. Thinking of just re-installing vortexbox, but since I made many tweaks it will be a pain if I can't copy the old LMS settings back.

    Hope someone can help fix this very frustrating problem.

    Thanks!

  • #2
    Yay! I got it resolved. I changed the settings from DHCP to static in ifcfg-eth0 and added a line in ifcfg-lo. Somehow that got it working. I guess it is not compatible with the DHCP server of my Synology router? Strainge. So here are my 2 network files in case anyone else has that problem.


    [[email protected] network-scripts]$ pwd
    /etc/sysconfig/network-scripts

    [[email protected] network-scripts]$ more ifcfg-eth0
    DEVICE="eth0"
    BOOTPROTO="none"
    ONBOOT="yes"
    TYPE="Ethernet"
    IPADDR=192.168.1.100
    NETMASK=255.255.255.0
    GATEWAY=192.168.1.1
    DNS1=8.8.8.8
    IPV6INIT=no
    USERCTL=no
    NM_CONTROLLED=yes

    [[email protected] network-scripts]$ more ifcfg-lo
    DEVICE=lo
    IPADDR=127.0.0.1
    NETMASK=255.0.0.0
    NETWORK=127.0.0.0
    # If you're having problems with gated making 127.0.0.0/8 a martian,
    # you can change this to something else (255.255.255.255, for example)
    BROADCAST=127.255.255.255
    ONBOOT=yes
    NAME=loopback
    NM_CONTROLLED=no

    Comment

    Working...
    X