Network issues

Discussion in 'Server Operation' started by rusty, Jun 7, 2017.

  1. rusty

    rusty Member HowtoForge Supporter

    I was looking into adding a network card, and inadvertantly messed up my Ubuntu 14.04 running zimbra 8.7.10
    I'm only using eth0 at present
    When I started:
    Code:
    dmesg | grep -i network
    would give the following result
    Code:
    [  4.203179] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
    [  4.321572] e1000e 0000:03:00.0 eth1: Intel(R) PRO/1000 Network Connection
    And the command
    Code:
    cat /etc/network/interfaces |sed 's/#.*$//'|grep dns-|sed 's/dns-//g'|sudo resolvconf -a eth0.inet
    would bring the dns-nameserver to resolv.conf
    Now
    Code:
    dmesg | grep -i network
    gives no results
    and
    Code:
    cat /etc/network/interfaces |sed 's/#.*$//'|grep dns-|sed 's/dns-//g'|sudo resolvconf -a eth0.inet
    fails to work. After this happened, I found that the name server info was missing from resolv.conf and had to manually enter the dns namservers (it will probably get over-written as not supposed to edit this file directly)
    Also my Zimbra has not been working correctly ever since (not sure it is related) but accounts going into lockout randomly and frequently
    And SSH sessions getting dropped every once in a while and Zimbra admin panel gets dropped too.
    Here's what I might have done to cause this:
    When I was doing the dmesg | grep -i network command I was trying to cut and paste, and it tried to executed the commands. Not sure if it did.
    And I plugged a network wire into the empty network port and I lost connection knocking my server offline, so I rebooted

    Code:
    ifconfig (notice eth3)
    root@mail:~# ifconfig
    eth0  Link encap:Ethernet  HWaddr 00:1e:67:16:36:65
      inet addr:71.184.68.19  Bcast:71.184.68.255  Mask:255.255.255.0
      inet6 addr: fe80::21e:67ff:fe16:3665/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:36320856 errors:0 dropped:18330 overruns:0 frame:0
      TX packets:71184839 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:4007218395 (4.0 GB)  TX bytes:101513088672 (101.5 GB)
      Interrupt:16 Memory:b2300000-b2320000
    
    eth3  Link encap:Ethernet  HWaddr 00:1e:67:16:36:64
      UP BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
      Interrupt:16 Memory:b2100000-b2120000
    
    lo  Link encap:Local Loopback
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:17723498 errors:0 dropped:0 overruns:0 frame:0
      TX packets:17723498 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1
      RX bytes:16379871555 (16.3 GB)  TX bytes:16379871555 (16.3 GB)
    
    tun0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
      inet addr:192.168.141.1  P-t-P:192.168.141.2  Mask:255.255.255.255
      UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:100
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     
    Last edited: Jun 7, 2017
  2. rusty

    rusty Member HowtoForge Supporter

    After disabling dnsmasq (based on howto) I found after reboots it was still running. Removed it and now everything back to normal.





     

Share This Page