ntmyflt
asked on
Ubuntu 12.04 LTS Server losing network connectivity after some time
Hello Experts,
I have a new Ubuntu 12.04 esxi virtual machine (console only) with Vmware tools installed and seem to be having a strange issue where if I don't use the vm for a few hours it will eventually lose network connectivity. (can't ping from within the vm outside, can't ssh into the vm). In order to bring it back online I have to run the ifup eth0 command.
The VM is set to a static ip address..
root@linux:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.107.50
netmask 255.255.255.0
broadcast 192.168.107.255
gateway 192.168.107.254
dns-nameservers 192.168.107.254
Here's the /var/log/kern.log entries that have to do with the network card:
May 30 13:54:31 linux kernel: [ 0.872393] Freeing unused kernel memory: 1200k freed
May 30 13:54:31 linux kernel: [ 0.899146] VMware vmxnet3 virtual NIC driver - version 1.1.29.0-k-NAPI
May 30 13:54:31 linux kernel: [ 0.904810] VMware PVSCSI driver - version 1.0.1.0-k
May 30 13:54:31 linux kernel: [ 0.948398] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
May 30 13:54:31 linux kernel: [ 0.948400] e1000: Copyright (c) 1999-2006 Intel Corporation.
May 30 13:54:31 linux kernel: [ 0.948454] e1000 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
May 30 13:54:31 linux kernel: [ 0.948543] e1000 0000:02:00.0: setting latency timer to 64
May 30 13:54:31 linux kernel: [ 0.956965] Floppy drive(s): fd0 is 1.44M
May 30 13:54:31 linux kernel: [ 0.972936] FDC 0 is a post-1991 82077
May 30 13:54:31 linux kernel: [ 1.296729] e1000 0000:02:00.0: eth0: (PCI:66MHz:32-bit) 00:50:56:91:5e:d4
May 30 13:54:31 linux kernel: [ 1.296733] e1000 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection
May 30 13:54:31 linux kernel: [ 1.728012] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
May 30 13:54:31 linux kernel: [ 9.780087] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 30 13:54:31 linux kernel: [ 9.791244] EXT4-fs (sda1): warning: checktime reached, running e2fsck is recommended
May 30 13:54:31 linux kernel: [ 9.877712] EXT4-fs (sda1): re-mounted. Opts: (null)
May 30 13:54:31 linux kernel: [ 10.002221] Adding 999420k swap on /dev/sda2. Priority:-1 extents:1 across:999420k
May 30 13:54:31 linux kernel: [ 10.111357] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
May 30 13:54:31 linux kernel: [ 10.116262] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 30 13:54:31 linux kernel: [ 10.116311] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Not really sure where to begin with this one, any help would be greatly appreciated.
Thanks,
I have a new Ubuntu 12.04 esxi virtual machine (console only) with Vmware tools installed and seem to be having a strange issue where if I don't use the vm for a few hours it will eventually lose network connectivity. (can't ping from within the vm outside, can't ssh into the vm). In order to bring it back online I have to run the ifup eth0 command.
The VM is set to a static ip address..
root@linux:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.107.50
netmask 255.255.255.0
broadcast 192.168.107.255
gateway 192.168.107.254
dns-nameservers 192.168.107.254
Here's the /var/log/kern.log entries that have to do with the network card:
May 30 13:54:31 linux kernel: [ 0.872393] Freeing unused kernel memory: 1200k freed
May 30 13:54:31 linux kernel: [ 0.899146] VMware vmxnet3 virtual NIC driver - version 1.1.29.0-k-NAPI
May 30 13:54:31 linux kernel: [ 0.904810] VMware PVSCSI driver - version 1.0.1.0-k
May 30 13:54:31 linux kernel: [ 0.948398] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
May 30 13:54:31 linux kernel: [ 0.948400] e1000: Copyright (c) 1999-2006 Intel Corporation.
May 30 13:54:31 linux kernel: [ 0.948454] e1000 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
May 30 13:54:31 linux kernel: [ 0.948543] e1000 0000:02:00.0: setting latency timer to 64
May 30 13:54:31 linux kernel: [ 0.956965] Floppy drive(s): fd0 is 1.44M
May 30 13:54:31 linux kernel: [ 0.972936] FDC 0 is a post-1991 82077
May 30 13:54:31 linux kernel: [ 1.296729] e1000 0000:02:00.0: eth0: (PCI:66MHz:32-bit) 00:50:56:91:5e:d4
May 30 13:54:31 linux kernel: [ 1.296733] e1000 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection
May 30 13:54:31 linux kernel: [ 1.728012] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
May 30 13:54:31 linux kernel: [ 9.780087] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 30 13:54:31 linux kernel: [ 9.791244] EXT4-fs (sda1): warning: checktime reached, running e2fsck is recommended
May 30 13:54:31 linux kernel: [ 9.877712] EXT4-fs (sda1): re-mounted. Opts: (null)
May 30 13:54:31 linux kernel: [ 10.002221] Adding 999420k swap on /dev/sda2. Priority:-1 extents:1 across:999420k
May 30 13:54:31 linux kernel: [ 10.111357] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
May 30 13:54:31 linux kernel: [ 10.116262] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 30 13:54:31 linux kernel: [ 10.116311] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Not really sure where to begin with this one, any help would be greatly appreciated.
Thanks,
That is an odd one. What is the OS of the VMware host?
ASKER
Hi, ESXi 5.1
I'm running the e1000 adaptor, just wondering if that would be the issue?
root@linux:/etc/network# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:07.7 System peripheral: VMware Virtual Machine Communication Interface (rev 10)
00:0f.0 VGA compatible controller: VMware SVGA II Adapter
00:11.0 PCI bridge: VMware PCI bridge (rev 02)
00:15.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.7 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.7 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.7 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.7 PCI bridge: VMware PCI Express Root Port (rev 01)
02:00.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
root@linux:/etc/network# ls
I'm running the e1000 adaptor, just wondering if that would be the issue?
root@linux:/etc/network# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:07.7 System peripheral: VMware Virtual Machine Communication Interface (rev 10)
00:0f.0 VGA compatible controller: VMware SVGA II Adapter
00:11.0 PCI bridge: VMware PCI bridge (rev 02)
00:15.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:15.7 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:16.7 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:17.7 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.0 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.1 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.2 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.3 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.4 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.5 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.6 PCI bridge: VMware PCI Express Root Port (rev 01)
00:18.7 PCI bridge: VMware PCI Express Root Port (rev 01)
02:00.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
root@linux:/etc/network# ls
ASKER
looks like it's down again.. any commands that maybe I can run to gather some data as to why this is happening?
ASKER
A little more insight into this virtual machine issue. This vm was downloaded from bitnami who provide pre-configured vms ready to go. It was for joomla. When downloaded the ovf file I vmware converted it into our esxi environment, all went well with no issues.
what I did a bit ago was uninstall vmware tools and it seemed the network came back up but now 45 minutes later it's no longer accessible again
what I did a bit ago was uninstall vmware tools and it seemed the network came back up but now 45 minutes later it's no longer accessible again
The VMware log for that VM might have some helpful error messages. Also, you could add another virtual NIC that uses a different adapter (and disable the broken NIC.)
If those ideas don't help, you may need to post your problem on a VMware forum. Does bitnami have a support forum?
If those ideas don't help, you may need to post your problem on a VMware forum. Does bitnami have a support forum?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Since I state the actual solution to the issue i had and nobody else seems to.