Hetzner Server - nach update fährt nicht mehr hoch

G

grep666

New Member
Guten Morgen,
nach einem Update fährt der Hetzner Server nicht mehr hoch. Ich habe mit den Rescue System das RAID gemountet und /var/log/messages ausgelesen. Leider finde ich den Grund nicht wieso der Server nicht mehr zu erreichen ist. Ich hatte zu Testzwecken zuvor auch die iptables geflusht, aber das war natürlich noch vor dem restart. Zudem arbeite ich mit Putty, das sollte dann "connection refused" o.ä. melden wenn die iptables sperren. Aber ich bekomme stattdessen "Network error: connection timed out" zu sehen.
Code: 
root@rescue ~ # cd /mnt/
root@rescue /mnt # mkdir rescue
root@rescue /mnt # mount -o ro /dev/md2 /mnt/rescue/
root@rescue /mnt # cat rescue/var/log/messages | tail -100

Apr 15 03:12:25 server kernel: [    3.176941] ata4: SATA link down (SStatus 0 SControl 300)
Apr 15 03:12:25 server kernel: [    3.512868] ata5: SATA link down (SStatus 0 SControl 300)
Apr 15 03:12:25 server kernel: [    3.848793] ata6: SATA link down (SStatus 0 SControl 300)
Apr 15 03:12:25 server kernel: [    3.869895] sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Apr 15 03:12:25 server kernel: [    3.869970] sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Apr 15 03:12:25 server kernel: [    3.870016] sd 0:0:0:0: [sda] Write Protect is off
Apr 15 03:12:25 server kernel: [    3.870042] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 15 03:12:25 server kernel: [    3.870168]  sda:
Apr 15 03:12:25 server kernel: [    3.870213] sd 1:0:0:0: [sdb] Write Protect is off
Apr 15 03:12:25 server kernel: [    3.870330] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 15 03:12:25 server kernel: [    3.870535]  sdb: sda1 sda2 sda3
Apr 15 03:12:25 server kernel: [    3.882041] sd 0:0:0:0: [sda] Attached SCSI disk
Apr 15 03:12:25 server kernel: [    3.887930]  sdb1 sdb2 sdb3
Apr 15 03:12:25 server kernel: [    3.888541] sd 1:0:0:0: [sdb] Attached SCSI disk
Apr 15 03:12:25 server kernel: [    4.112837] md: raid0 personality registered for level 0
Apr 15 03:12:25 server kernel: [    4.115133] md: raid1 personality registered for level 1
Apr 15 03:12:25 server kernel: [    4.116578] async_tx: api initialized (async)
Apr 15 03:12:25 server kernel: [    4.116935] xor: automatically using best checksumming function: generic_sse
Apr 15 03:12:25 server kernel: [    4.136604]    generic_sse: 11617.000 MB/sec
Apr 15 03:12:25 server kernel: [    4.136652] xor: using function: generic_sse (11617.000 MB/sec)
Apr 15 03:12:25 server kernel: [    4.204593] raid6: int64x1   3093 MB/s
Apr 15 03:12:25 server kernel: [    4.272576] raid6: int64x2   3931 MB/s
Apr 15 03:12:25 server kernel: [    4.340556] raid6: int64x4   2786 MB/s
Apr 15 03:12:25 server kernel: [    4.408557] raid6: int64x8   2701 MB/s
Apr 15 03:12:25 server kernel: [    4.476533] raid6: sse2x1    7634 MB/s
Apr 15 03:12:25 server kernel: [    4.544512] raid6: sse2x2    8929 MB/s
Apr 15 03:12:25 server kernel: [    4.612500] raid6: sse2x4   10289 MB/s
Apr 15 03:12:25 server kernel: [    4.612547] raid6: using algorithm sse2x4 (10289 MB/s)
Apr 15 03:12:25 server kernel: [    4.615130] md: raid6 personality registered for level 6
Apr 15 03:12:25 server kernel: [    4.615181] md: raid5 personality registered for level 5
Apr 15 03:12:25 server kernel: [    4.615231] md: raid4 personality registered for level 4
Apr 15 03:12:25 server kernel: [    4.618975] md: raid10 personality registered for level 10
Apr 15 03:12:25 server kernel: [    4.620885] 3ware Storage Controller device driver for Linux v1.26.02.002.
Apr 15 03:12:25 server kernel: [    4.622961] 3ware 9000 Storage Controller device driver for Linux v2.26.02.012.
Apr 15 03:12:25 server kernel: [    4.625601] Adaptec aacraid driver 1.1-7[28000]-ms
Apr 15 03:12:25 server kernel: [    4.681150] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.681214] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.681579] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.681681] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.681984] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.682040] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.682350] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.682405] mdadm: sending ioctl 1261 to a partition!
Apr 15 03:12:25 server kernel: [    4.682728] mdadm: sending ioctl 800c0910 to a partition!
Apr 15 03:12:25 server kernel: [    4.682784] mdadm: sending ioctl 800c0910 to a partition!
Apr 15 03:12:25 server kernel: [    4.689602] md: md0 stopped.
Apr 15 03:12:25 server kernel: [    4.691047] md: bind<sdb1>
Apr 15 03:12:25 server kernel: [    4.691348] md: bind<sda1>
Apr 15 03:12:25 server kernel: [    4.693424] raid1: raid set md0 active with 2 out of 2 mirrors
Apr 15 03:12:25 server kernel: [    4.693487] md0: detected capacity change from 0 to 2146369536
Apr 15 03:12:25 server kernel: [    4.694117]  md0: unknown partition table
Apr 15 03:12:25 server kernel: [    4.738463] md: md1 stopped.
Apr 15 03:12:25 server kernel: [    4.741754] md: bind<sdb2>
Apr 15 03:12:25 server kernel: [    4.742105] md: bind<sda2>
Apr 15 03:12:25 server kernel: [    4.743732] raid1: raid set md1 active with 2 out of 2 mirrors
Apr 15 03:12:25 server kernel: [    4.743796] md1: detected capacity change from 0 to 536805376
Apr 15 03:12:25 server kernel: [    4.744263]  md1: unknown partition table
Apr 15 03:12:25 server kernel: [    4.769973] md: md2 stopped.
Apr 15 03:12:25 server kernel: [    4.771670] md: bind<sdb3>
Apr 15 03:12:25 server kernel: [    4.771984] md: bind<sda3>
Apr 15 03:12:25 server kernel: [    4.773770] raid1: raid set md2 active with 2 out of 2 mirrors
Apr 15 03:12:25 server kernel: [    4.773869] md2: detected capacity change from 0 to 1497617072128
Apr 15 03:12:25 server kernel: [    4.774431]  md2: unknown partition table
Apr 15 03:12:25 server kernel: [    4.778598] device-mapper: uevent: version 1.0.3
Apr 15 03:12:25 server kernel: [    4.778725] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
Apr 15 03:12:25 server kernel: [    5.004684] EXT4-fs (md2): mounted filesystem with ordered data mode
Apr 15 03:12:25 server kernel: [    6.655564] udev[558]: starting version 164
Apr 15 03:12:25 server kernel: [    6.934832] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
Apr 15 03:12:25 server kernel: [    6.934908] ACPI: Power Button [PWRB]
Apr 15 03:12:25 server kernel: [    6.938228] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Apr 15 03:12:25 server kernel: [    6.938300] ACPI: Power Button [PWRF]
Apr 15 03:12:25 server kernel: [    6.985559] input: PC Speaker as /devices/platform/pcspkr/input/input4
Apr 15 03:12:25 server kernel: [    6.992632] ACPI: WMI: Mapper loaded
Apr 15 03:12:25 server kernel: [    7.198190] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Apr 15 03:12:25 server kernel: [    7.243923] [drm] Initialized drm 1.1.0 20060810
Apr 15 03:12:25 server kernel: [    7.433201] HDA Intel 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Apr 15 03:12:25 server kernel: [    7.581380] [drm] radeon defaulting to userspace modesetting.
Apr 15 03:12:25 server kernel: [    7.581696] pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Apr 15 03:12:25 server kernel: [    7.582135] [drm] Initialized radeon 1.32.0 20080528 for 0000:02:00.0 on minor 0
Apr 15 03:12:25 server kernel: [    8.507616] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x002f0d00
Apr 15 03:12:25 server kernel: [    8.836651] Adding 2096056k swap on /dev/md0.  Priority:-1 extents:1 across:2096056k
Apr 15 03:12:25 server kernel: [    8.840898] EXT4-fs (md2): warning: checktime reached, running e2fsck is recommended
Apr 15 03:12:25 server kernel: [    8.999545] loop: module loaded
Apr 15 03:12:25 server kernel: [    9.877732] kjournald starting.  Commit interval 5 seconds
Apr 15 03:12:25 server kernel: [    9.877740] EXT3-fs warning: checktime reached, running e2fsck is recommended
Apr 15 03:12:25 server kernel: [    9.895746] EXT3 FS on md1, internal journal
Apr 15 03:12:25 server kernel: [    9.895831] EXT3-fs: mounted filesystem with ordered data mode.
Apr 15 03:12:25 server kernel: [   11.116344] r8169 0000:06:00.0: eth0: link down
Apr 15 03:12:25 server kernel: [   11.116411] r8169 0000:06:00.0: eth0: link down
Apr 15 03:12:25 server kernel: [   11.117612] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 15 03:12:25 server kernel: [   11.769052] VFS (md2): Writes happened before quota was turned on thus quota information is probably inconsistent. Please run quotacheck(8).
Apr 15 03:12:25 server kernel: [   11.837904] VFS (md2): Writes happened before quota was turned on thus quota information is probably inconsistent. Please run quotacheck(8).
Apr 15 03:12:25 server kernel: [   12.771906] r8169 0000:06:00.0: eth0: link up
Apr 15 03:12:25 server kernel: [   12.773137] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 15 03:12:25 server kernel: [   17.363242] ip_tables: (C) 2000-2006 Netfilter Core Team
Apr 15 03:12:25 server kernel: [   17.580160] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Apr 15 03:12:25 server kernel: [   17.580345] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
Apr 15 03:12:25 server kernel: [   17.580414] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
Apr 15 03:12:25 server kernel: [   17.580483] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Apr 15 03:15:05 server kernel: [  180.033652] ip6_tables: (C) 2000-2006 Netfilter Core Team

