Server nicht erreichbar

[hippoth]

Hallo Leute,

ich habe eine Ubuntu 10.04 LTS Server welcher nach einiger Zeit einfach nicht mehr netzwerktechnisch erreichbar ist, kein ping kommt an, nix ...

Gehe ich direkt auf den Server und pinge etwas außerhalb des Servers an, dann dauert es gut 5 Sekunden und das Netzwerk geht wieder. Das Netzwerk kommt auch wieder in Schwung, wenn ich einfach eine /etc/init.d/networking restart mache. Außerdem kam neulich das Netzwerk für gut 5 Pings in Schwung als ich den Server dann mal neu gestartet habe.

Kann mir jemand einen Anhaltspunkt zum Troubleshooting geben?

[zyrusthc]

Logfiles / Meldungen ?!

Greeez Oli

[hippoth]

Logfiles / Meldungen ?!

Greeez Oli
Ich kann nichts außergwöhnliches finden.

Hattest du an ein bestimmtest Log gedacht?

[zyrusthc]

An das Syslog zum Zeitpunkt des Ausfalls. Desweiteren mal die Einstellungen der Netzwerkkarte mit ethtool checken.

Greeez Oli

[hippoth]

Ich habe den Server vollständig neu gestartet und dann ist das Netz zwei mal ausgefallen und hier das syslog seit dem Neustart. Ich habe nach jedem Netzausfall ein "/etc/init.d/networking restart" gemacht.

Ein Test (sudo ethtool -t eth0) des Interfaces funktioniert leider nicht, ich bekomme ein "Cannot test: Operation not supported"