Ich sehe das keine Fehler die darauf hinweisen würden wieso ich den server nicht mehr erreichen kann.

Hier syslog
Code: 
root@rescue /mnt # cat rescue/var/log/syslog | tail -100
Apr 15 03:12:25 server kernel: [    4.769973] md: md2 stopped.
Apr 15 03:12:25 server kernel: [    4.771670] md: bind<sdb3>
Apr 15 03:12:25 server kernel: [    4.771984] md: bind<sda3>
Apr 15 03:12:25 server kernel: [    4.773770] raid1: raid set md2 active with 2 out of 2 mirrors
Apr 15 03:12:25 server kernel: [    4.773869] md2: detected capacity change from 0 to 1497617072128
Apr 15 03:12:25 server kernel: [    4.774431]  md2: unknown partition table
Apr 15 03:12:25 server kernel: [    4.778598] device-mapper: uevent: version 1.0.3
Apr 15 03:12:25 server kernel: [    4.778725] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
Apr 15 03:12:25 server kernel: [    5.004684] EXT4-fs (md2): mounted filesystem with ordered data mode
Apr 15 03:12:25 server kernel: [    6.655564] udev[558]: starting version 164
Apr 15 03:12:25 server kernel: [    6.934832] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
Apr 15 03:12:25 server kernel: [    6.934908] ACPI: Power Button [PWRB]
Apr 15 03:12:25 server kernel: [    6.938228] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Apr 15 03:12:25 server kernel: [    6.938300] ACPI: Power Button [PWRF]
Apr 15 03:12:25 server kernel: [    6.985559] input: PC Speaker as /devices/platform/pcspkr/input/input4
Apr 15 03:12:25 server kernel: [    6.992632] ACPI: WMI: Mapper loaded
Apr 15 03:12:25 server kernel: [    7.198190] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Apr 15 03:12:25 server kernel: [    7.243923] [drm] Initialized drm 1.1.0 20060810
Apr 15 03:12:25 server kernel: [    7.433201] HDA Intel 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Apr 15 03:12:25 server kernel: [    7.433487] HDA Intel 0000:02:00.1: setting latency timer to 64
Apr 15 03:12:25 server kernel: [    7.489592] Error: Driver 'pcspkr' is already registered, aborting...
Apr 15 03:12:25 server kernel: [    7.581380] [drm] radeon defaulting to userspace modesetting.
Apr 15 03:12:25 server kernel: [    7.581696] pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Apr 15 03:12:25 server kernel: [    7.581752] pci 0000:02:00.0: setting latency timer to 64
Apr 15 03:12:25 server kernel: [    7.582135] [drm] Initialized radeon 1.32.0 20080528 for 0000:02:00.0 on minor 0
Apr 15 03:12:25 server kernel: [    8.507616] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x002f0d00
Apr 15 03:12:25 server kernel: [    8.836651] Adding 2096056k swap on /dev/md0.  Priority:-1 extents:1 across:2096056k
Apr 15 03:12:25 server kernel: [    8.840898] EXT4-fs (md2): warning: checktime reached, running e2fsck is recommended
Apr 15 03:12:25 server kernel: [    8.999545] loop: module loaded
Apr 15 03:12:25 server kernel: [    9.877732] kjournald starting.  Commit interval 5 seconds
Apr 15 03:12:25 server kernel: [    9.877740] EXT3-fs warning: checktime reached, running e2fsck is recommended
Apr 15 03:12:25 server kernel: [    9.895746] EXT3 FS on md1, internal journal
Apr 15 03:12:25 server kernel: [    9.895831] EXT3-fs: mounted filesystem with ordered data mode.
Apr 15 03:12:25 server kernel: [   11.116344] r8169 0000:06:00.0: eth0: link down
Apr 15 03:12:25 server kernel: [   11.116411] r8169 0000:06:00.0: eth0: link down
Apr 15 03:12:25 server kernel: [   11.117612] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 15 03:12:25 server kernel: [   11.769052] VFS (md2): Writes happened before quota was turned on thus quota information is probably inconsistent. Please run quotacheck(8).
Apr 15 03:12:25 server kernel: [   11.837904] VFS (md2): Writes happened before quota was turned on thus quota information is probably inconsistent. Please run quotacheck(8).
Apr 15 03:12:25 server kernel: [   12.771906] r8169 0000:06:00.0: eth0: link up
Apr 15 03:12:25 server kernel: [   12.773137] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 15 03:12:25 server kernel: [   17.363242] ip_tables: (C) 2000-2006 Netfilter Core Team
Apr 15 03:12:25 server kernel: [   17.580160] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Apr 15 03:12:25 server kernel: [   17.580345] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
Apr 15 03:12:25 server kernel: [   17.580414] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
Apr 15 03:12:25 server kernel: [   17.580483] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Apr 15 03:12:26 server ntpd[1846]: Deferring DNS for ntp1.hetzner.de 1
Apr 15 03:12:26 server ntpd[1846]: Deferring DNS for ntp2.hetzner.com 1
Apr 15 03:12:26 server ntpd[1846]: Deferring DNS for ntp3.hetzner.net 1
Apr 15 03:12:26 server ntpd[1846]: Deferring DNS for 0.debian.pool.ntp.org 1
Apr 15 03:12:26 server ntpd[1846]: Deferring DNS for 1.debian.pool.ntp.org 1
Apr 15 03:12:26 server ntpd[1897]: signal_no_reset: signal 17 had flags 4000000
Apr 15 03:12:27 server mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Apr 15 03:12:27 server mysqld: 130415  3:12:27 [Note] Plugin 'FEDERATED' is disabled.
Apr 15 03:12:27 server mysqld: 130415  3:12:27  InnoDB: Initializing buffer pool, size = 8.0M
Apr 15 03:12:27 server mysqld: 130415  3:12:27  InnoDB: Completed initialization of buffer pool
Apr 15 03:12:28 server ntpd_intres[1897]: host name not found: ntp1.hetzner.de
Apr 15 03:12:28 server ntpd_intres[1897]: host name not found: ntp2.hetzner.com
Apr 15 03:12:28 server ntpd_intres[1897]: host name not found: ntp3.hetzner.net
Apr 15 03:12:28 server ntpd_intres[1897]: host name not found: 0.debian.pool.ntp.org
Apr 15 03:12:28 server ntpd_intres[1897]: host name not found: 1.debian.pool.ntp.org
Apr 15 03:12:28 server kernel: [   23.124746] eth0: no IPv6 routers present
Apr 15 03:12:29 server mysqld: 130415  3:12:29  InnoDB: Started; log sequence number 9 3575012884
Apr 15 03:12:29 server mysqld: 130415  3:12:29 [Note] Event Scheduler: Loaded 0 events
Apr 15 03:12:29 server mysqld: 130415  3:12:29 [Note] /usr/sbin/mysqld: ready for connections.
Apr 15 03:12:29 server mysqld: Version: '5.1.61-0+squeeze1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
Apr 15 03:12:29 server /etc/mysql/debian-start[2130]: Upgrading MySQL tables if necessary.
Apr 15 03:12:30 server /etc/mysql/debian-start[2134]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 15 03:12:30 server /etc/mysql/debian-start[2134]: Looking for 'mysql' as: /usr/bin/mysql
Apr 15 03:12:30 server /etc/mysql/debian-start[2134]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 15 03:12:30 server /etc/mysql/debian-start[2134]: This installation of MySQL is already upgraded to 5.1.61, use --force if you still need to run mysql_upgrade
Apr 15 03:12:30 server /etc/mysql/debian-start[2141]: Checking for insecure root accounts.
Apr 15 03:12:30 server /etc/mysql/debian-start[2145]: Triggering myisam-recover for all MyISAM tables
Apr 15 03:12:34 server /usr/sbin/cron[2311]: (CRON) INFO (pidfile fd = 3)
Apr 15 03:12:34 server /usr/sbin/cron[2312]: (CRON) STARTUP (fork ok)
Apr 15 03:12:34 server cron[2312]: Error: bad username; while reading /etc/cron.d/ispc_web8
Apr 15 03:12:34 server /usr/sbin/cron[2312]: (*system*ispc_web8) ERROR (Syntax error, this crontab file will be ignored)
Apr 15 03:12:34 server /usr/sbin/cron[2312]: (CRON) INFO (Running @reboot jobs)
Apr 15 03:12:36 server postfix/master[2404]: daemon started -- version 2.7.1, configuration /etc/postfix
Apr 15 03:13:01 server /USR/SBIN/CRON[2446]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Apr 15 03:13:30 server ntpd_intres[1897]: host name not found: ntp1.hetzner.de
Apr 15 03:13:30 server ntpd_intres[1897]: host name not found: ntp2.hetzner.com
Apr 15 03:13:30 server ntpd_intres[1897]: host name not found: ntp3.hetzner.net
Apr 15 03:13:30 server ntpd_intres[1897]: host name not found: 0.debian.pool.ntp.org
Apr 15 03:13:30 server ntpd_intres[1897]: host name not found: 1.debian.pool.ntp.org
Apr 15 03:14:01 server /USR/SBIN/CRON[2760]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Apr 15 03:15:01 server /USR/SBIN/CRON[2768]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Apr 15 03:15:02 server /USR/SBIN/CRON[2772]: (getmail) CMD (/usr/local/bin/run-getmail.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Apr 15 03:15:05 server pop3d: Connection, ip=[::ffff:127.0.0.1]
Apr 15 03:15:05 server pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Apr 15 03:15:05 server imapd: Connection, ip=[::ffff:127.0.0.1]
Apr 15 03:15:05 server imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Apr 15 03:15:05 server kernel: [  180.033652] ip6_tables: (C) 2000-2006 Netfilter Core Team
Apr 15 03:15:05 server postfix/smtpd[2793]: connect from localhost[127.0.0.1]
Apr 15 03:15:05 server postfix/smtpd[2793]: lost connection after CONNECT from localhost[127.0.0.1]
Apr 15 03:15:05 server postfix/smtpd[2793]: disconnect from localhost[127.0.0.1]
Apr 15 03:15:32 server ntpd_intres[1897]: host name not found: ntp1.hetzner.de
Apr 15 03:15:32 server ntpd_intres[1897]: host name not found: ntp2.hetzner.com
Apr 15 03:15:32 server ntpd_intres[1897]: host name not found: ntp3.hetzner.net
Apr 15 03:15:32 server ntpd_intres[1897]: host name not found: 0.debian.pool.ntp.org
Apr 15 03:15:32 server ntpd_intres[1897]: host name not found: 1.debian.pool.ntp.org

Ich habe mit fsck -C0 /dev/md2 gescannt:
Code: 
root@rescue /mnt # fsck -C0 /dev/md2
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/md2: clean, 5445568/91414528 files, 24363058/365629168 blocks

Weiß jemand einen Rat?
 
Ich habe mit --bind die /dev /proc /sys gemounted.

Code: 
root@rescue:/# cat /etc/network/interfaces
### Hetzner Online AG - installimage
# Loopback device:
auto lo
iface lo inet loopback

# device: eth0
auto  eth0
iface eth0 inet static
  address   123.456.78.90
  broadcast 123.456.78.223
  netmask   255.255.255.224
  gateway   fe80::1
ip route add default via fe80::1 dev eth0

# default route to access subnet
up route add -net 123.456.78.90 netmask 255.255.255.224 gw 123.456.78.91 eth0

iface eth0 inet6 static
  # Haupt-IPv6-Adresse des Servers
  address xxxx:xxxx:xxxx:xxxx::2
  netmask 64
  # Host-Route, da das Gateway ausserhalb des eigenen /64 Blocks liegt
  up ip -6 route add xxxx:xxxx:xxxx:xxxx::2 dev eth0
  # Host-Route, da das Gateway ausserhalb des eigenen /64 Blocks liegt
  down ip -6 route del xxxx:xxxx:xxxx:xxxx::2 dev eth0
  # Default Route
  gateway fe80::1
  up ip -6 route add default via xxxx:xxxx:xxxx:xxxx::2 dev eth0
  down ip -6 route del default via xxxx:xxxx:xxxx:xxxx::2 dev eth0

Ich glaube, ich habe den Fehler gemacht und die iptables regeln gekillt. Ich schrieb folgendes:
Code: 
# iptables -F
# iptables -X
# iptables -t nat -F
# iptables -t nat -X
# iptables -t mangle -F
# iptables -t mangle -X

aber ich vergaß das zu schreiben:
Code: 
# iptables -P INPUT ACCEPT
# iptables -P OUTPUT ACCEPT

Und habe mich somit ausgesperrt. Kann das sein und wie kann ich das wieder gut machen?
 
Du hast uns die falsche Datei gegeben. Bitte nochmal versuchen ;)

(Tipp: Du hast uns die interface datei vom Rescue System gegeben, nicht von deinem OS)
 
Hi,
leider nicht - es war die richtige. :(

Code: 
root@rescue ~ # mkdir /mnt/rescue
root@rescue ~ # mount /dev/md2 /mnt/rescue/
root@rescue ~ # cat /mnt/rescue/etc/network/interfaces
### Hetzner Online AG - installimage
# Loopback device:
auto lo
iface lo inet loopback

# device: eth0
auto  eth0
iface eth0 inet static
  address   123.456.78.90
  broadcast 123.456.78.223
  netmask   255.255.255.224
  gateway   fe80::1
ip route add default via fe80::1 dev eth0

# default route to access subnet
up route add -net 123.456.78.92 netmask 255.255.255.224 gw 123.456.78.93 eth0

iface eth0 inet6 static
  # Haupt-IPv6-Adresse des Servers
  address xxxx:xxxx:xxxx:xxxx::2
  netmask 64
  # Host-Route, da das Gateway ausserhalb des eigenen /64 Blocks liegt
  up ip -6 route add xxxx:xxxx:xxxx:xxxx::2 dev eth0
  # Host-Route, da das Gateway ausserhalb des eigenen /64 Blocks liegt
  down ip -6 route del xxxx:xxxx:xxxx:xxxx::2 dev eth0
  # Default Route
  gateway fe80::1
  up ip -6 route add default via xxxx:xxxx:xxxx:xxxx::2 dev eth0
  down ip -6 route del default via xxxx:xxxx:xxxx:xxxx::2 dev eth0
 
Ich hatte in iptables vorher folgende Regeln:
Code: 
/sbin/iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
fail2ban-sasl  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 25,465,143,220,993,110,995
fail2ban-pure-ftpd  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 21,20,990,989
fail2ban-courierimaps  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 993
fail2ban-ssh  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 22
fail2ban-courierimap  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 143
fail2ban-courierpop3s  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 995
fail2ban-courierpop3  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 110

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain fail2ban-courierimap (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-courierimaps (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-courierpop3 (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-courierpop3s (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-pure-ftpd (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-sasl (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-ssh (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0
 
Kann man über rescue pakete verwalten?

Ich habe in /var/log/messages folgende Fehlermeldungen entdeckt:
Code: 
root@rescue ~ # cat /mnt/rescue/var/log/messages | grep 'permission'
Apr 15 03:38:53 server lswred[1799]: none:0: open: /etc/bind/rndc.key: permission denied
Apr 15 03:38:53 server lswred[1799]: couldn't add command channel 127.0.0.1#953: permission denied
Apr 15 03:38:53 server lswred[1799]: none:0: open: /etc/bind/rndc.key: permission denied
Apr 15 03:38:53 server lswred[1799]: couldn't add command channel ::1#953: permission denied
Apr 15 04:12:25 server lswred[1793]: none:0: open: /etc/bind/rndc.key: permission denied
Apr 15 04:12:25 server lswred[1793]: couldn't add command channel 127.0.0.1#953: permission denied
Apr 15 04:12:25 server lswred[1793]: none:0: open: /etc/bind/rndc.key: permission denied
Apr 15 04:12:25 server lswred[1793]: couldn't add command channel ::1#953: permission denied
Apr 15 05:48:23 server lswred[1744]: none:0: open: /etc/bind/rndc.key: permission denied
Apr 15 05:48:23 server lswred[1744]: couldn't add command channel 127.0.0.1#953: permission denied
Apr 15 05:48:23 server lswred[1744]: none:0: open: /etc/bind/rndc.key: permission denied
Apr 15 05:48:23 server lswred[1744]: couldn't add command channel ::1#953: permission denied
 
Ich würde die interface Datei mal richtig anpassen.
Warum ist bei der IPv4 Adresse ein IPv6 Gateway eingetragen?

Code: 
### Hetzner Online AG - installimage
# Loopback device:
auto lo
iface lo inet loopback

# device: eth0
auto  eth0
iface eth0 inet static
  address   123.456.78.90
  broadcast 123.456.78.223
  netmask   255.255.255.224
  gateway  123.456.78.93

# default route to access subnet
up route add -net 123.456.78.92 netmask 255.255.255.224 gw 123.456.78.93 eth0

iface eth0 inet6 static
  # Haupt-IPv6-Adresse des Servers
  address xxxx:xxxx:xxxx:xxxx::2
  netmask 64
  gateway fe80::1
 
Gehst du davon aus?
Code: 
# device: eth0
auto  eth0
iface eth0 inet static
  address   123.456.78.90
  broadcast 123.456.78.223
  netmask   255.255.255.224
  gateway   fe80::1
ip route add default via fe80::1 dev eth0

Die IP Adressen (dummy 123.456.78.x) sind natürlich öffentlich. Das gateway war schon so, es scheint bei der konfiguration so automatisch erstellt worden zu sein. Wissentlich habe ich da nichts verändert. Beachte die letzte Zeile.
 
nevakee said:
Ich würde die interface Datei mal richtig anpassen.
Warum ist bei der IPv4 Adresse ein IPv6 Gateway eingetragen?
Click to expand...

Ich habe es jetzt ausprobiert - eine Änderung! Jetzt bekomme ich die Meldung "connection refused". Das bedeutet, daß der Server schonmal oben ist. Leider nicht die ganzen Dienste, die Webseite usw. sind nicht erreichbar. Ist aber ein Fortschritt.
 
grep666 said:
Kann man über rescue pakete verwalten?

Ich habe in /var/log/messages folgende Fehlermeldungen entdeckt:
Code: 
...
Click to expand...

Vom Rescue aus:
Code: 
mkdir /hdd
mount /dev/md2 /hdd
chroot /hdd

Dann solltest du auch Pakete verwalten können. Wenn du nach aktuellem Stand "Connection refused" bekommst, solltest du deine iptables-Regeln mal überprüfen, bzw. ggf. vorerst ganz entfernen, was mit den gleichen Schritten möglich ist.

PS: Und am Ende natürlich unmount nicht vergessen:

Code: 
exit
umount /hdd
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top