Feb 26 19:01:28 zimbra kernel: [ 2.436380] sda: sda1 sda2 < sda5 >
Feb 26 19:01:28 zimbra kernel: [ 2.437349] sd 2:0:0:0: [sda] Cache data unavailable
Feb 26 19:01:28 zimbra kernel: [ 2.437352] sd 2:0:0:0: [sda] Assuming drive cache: write through
Feb 26 19:01:28 zimbra kernel: [ 2.437355] sd 2:0:0:0: [sda] Attached SCSI disk
Feb 26 19:01:28 zimbra kernel: [ 2.657070] EXT4-fs (dm-0): mounted filesystem with ordered data mode
Feb 26 19:01:28 zimbra kernel: [ 4.555298] Adding 2174968k swap on /dev/mapper/zimbra-swap_1. Priority:-1 extents:1 across:2174968k
Feb 26 19:01:28 zimbra kernel: [ 4.892001] udev: starting version 151
Feb 26 19:01:28 zimbra kernel: [ 5.138344] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 26 19:01:28 zimbra kernel: [ 5.215618] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3
Feb 26 19:01:28 zimbra kernel: [ 5.217651] ACPI: resource piix4_smbus [0x1040-0x1047] conflicts with ACPI region SMB_ [0x1040-0x104b]
Feb 26 19:01:28 zimbra kernel: [ 5.217652] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 26 19:01:28 zimbra kernel: [ 5.258544] VMware vmxnet3 virtual NIC driver - version 1.0.5.0-k-NAPI
Feb 26 19:01:28 zimbra kernel: [ 5.258669] alloc irq_desc for 18 on node -1
Feb 26 19:01:28 zimbra kernel: [ 5.258671] alloc kstat_irqs on node -1
Feb 26 19:01:28 zimbra kernel: [ 5.258682] vmxnet3 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Feb 26 19:01:28 zimbra kernel: [ 5.258735] vmxnet3 0000:03:00.0: setting latency timer to 64
Feb 26 19:01:28 zimbra kernel: [ 5.315570] agpgart-intel 0000:00:00.0: Intel 440BX Chipset
Feb 26 19:01:28 zimbra kernel: [ 5.315713] features: sg csum vlan jf tso tsoIPv6 lro highDMA
Feb 26 19:01:28 zimbra kernel: [ 5.316356] alloc irq_desc for 56 on node -1
Feb 26 19:01:28 zimbra kernel: [ 5.316359] alloc kstat_irqs on node -1
Feb 26 19:01:28 zimbra kernel: [ 5.316427] vmxnet3 0000:03:00.0: irq 56 for MSI/MSI-X
Feb 26 19:01:28 zimbra kernel: [ 5.316552] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x0
Feb 26 19:01:28 zimbra kernel: [ 5.318940] vga16fb: initializing
Feb 26 19:01:28 zimbra kernel: [ 5.318942] vga16fb: mapped to 0xffff8800000a0000
Feb 26 19:01:28 zimbra kernel: [ 5.318978] fb0: VGA16 VGA frame buffer device
Feb 26 19:01:28 zimbra kernel: [ 5.350837] parport_pc 00:08: reported by Plug and Play ACPI
Feb 26 19:01:28 zimbra kernel: [ 5.351109] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Feb 26 19:01:28 zimbra kernel: [ 5.353849] lp: driver loaded but no devices found
Feb 26 19:01:28 zimbra kernel: [ 5.370630] ppdev: user-space parallel port driver
Feb 26 19:01:28 zimbra kernel: [ 5.437886] lp0: using parport0 (interrupt-driven).
Feb 26 19:01:28 zimbra kernel: [ 5.537130] type=1505 audit(1330279288.564:2): operation="profile_load" pid=585 name="/sbin/dhclient3"
Feb 26 19:01:28 zimbra kernel: [ 5.537575] type=1505 audit(1330279288.564:3): operation="profile_load" pid=585 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
Feb 26 19:01:28 zimbra kernel: [ 5.537812] type=1505 audit(1330279288.564:4): operation="profile_load" pid=585 name="/usr/lib/connman/scripts/dhclient-script"
Feb 26 19:01:28 zimbra kernel: [ 5.538490] type=1505 audit(1330279288.564:5): operation="profile_replace" pid=654 name="/sbin/dhclient3"
Feb 26 19:01:28 zimbra kernel: [ 5.538921] type=1505 audit(1330279288.564:6): operation="profile_replace" pid=654 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
Feb 26 19:01:28 zimbra kernel: [ 5.539169] type=1505 audit(1330279288.564:7): operation="profile_replace" pid=654 name="/usr/lib/connman/scripts/dhclient-script"
Feb 26 19:01:28 zimbra kernel: [ 5.633857] Console: switching to colour frame buffer device 80x30
Feb 26 19:01:28 zimbra kernel: [ 5.647055] eth0: intr type 3, mode 0, 1 vectors allocated
Feb 26 19:01:28 zimbra kernel: [ 5.648250] eth0: NIC Link is Up 10000 Mbps
Feb 26 19:01:28 zimbra kernel: [ 5.895384] type=1505 audit(1330279288.924:8): operation="profile_replace" pid=724 name="/sbin/dhclient3"
Feb 26 19:01:28 zimbra kernel: [ 5.896091] type=1505 audit(1330279288.924:9): operation="profile_replace" pid=724 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
Feb 26 19:01:28 zimbra kernel: [ 5.896479] type=1505 audit(1330279288.924:10): operation="profile_replace" pid=724 name="/usr/lib/connman/scripts/dhclient-script"
Feb 26 19:01:28 zimbra kernel: [ 5.912828] type=1505 audit(1330279288.944:11): operation="profile_load" pid=725 name="/usr/sbin/named"
Feb 26 19:01:28 zimbra kernel: [ 5.927179] type=1505 audit(1330279288.954:12): operation="profile_load" pid=726 name="/usr/sbin/tcpdump"
Feb 26 19:01:29 zimbra init: ssh main process (380) terminated with status 255
Feb 26 19:01:29 zimbra kernel: [ 6.155556] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 26 19:01:29 zimbra kernel: [ 6.155967] acpiphp: Slot [32] registered
Feb 26 19:01:29 zimbra kernel: [ 6.155991] acpiphp: Slot [33] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156015] acpiphp: Slot [34] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156038] acpiphp: Slot [35] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156061] acpiphp: Slot [36] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156085] acpiphp: Slot [37] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156109] acpiphp: Slot [38] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156132] acpiphp: Slot [39] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156155] acpiphp: Slot [40] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156178] acpiphp: Slot [41] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156202] acpiphp: Slot [42] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156225] acpiphp: Slot [43] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156247] acpiphp: Slot [44] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156270] acpiphp: Slot [45] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156293] acpiphp: Slot [46] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156317] acpiphp: Slot [47] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156341] acpiphp: Slot [48] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156369] acpiphp: Slot [49] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156404] acpiphp: Slot [50] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156439] acpiphp: Slot [51] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156474] acpiphp: Slot [52] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156510] acpiphp: Slot [53] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156543] acpiphp: Slot [54] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156579] acpiphp: Slot [55] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156615] acpiphp: Slot [56] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156652] acpiphp: Slot [57] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156692] acpiphp: Slot [58] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156729] acpiphp: Slot [59] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156766] acpiphp: Slot [60] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156822] acpiphp: Slot [61] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156860] acpiphp: Slot [62] registered
Feb 26 19:01:29 zimbra kernel: [ 6.156896] acpiphp: Slot [63] registered
Feb 26 19:01:29 zimbra kernel: [ 6.157318] acpiphp_glue: Slot 160 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157355] acpiphp_glue: Slot 192 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157389] acpiphp_glue: Slot 224 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157424] acpiphp_glue: Slot 256 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157489] acpiphp_glue: Slot 161 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157523] acpiphp_glue: Slot 162 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157556] acpiphp_glue: Slot 163 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157589] acpiphp_glue: Slot 164 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157623] acpiphp_glue: Slot 165 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157655] acpiphp_glue: Slot 166 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157689] acpiphp_glue: Slot 167 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157722] acpiphp_glue: Slot 193 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157755] acpiphp_glue: Slot 194 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157788] acpiphp_glue: Slot 195 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157821] acpiphp_glue: Slot 196 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157868] acpiphp_glue: Slot 197 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157902] acpiphp_glue: Slot 198 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157935] acpiphp_glue: Slot 199 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.157969] acpiphp_glue: Slot 225 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158002] acpiphp_glue: Slot 226 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158035] acpiphp_glue: Slot 227 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158067] acpiphp_glue: Slot 228 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158099] acpiphp_glue: Slot 229 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158132] acpiphp_glue: Slot 230 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158164] acpiphp_glue: Slot 231 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158196] acpiphp_glue: Slot 257 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158228] acpiphp_glue: Slot 258 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158261] acpiphp_glue: Slot 259 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158293] acpiphp_glue: Slot 260 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158326] acpiphp_glue: Slot 261 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158358] acpiphp_glue: Slot 262 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.158391] acpiphp_glue: Slot 263 already registered by another hotplug driver
Feb 26 19:01:29 zimbra kernel: [ 6.676781] vmmemctl: disagrees about version of symbol module_layout
Feb 26 19:01:29 zimbra kernel: [ 6.710490] vmci: disagrees about version of symbol module_layout
Feb 26 19:01:30 zimbra cron[967]: (CRON) INFO (pidfile fd = 3)
Feb 26 19:01:30 zimbra init: apport pre-start process (961) terminated with status 1
Feb 26 19:01:30 zimbra init: apport post-stop process (981) terminated with status 1
Feb 26 19:01:30 zimbra cron[995]: (CRON) STARTUP (fork ok)
Feb 26 19:01:30 zimbra cron[995]: (CRON) INFO (Running @reboot jobs)
Feb 26 19:01:30 zimbra named[1008]: starting BIND 9.7.0-P1 -u bind
Feb 26 19:01:30 zimbra named[1008]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS='
Feb 26 19:01:30 zimbra named[1008]: adjusted limit on open files from 1024 to 1048576
Feb 26 19:01:30 zimbra named[1008]: found 2 CPUs, using 2 worker threads
Feb 26 19:01:30 zimbra named[1008]: using up to 4096 sockets
Feb 26 19:01:30 zimbra named[1008]: loading configuration from '/etc/bind/named.conf'
Feb 26 19:01:30 zimbra named[1008]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 26 19:01:30 zimbra named[1008]: using default UDP/IPv4 port range: [1024, 65535]
Feb 26 19:01:30 zimbra named[1008]: using default UDP/IPv6 port range: [1024, 65535]
Feb 26 19:01:30 zimbra named[1008]: listening on IPv6 interfaces, port 53
Feb 26 19:01:30 zimbra named[1008]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 26 19:01:30 zimbra named[1008]: listening on IPv4 interface eth0, x.x.193.144#53
Feb 26 19:01:30 zimbra named[1008]: generating session key for dynamic DNS
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: 254.169.IN-ADDR.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.0.IP6.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.0.IP6.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: D.F.IP6.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: 8.E.F.IP6.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: 9.E.F.IP6.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: A.E.F.IP6.ARPA
Feb 26 19:01:30 zimbra named[1008]: automatic empty zone: B.E.F.IP6.ARPA
Feb 26 19:01:30 zimbra named[1008]: command channel listening on 127.0.0.1#953
Feb 26 19:01:30 zimbra named[1008]: command channel listening on ::1#953
Feb 26 19:01:30 zimbra named[1008]: zone 0.in-addr.arpa/IN: loaded serial 1
Feb 26 19:01:30 zimbra named[1008]: zone 127.in-addr.arpa/IN: loaded serial 1
Feb 26 19:01:30 zimbra named[1008]: zone 255.in-addr.arpa/IN: loaded serial 1
Feb 26 19:01:30 zimbra named[1008]: zone localhost/IN: loaded serial 2
Feb 26 19:01:30 zimbra named[1008]: running
Feb 26 19:01:32 zimbra ntpdate[751]: no server suitable for synchronization found
Feb 26 19:01:38 zimbra kernel: [ 15.651871] eth0: no IPv6 routers present
Feb 26 19:02:00 zimbra CRON[1344]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog > /dev/null 2>&1)
Feb 26 19:02:53 zimbra saslauthd: auth_zimbra_init: zimbra_cert_check is off!
Feb 26 19:02:53 zimbra saslauthd: auth_zimbra_init: 1 auth urls initialized for round-robin
Feb 26 19:04:01 zimbra CRON[4035]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog > /dev/null 2>&1)
Feb 26 19:05:01 zimbra CRON[4649]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 26 19:05:01 zimbra CRON[4648]: (zimbra) CMD (/opt/zimbra/libexec/zmcheckduplicatemysqld -e > /dev/null 2>&1)
Feb 26 19:06:01 zimbra CRON[4938]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog > /dev/null 2>&1)
Feb 26 19:06:22 zimbra named[1008]: received control channel command 'reconfig'
Feb 26 19:06:22 zimbra named[1008]: loading configuration from '/etc/bind/named.conf'
Feb 26 19:06:22 zimbra named[1008]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 26 19:06:22 zimbra named[1008]: using default UDP/IPv4 port range: [1024, 65535]
Feb 26 19:06:22 zimbra named[1008]: using default UDP/IPv6 port range: [1024, 65535]
Feb 26 19:06:22 zimbra named[1008]: reloading configuration succeeded
Feb 26 19:06:22 zimbra named[1008]: any newly configured zones are now loaded
Feb 26 19:06:22 zimbra kernel: [ 299.660053] eth0: intr type 3, mode 0, 1 vectors allocated
Feb 26 19:06:22 zimbra kernel: [ 299.660892] eth0: NIC Link is Up 10000 Mbps
Feb 26 19:06:22 zimbra named[1008]: received control channel command 'reconfig'
Feb 26 19:06:22 zimbra named[1008]: loading configuration from '/etc/bind/named.conf'
Feb 26 19:06:22 zimbra named[1008]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 26 19:06:22 zimbra named[1008]: using default UDP/IPv4 port range: [1024, 65535]
Feb 26 19:06:22 zimbra named[1008]: using default UDP/IPv6 port range: [1024, 65535]
Feb 26 19:06:22 zimbra named[1008]: reloading configuration succeeded
Feb 26 19:06:22 zimbra named[1008]: any newly configured zones are now loaded
Feb 26 19:06:22 zimbra init: ssh main process (749) terminated with status 255
Feb 26 19:06:27 zimbra ntpdate[5465]: no server suitable for synchronization found
Feb 26 19:06:32 zimbra kernel: [ 309.648175] eth0: no IPv6 routers present
Feb 26 19:08:01 zimbra CRON[6065]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog > /dev/null 2>&1)
Feb 26 19:10:01 zimbra CRON[6956]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog > /dev/null 2>&1)
Feb 26 19:10:01 zimbra CRON[6958]: (zimbra) CMD (/opt/zimbra/libexec/zmcheckduplicatemysqld -e > /dev/null 2>&1)
Feb 26 19:10:01 zimbra CRON[6957]: (zimbra) CMD (/opt/zimbra/libexec/zmlogprocess > /tmp/logprocess.out 2>&1)
Feb 26 19:10:01 zimbra CRON[6959]: (zimbra) CMD (/opt/zimbra/libexec/zmqueuelog)
Feb 26 19:11:57 zimbra named[1008]: received control channel command 'reconfig'
Feb 26 19:11:57 zimbra named[1008]: loading configuration from '/etc/bind/named.conf'
Feb 26 19:11:57 zimbra named[1008]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 26 19:11:57 zimbra named[1008]: using default UDP/IPv4 port range: [1024, 65535]
Feb 26 19:11:57 zimbra named[1008]: using default UDP/IPv6 port range: [1024, 65535]
Feb 26 19:11:57 zimbra named[1008]: reloading configuration succeeded
Feb 26 19:11:57 zimbra named[1008]: any newly configured zones are now loaded
Feb 26 19:11:57 zimbra kernel: [ 633.647017] eth0: intr type 3, mode 0, 1 vectors allocated
Feb 26 19:11:57 zimbra kernel: [ 633.648160] eth0: NIC Link is Up 10000 Mbps
Feb 26 19:11:57 zimbra named[1008]: received control channel command 'reconfig'
Feb 26 19:11:57 zimbra named[1008]: loading configuration from '/etc/bind/named.conf'
Feb 26 19:11:57 zimbra named[1008]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 26 19:11:57 zimbra named[1008]: using default UDP/IPv4 port range: [1024, 65535]
Feb 26 19:11:57 zimbra named[1008]: using default UDP/IPv6 port range: [1024, 65535]
Feb 26 19:11:57 zimbra named[1008]: reloading configuration succeeded
Feb 26 19:11:57 zimbra named[1008]: any newly configured zones are now loaded
Feb 26 19:11:57 zimbra init: ssh main process (5463) terminated with status 255
Feb 26 19:12:01 zimbra ntpdate[8043]: no server suitable for synchronization found
Feb 26 19:12:01 zimbra CRON[8066]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog > /dev/null 2>&1)
Feb 26 19:12:07 zimbra kernel: [ 644.079114] eth0: no IPv6 routers present

[zyrusthc]

Schau dir mal das an und teste ein wenig --> http://wiki.ubuntuusers.de/ethtool

Was mir an deinem Syslog auffällt ist vor allem das:

Feb 26 19:11:57 zimbra kernel: [ 633.648160] eth0: NIC Link is Up 10000 Mbps

Daher denke ich mal das du vielleicht sowas in deine Netzwerkkonfiguration eintragen musst.

ETHTOOL_OPTS="speed 100 duplex full autoneg off"
Siehe --> http://www.cyberciti.biz/tips/howto-linux-add-ethtool-duplex-settings-permanent.html

Greeez Oli

[hippoth]

Hi Oli,

ich habe deine Rat mit ETHTOOL_OPTS mal umgesetzt aber leider ist das ohne Erfolg geblieben, da dies offensichtlich nicht unterstütz wird.

Ich bekomme folgenden Fehler:


"Setting eth0 speed 100 duplex full ... Cannot set new settings: Operation not supported. Not setting speed. Not setting duplex. Done."

Ich denke auch, dass mein eth0 1000 Mbps unterstützt, zumindest gibt das mir ethtool aus:


@zimbra:~$ sudo ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 1000baseT/Full
10000baseT/Full
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Link partner advertised link modes: Not reported
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: No
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
MDI-X: Unknown
Supports Wake-on: uag
Wake-on: d
Link detected: yes

Von daher ist da vllt. garnichts anzupassen.

Mir sind zwei Zeilen beim Booten des Servers noch aufgefallen ():

VM communication interface --> failed
VM communication interface socket family --> failed
(siehe Screenshot)

Könnte das da mit reinspielen?

Was mich auch wundert. Wenn ich ein "/etc/init.d/networking restart" mache, dann kommt auch folgende Meldung mit:


ssh stop/waiting
ssh start/running, process 4991

Warum startet dann der ssh Server mit durch? Ist das korrekt?