Server Akzeptiert keine Passwörter

Apache, Lighttpd, nginx, Cherokee
lenuweit
Posts: 38
Joined: 2004-12-27 22:04
Location: Edewecht

Server Akzeptiert keine Passwörter

Post by lenuweit » 2008-03-24 17:04

Hallo,
mein Server Akzeptiert keine Passwörter mehr !
Es sind auch keine Webseiten mehr zu Sehen !

Was kann ich da machen ?

krackman
Posts: 20
Joined: 2004-04-09 04:31
Location: Bremen

Re: Server Akzeptiert keine Passwörter

Post by krackman » 2008-03-24 17:12

Ohne mehr Informationen kann man da nichts sagen.
Was geht nicht genau?
Läuft der Webserver überhaupt?
Welche Ports sind überhaupt offen?

User avatar
Joe User
Project Manager
Project Manager
Posts: 11138
Joined: 2003-02-27 01:00
Location: Hamburg

Re: Server Akzeptiert keine Passwörter

Post by Joe User » 2008-03-24 17:22

System komplett neu aufsetzen und künftig regelmässig Updates einspielen und sich mehr um die Sicherheit kümmern.
PayPal.Me/JoeUserFreeBSD Remote Installation
Wings for LifeWings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.

lenuweit
Posts: 38
Joined: 2004-12-27 22:04
Location: Edewecht

Re: Server Akzeptiert keine Passwörter

Post by lenuweit » 2008-03-24 17:37

Hallo,
es geht nichts !
Der Websever läuft !
Komme auch nicht per Putty auf den Server nur mit dem Rescue-System !
Beim Aufruf der Serverdomain kommt dann Die Domain "login.pintax.de" ist nicht verfügbar.

Das System ist ganz neu Installiert worden [ 27.2.2008 ].

Es ist ein RAID System !
Eine Neuinstallation ist zur Zeit nicht Möglich, Da Kunden Accounts auf dem Server Laufen !

freddy36
Posts: 273
Joined: 2008-03-20 17:31

Re: Server Akzeptiert keine Passwörter

Post by freddy36 » 2008-03-24 17:58

Und änder das root pw, etc. im rescue, wieder normal booten, gucken was da nicht stimmt...
login.pintax.de, tolle confixx Standard Page, sicher das du nicht zufällig ne Neuinstallation machen lassen hast? :>

lenuweit
Posts: 38
Joined: 2004-12-27 22:04
Location: Edewecht

Re: Server Akzeptiert keine Passwörter

Post by lenuweit » 2008-03-24 18:08

Hallo,
ich bin Anfänger und kenne mich mit dem Server nicht so aus !

Hier mal der Auszug aus der log/messages

Mar 24 19:03:29 rescue Linux agpgart interface v0.102
Mar 24 19:03:29 rescue bus platform: add driver parport_pc
Mar 24 19:03:29 rescue bus pnp: add driver parport_pc
Mar 24 19:03:29 rescue Registering platform device 'parport_pc.956'. Parent at platform
Mar 24 19:03:29 rescue DEV: registering device: ID = 'parport_pc.956'
Mar 24 19:03:29 rescue bus platform: add device parport_pc.956
Mar 24 19:03:29 rescue platform: Matched Device parport_pc.956 with Driver parport_pc
Mar 24 19:03:29 rescue platform: Probing driver parport_pc with device parport_pc.956
Mar 24 19:03:29 rescue bound device 'parport_pc.956' to driver 'parport_pc'
Mar 24 19:03:29 rescue platform: Bound Device parport_pc.956 to Driver parport_pc
Mar 24 19:03:29 rescue bus platform: remove device parport_pc.956
Mar 24 19:03:29 rescue Registering platform device 'parport_pc.888'. Parent at platform
Mar 24 19:03:29 rescue DEV: registering device: ID = 'parport_pc.888'
Mar 24 19:03:29 rescue bus platform: add device parport_pc.888
Mar 24 19:03:29 rescue platform: Matched Device parport_pc.888 with Driver parport_pc
Mar 24 19:03:29 rescue platform: Probing driver parport_pc with device parport_pc.888
Mar 24 19:03:29 rescue bound device 'parport_pc.888' to driver 'parport_pc'
Mar 24 19:03:29 rescue platform: Bound Device parport_pc.888 to Driver parport_pc
Mar 24 19:03:29 rescue bus platform: remove device parport_pc.888
Mar 24 19:03:29 rescue Registering platform device 'parport_pc.632'. Parent at platform
Mar 24 19:03:29 rescue DEV: registering device: ID = 'parport_pc.632'
Mar 24 19:03:29 rescue bus platform: add device parport_pc.632
Mar 24 19:03:29 rescue platform: Matched Device parport_pc.632 with Driver parport_pc
Mar 24 19:03:29 rescue platform: Probing driver parport_pc with device parport_pc.632
Mar 24 19:03:29 rescue bound device 'parport_pc.632' to driver 'parport_pc'
Mar 24 19:03:29 rescue platform: Bound Device parport_pc.632 to Driver parport_pc
Mar 24 19:03:29 rescue bus platform: remove device parport_pc.632
Mar 24 19:03:29 rescue bus pci: add driver parport_pc
Mar 24 19:03:29 rescue floppy0: no floppy controllers found
Mar 24 19:03:29 rescue RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Mar 24 19:03:29 rescue bus platform: add driver sm501
Mar 24 19:03:29 rescue bus pci: add driver sm501
Mar 24 19:03:29 rescue PPP generic driver version 2.4.2
Mar 24 19:03:29 rescue device class 'ppp': registering
Mar 24 19:03:29 rescue DEV: registering device: ID = 'ppp'
Mar 24 19:03:29 rescue NET: Registered protocol family 24
Mar 24 19:03:29 rescue Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Mar 24 19:03:29 rescue ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Mar 24 19:03:29 rescue bus type 'ide' registered
Mar 24 19:03:29 rescue bus pci: add driver PCI_IDE
Mar 24 19:03:29 rescue pci: Matched Device 0000:00:08.0 with Driver PCI_IDE
Mar 24 19:03:29 rescue pci: Probing driver PCI_IDE with device 0000:00:08.0
Mar 24 19:03:29 rescue bus pnp: add driver ide
Mar 24 19:03:29 rescue Probing IDE interface ide0...
Mar 24 19:03:29 rescue Probing IDE interface ide1...
Mar 24 19:03:29 rescue bus ide: add driver ide-disk
Mar 24 19:03:29 rescue device class 'raid_devices': registering
Mar 24 19:03:29 rescue device class 'spi_transport': registering
Mar 24 19:03:29 rescue device class 'spi_host': registering
Mar 24 19:03:29 rescue device class 'fc_host': registering
Mar 24 19:03:29 rescue device class 'fc_vports': registering
Mar 24 19:03:29 rescue device class 'fc_remote_ports': registering
Mar 24 19:03:29 rescue device class 'fc_transport': registering
Mar 24 19:03:29 rescue Loading iSCSI transport class v2.0-724.
Mar 24 19:03:29 rescue device class 'iscsi_transport': registering
Mar 24 19:03:29 rescue device class 'iscsi_host': registering
Mar 24 19:03:29 rescue device class 'iscsi_connection': registering
Mar 24 19:03:29 rescue device class 'iscsi_session': registering
Mar 24 19:03:29 rescue device class 'sas_host': registering
Mar 24 19:03:29 rescue device class 'sas_phy': registering
Mar 24 19:03:29 rescue device class 'sas_port': registering
Mar 24 19:03:29 rescue device class 'sas_device': registering
Mar 24 19:03:29 rescue device class 'sas_end_device': registering
Mar 24 19:03:29 rescue device class 'sas_expander': registering
Mar 24 19:03:29 rescue device class 'scsi_disk': registering
Mar 24 19:03:29 rescue bus scsi: add driver sd
Mar 24 19:03:29 rescue bus scsi: add driver sr
Mar 24 19:03:29 rescue Fusion MPT base driver 3.04.06
Mar 24 19:03:29 rescue Copyright (c) 1999-2007 LSI Corporation
Mar 24 19:03:29 rescue Fusion MPT SPI Host driver 3.04.06
Mar 24 19:03:29 rescue bus pci: add driver mptspi
Mar 24 19:03:29 rescue Fusion MPT FC Host driver 3.04.06
Mar 24 19:03:29 rescue bus pci: add driver mptfc
Mar 24 19:03:29 rescue Fusion MPT SAS Host driver 3.04.06
Mar 24 19:03:29 rescue bus pci: add driver mptsas
Mar 24 19:03:29 rescue Fusion MPT misc device (ioctl) driver 3.04.06
Mar 24 19:03:29 rescue DEV: registering device: ID = 'mptctl'
Mar 24 19:03:29 rescue mptctl: Registered with Fusion MPT base driver
Mar 24 19:03:29 rescue mptctl: /dev/mptctl @ (major,minor=10,220)
Mar 24 19:03:29 rescue Fusion MPT LAN driver 3.04.06
Mar 24 19:03:29 rescue device class 'aoe': registering
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'err'
Mar 24 19:03:29 rescue class_uevent - name = err
Mar 24 19:03:29 rescue class_device_create_uevent called for err
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'discover'
Mar 24 19:03:29 rescue class_uevent - name = discover
Mar 24 19:03:29 rescue class_device_create_uevent called for discover
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'interfaces'
Mar 24 19:03:29 rescue class_uevent - name = interfaces
Mar 24 19:03:29 rescue class_device_create_uevent called for interfaces
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'revalidate'
Mar 24 19:03:29 rescue class_uevent - name = revalidate
Mar 24 19:03:29 rescue class_device_create_uevent called for revalidate
Mar 24 19:03:29 rescue aoe: AoE v32 initialised.
Mar 24 19:03:29 rescue device class 'usbmon': registering
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbmon0'
Mar 24 19:03:29 rescue bus pci: add driver ehci_hcd
Mar 24 19:03:29 rescue pci: Matched Device 0000:00:02.1 with Driver ehci_hcd
Mar 24 19:03:29 rescue pci: Probing driver ehci_hcd with device 0000:00:02.1
Mar 24 19:03:29 rescue ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 23
Mar 24 19:03:29 rescue ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUB2] -> GSI 23 (level, low) -> IRQ 23
Mar 24 19:03:29 rescue PCI: Setting latency timer of device 0000:00:02.1 to 64
Mar 24 19:03:29 rescue ehci_hcd 0000:00:02.1: EHCI Host Controller
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'usb_host1'
Mar 24 19:03:29 rescue class_uevent - name = usb_host1
Mar 24 19:03:29 rescue class_device_create_uevent called for usb_host1
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbmon1'
Mar 24 19:03:29 rescue ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
Mar 24 19:03:29 rescue ehci_hcd 0000:00:02.1: debug port 1
Mar 24 19:03:29 rescue PCI: cache line size of 64 is not supported by device 0000:00:02.1
Mar 24 19:03:29 rescue ehci_hcd 0000:00:02.1: irq 23, io mem 0xdfcfec00
Mar 24 19:03:29 rescue ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usb1'
Mar 24 19:03:29 rescue bus usb: add device usb1
Mar 24 19:03:29 rescue usb: Matched Device usb1 with Driver usb
Mar 24 19:03:29 rescue usb: Probing driver usb with device usb1
Mar 24 19:03:29 rescue device class 'usb_endpoint': registering
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbdev1.1_ep00'
Mar 24 19:03:29 rescue usb usb1: configuration #1 chosen from 1 choice
Mar 24 19:03:29 rescue DEV: registering device: ID = '1-0:1.0'
Mar 24 19:03:29 rescue bus usb: add device 1-0:1.0
Mar 24 19:03:29 rescue usb: Matched Device 1-0:1.0 with Driver hub
Mar 24 19:03:29 rescue usb: Probing driver hub with device 1-0:1.0
Mar 24 19:03:29 rescue hub 1-0:1.0: USB hub found
Mar 24 19:03:29 rescue hub 1-0:1.0: 8 ports detected
Mar 24 19:03:29 rescue bound device '1-0:1.0' to driver 'hub'
Mar 24 19:03:29 rescue usb: Bound Device 1-0:1.0 to Driver hub
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbdev1.1_ep81'
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbdev1.1'
Mar 24 19:03:29 rescue bound device 'usb1' to driver 'usb'
Mar 24 19:03:29 rescue usb: Bound Device usb1 to Driver usb
Mar 24 19:03:29 rescue bound device '0000:00:02.1' to driver 'ehci_hcd'
Mar 24 19:03:29 rescue pci: Bound Device 0000:00:02.1 to Driver ehci_hcd
Mar 24 19:03:29 rescue 116x: driver isp116x-hcd, 03 Nov 2005
Mar 24 19:03:29 rescue bus platform: add driver isp116x-hcd
Mar 24 19:03:29 rescue ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
Mar 24 19:03:29 rescue bus pci: add driver ohci_hcd
Mar 24 19:03:29 rescue pci: Matched Device 0000:00:02.0 with Driver ohci_hcd
Mar 24 19:03:29 rescue pci: Probing driver ohci_hcd with device 0000:00:02.0
Mar 24 19:03:29 rescue ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 22
Mar 24 19:03:29 rescue ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUB0] -> GSI 22 (level, low) -> IRQ 22
Mar 24 19:03:29 rescue PCI: Setting latency timer of device 0000:00:02.0 to 64
Mar 24 19:03:29 rescue ohci_hcd 0000:00:02.0: OHCI Host Controller
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'usb_host2'
Mar 24 19:03:29 rescue class_uevent - name = usb_host2
Mar 24 19:03:29 rescue class_device_create_uevent called for usb_host2
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbmon2'
Mar 24 19:03:29 rescue ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
Mar 24 19:03:29 rescue ohci_hcd 0000:00:02.0: irq 22, io mem 0xdfcff000
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usb2'
Mar 24 19:03:29 rescue bus usb: add device usb2
Mar 24 19:03:29 rescue usb: Matched Device usb2 with Driver usb
Mar 24 19:03:29 rescue usb: Probing driver usb with device usb2
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbdev2.1_ep00'
Mar 24 19:03:29 rescue usb usb2: configuration #1 chosen from 1 choice
Mar 24 19:03:29 rescue DEV: registering device: ID = '2-0:1.0'
Mar 24 19:03:29 rescue bus usb: add device 2-0:1.0
Mar 24 19:03:29 rescue usb: Matched Device 2-0:1.0 with Driver hub
Mar 24 19:03:29 rescue usb: Probing driver hub with device 2-0:1.0
Mar 24 19:03:29 rescue hub 2-0:1.0: USB hub found
Mar 24 19:03:29 rescue hub 2-0:1.0: 8 ports detected
Mar 24 19:03:29 rescue bound device '2-0:1.0' to driver 'hub'
Mar 24 19:03:29 rescue usb: Bound Device 2-0:1.0 to Driver hub
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbdev2.1_ep81'
Mar 24 19:03:29 rescue DEV: registering device: ID = 'usbdev2.1'
Mar 24 19:03:29 rescue bound device 'usb2' to driver 'usb'
Mar 24 19:03:29 rescue usb: Bound Device usb2 to Driver usb
Mar 24 19:03:29 rescue bound device '0000:00:02.0' to driver 'ohci_hcd'
Mar 24 19:03:29 rescue pci: Bound Device 0000:00:02.0 to Driver ohci_hcd
Mar 24 19:03:29 rescue USB Universal Host Controller Interface driver v3.0
Mar 24 19:03:29 rescue bus pci: add driver uhci_hcd
Mar 24 19:03:29 rescue sl811: driver sl811-hcd, 19 May 2005
Mar 24 19:03:29 rescue bus platform: add driver sl811-hcd
Mar 24 19:03:29 rescue bus pnp: add driver i8042 kbd
Mar 24 19:03:29 rescue pnp: Matched Device 00:07 with Driver i8042 kbd
Mar 24 19:03:29 rescue pnp: Probing driver i8042 kbd with device 00:07
Mar 24 19:03:29 rescue bound device '00:07' to driver 'i8042 kbd'
Mar 24 19:03:29 rescue pnp: Bound Device 00:07 to Driver i8042 kbd
Mar 24 19:03:29 rescue bus pnp: add driver i8042 aux
Mar 24 19:03:29 rescue PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Mar 24 19:03:29 rescue PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Mar 24 19:03:29 rescue bus platform: add driver i8042
Mar 24 19:03:29 rescue Registering platform device 'i8042'. Parent at platform
Mar 24 19:03:29 rescue DEV: registering device: ID = 'i8042'
Mar 24 19:03:29 rescue bus platform: add device i8042
Mar 24 19:03:29 rescue platform: Matched Device i8042 with Driver i8042
Mar 24 19:03:29 rescue platform: Probing driver i8042 with device i8042
Mar 24 19:03:29 rescue serio: i8042 KBD port at 0x60,0x64 irq 1
Mar 24 19:03:29 rescue bound device 'i8042' to driver 'i8042'
Mar 24 19:03:29 rescue platform: Bound Device i8042 to Driver i8042
Mar 24 19:03:29 rescue DEV: registering device: ID = 'mice'
Mar 24 19:03:29 rescue DEV: registering device: ID = 'serio0'
Mar 24 19:03:29 rescue bus serio: add device serio0
Mar 24 19:03:29 rescue DEV: registering device: ID = 'psaux'
Mar 24 19:03:29 rescue mice: PS/2 mouse device common for all mice
Mar 24 19:03:29 rescue bus serio: add driver atkbd
Mar 24 19:03:29 rescue serio: Matched Device serio0 with Driver atkbd
Mar 24 19:03:29 rescue serio: Probing driver atkbd with device serio0
Mar 24 19:03:29 rescue bus serio: add driver psmouse
Mar 24 19:03:29 rescue md: linear personality registered for level -1
Mar 24 19:03:29 rescue md: raid0 personality registered for level 0
Mar 24 19:03:29 rescue md: raid1 personality registered for level 1
Mar 24 19:03:29 rescue md: raid10 personality registered for level 10
Mar 24 19:03:29 rescue raid6: int64x1 2050 MB/s
Mar 24 19:03:29 rescue raid6: int64x2 2738 MB/s
Mar 24 19:03:29 rescue raid6: int64x4 2847 MB/s
Mar 24 19:03:29 rescue raid6: int64x8 1890 MB/s
Mar 24 19:03:29 rescue raid6: sse2x1 3070 MB/s
Mar 24 19:03:29 rescue raid6: sse2x2 4097 MB/s
Mar 24 19:03:29 rescue raid6: sse2x4 4281 MB/s
Mar 24 19:03:29 rescue raid6: using algorithm sse2x4 (4281 MB/s)
Mar 24 19:03:29 rescue md: raid6 personality registered for level 6
Mar 24 19:03:29 rescue md: raid5 personality registered for level 5
Mar 24 19:03:29 rescue md: raid4 personality registered for level 4
Mar 24 19:03:29 rescue md: multipath personality registered for level -4
Mar 24 19:03:29 rescue md: faulty personality registered for level -5
Mar 24 19:03:29 rescue DEV: registering device: ID = 'device-mapper'
Mar 24 19:03:29 rescue device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
Mar 24 19:03:29 rescue bus usb: add driver hiddev
Mar 24 19:03:29 rescue usbcore: registered new interface driver hiddev
Mar 24 19:03:29 rescue bus usb: add driver usbhid
Mar 24 19:03:29 rescue usbcore: registered new interface driver usbhid
Mar 24 19:03:29 rescue drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Mar 24 19:03:29 rescue IPv4 over IPv4 tunneling driver
Mar 24 19:03:29 rescue DEV: registering device: ID = 'tunl0'
Mar 24 19:03:29 rescue GRE over IPv4 tunneling driver
Mar 24 19:03:29 rescue DEV: registering device: ID = 'gre0'
Mar 24 19:03:29 rescue Initializing XFRM netlink socket
Mar 24 19:03:29 rescue NET: Registered protocol family 1
Mar 24 19:03:29 rescue NET: Registered protocol family 10
Mar 24 19:03:29 rescue lo: Disabled Privacy Extensions
Mar 24 19:03:29 rescue tunl0: Disabled Privacy Extensions
Mar 24 19:03:29 rescue IPv6 over IPv4 tunneling driver
Mar 24 19:03:29 rescue DEV: registering device: ID = 'sit0'
Mar 24 19:03:29 rescue sit0: Disabled Privacy Extensions
Mar 24 19:03:29 rescue DEV: registering device: ID = 'ip6tnl0'
Mar 24 19:03:29 rescue NET: Registered protocol family 17
Mar 24 19:03:29 rescue NET: Registered protocol family 15
Mar 24 19:03:29 rescue 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Mar 24 19:03:29 rescue All bugs added by David S. Miller <davem@redhat.com>
Mar 24 19:03:29 rescue ieee80211: 802.11 data/management/control stack, git-1.1.13
Mar 24 19:03:29 rescue ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Mar 24 19:03:29 rescue ieee80211_crypt: registered algorithm 'NULL'
Mar 24 19:03:29 rescue ieee80211_crypt: registered algorithm 'WEP'
Mar 24 19:03:29 rescue ieee80211_crypt: registered algorithm 'CCMP'
Mar 24 19:03:29 rescue ieee80211_crypt: registered algorithm 'TKIP'
Mar 24 19:03:29 rescue Freeing unused kernel memory: 300k freed
Mar 24 19:03:29 rescue DEV: registering device: ID = 'vcs1'
Mar 24 19:03:29 rescue DEV: registering device: ID = 'vcsa1'
Mar 24 19:03:29 rescue eepro100.c:v1.09j-t 9/29/99 Donald Becker
Mar 24 19:03:29 rescue eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
Mar 24 19:03:29 rescue bus pci: add driver eepro100
Mar 24 19:03:29 rescue pci: Matched Device 0000:01:0a.0 with Driver eepro100
Mar 24 19:03:29 rescue pci: Probing driver eepro100 with device 0000:01:0a.0
Mar 24 19:03:29 rescue ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19
Mar 24 19:03:29 rescue ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [LNKC] -> GSI 19 (level, low) -> IRQ 19
Mar 24 19:03:29 rescue eth0: 0000:01:0a.0, 00:02:b3:20:e4:1e, IRQ 19.
Mar 24 19:03:29 rescue Board assembly 721383-016, Physical connectors present: RJ45
Mar 24 19:03:29 rescue Primary interface chip i82555 PHY #1.
Mar 24 19:03:29 rescue General self-test: passed.
Mar 24 19:03:29 rescue Serial sub-system self-test: passed.
Mar 24 19:03:29 rescue Internal registers self-test: passed.
Mar 24 19:03:29 rescue ROM checksum self-test: passed (0x04f4518b).
Mar 24 19:03:29 rescue DEV: registering device: ID = 'eth0'
Mar 24 19:03:29 rescue bound device '0000:01:0a.0' to driver 'eepro100'
Mar 24 19:03:29 rescue pci: Bound Device 0000:01:0a.0 to Driver eepro100
Mar 24 19:03:29 rescue e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
Mar 24 19:03:29 rescue e100: Copyright(c) 1999-2006 Intel Corporation
Mar 24 19:03:29 rescue bus pci: add driver e100
Mar 24 19:03:29 rescue bus pci: add driver sata_nv
Mar 24 19:03:29 rescue pci: Matched Device 0000:00:08.0 with Driver sata_nv
Mar 24 19:03:29 rescue pci: Probing driver sata_nv with device 0000:00:08.0
Mar 24 19:03:29 rescue sata_nv 0000:00:08.0: version 3.5
Mar 24 19:03:29 rescue ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 21
Mar 24 19:03:29 rescue ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LSA0] -> GSI 21 (level, low) -> IRQ 21
Mar 24 19:03:29 rescue PCI: Setting latency timer of device 0000:00:08.0 to 64
Mar 24 19:03:29 rescue scsi0 : sata_nv
Mar 24 19:03:29 rescue DEV: registering device: ID = 'host0'
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'host0'
Mar 24 19:03:29 rescue class_uevent - name = host0
Mar 24 19:03:29 rescue scsi1 : sata_nv
Mar 24 19:03:29 rescue DEV: registering device: ID = 'host1'
Mar 24 19:03:29 rescue CLASS: registering class device: ID = 'host1'
Mar 24 19:03:29 rescue class_uevent - name = host1
Mar 24 19:03:29 rescue ata1: SATA max UDMA/133 cmd 0xe00 ctl 0xe20 bmdma 0xcc00 irq 21
Mar 24 19:03:29 rescue ata2: SATA max UDMA/133 cmd 0xe40 ctl 0xe60 bmdma 0xcc08 irq 21
Mar 24 19:03:29 rescue ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 24 19:03:29 rescue ata1.00: ATA-7: WDC WD1600JS-00NCB1, 10.02E02, max UDMA/133
Mar 24 19:03:29 rescue ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
Mar 24 19:03:29 rescue ata1.00: configured for UDMA/133
Mar 24 19:03:29 rescue ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 24 19:03:29 rescue ata2.00: ATA-7: WDC WD1600JS-00NCB1, 10.02E02, max UDMA/133
Mar 24 19:03:29 rescue ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
Mar 24 19:03:29 rescue ata2.00: configured for UDMA/133
Mar 24 19:03:29 rescue DEV: registering device: ID = 'target0:0:0'
Mar 24 19:03:29 rescue scsi 0:0:0:0: Direct-Access ATA WDC WD1600JS-00N 10.0 PQ: 0 ANSI: 5
Mar 24 19:03:29 rescue DEV: registering device: ID = '0:0:0:0'
Mar 24 19:03:29 rescue bus scsi: add device 0:0:0:0
Mar 24 19:03:29 rescue scsi: Matched Device 0:0:0:0 with Driver sd
Mar 24 19:03:29 rescue scsi: Probing driver sd with device 0:0:0:0
Mar 24 19:03:29 rescue CLASS: registering class device: ID = '0:0:0:0'
Mar 24 19:03:29 rescue class_uevent - name = 0:0:0:0
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] Write Protect is off
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] Write Protect is off
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 24 19:03:29 rescue sda: sda1 sda2 sda3
Mar 24 19:03:29 rescue sd 0:0:0:0: [sda] Attached SCSI disk
Mar 24 19:03:29 rescue bound device '0:0:0:0' to driver 'sd'
Mar 24 19:03:29 rescue scsi: Bound Device 0:0:0:0 to Driver sd
Mar 24 19:03:29 rescue CLASS: registering class device: ID = '0:0:0:0'
Mar 24 19:03:29 rescue class_uevent - name = 0:0:0:0
Mar 24 19:03:29 rescue DEV: registering device: ID = 'target1:0:0'
Mar 24 19:03:29 rescue scsi 1:0:0:0: Direct-Access ATA WDC WD1600JS-00N 10.0 PQ: 0 ANSI: 5
Mar 24 19:03:29 rescue DEV: registering device: ID = '1:0:0:0'
Mar 24 19:03:29 rescue bus scsi: add device 1:0:0:0
Mar 24 19:03:29 rescue scsi: Matched Device 1:0:0:0 with Driver sd
Mar 24 19:03:29 rescue scsi: Probing driver sd with device 1:0:0:0
Mar 24 19:03:29 rescue CLASS: registering class device: ID = '1:0:0:0'
Mar 24 19:03:29 rescue class_uevent - name = 1:0:0:0
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] Write Protect is off
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] Write Protect is off
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 24 19:03:29 rescue sdb: sdb1 sdb2 sdb3
Mar 24 19:03:29 rescue sd 1:0:0:0: [sdb] Attached SCSI disk
Mar 24 19:03:29 rescue bound device '1:0:0:0' to driver 'sd'
Mar 24 19:03:29 rescue scsi: Bound Device 1:0:0:0 to Driver sd
Mar 24 19:03:29 rescue CLASS: registering class device: ID = '1:0:0:0'
Mar 24 19:03:29 rescue class_uevent - name = 1:0:0:0
Mar 24 19:03:29 rescue bound device '0000:00:08.0' to driver 'sata_nv'
Mar 24 19:03:29 rescue pci: Bound Device 0000:00:08.0 to Driver sata_nv
Mar 24 19:03:29 rescue bus pci: add driver pata_acpi
Mar 24 19:03:29 rescue bus pci: add driver ata_generic
Mar 24 19:03:29 rescue BIOS EDD facility v0.16 2004-Jun-25, 6 devices found
Mar 24 19:03:48 rescue sshd[5040]: reverse mapping checking getaddrinfo for g227207173.adsl.alicedsl.de [92.227.207.173] failed - POSSIBLE BREAK-IN ATTEMPT!
Mar 24 19:03:49 rescue sshd[5040]: Failed password for root from 92.227.207.173 port 3445 ssh2
Mar 24 19:03:51 rescue sshd[5040]: Accepted password for root from 92.227.207.173 port 3445 ssh2

User avatar
Joe User
Project Manager
Project Manager
Posts: 11138
Joined: 2003-02-27 01:00
Location: Hamburg

Re: Server Akzeptiert keine Passwörter

Post by Joe User » 2008-03-24 18:13

Lenuweit wrote:Eine Neuinstallation ist zur Zeit nicht Möglich, Da Kunden Accounts auf dem Server Laufen !

Was denn nun? Laufen die Websites oder nicht? Wenn nicht, weisst Du ja was zu tun ist...
PayPal.Me/JoeUserFreeBSD Remote Installation
Wings for LifeWings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.

lenuweit
Posts: 38
Joined: 2004-12-27 22:04
Location: Edewecht

Re: Server Akzeptiert keine Passwörter

Post by lenuweit » 2008-03-24 18:13

Hallo,
nein die Webseiten laufen nicht !
Ich weiss nicht was ich zu tun habe

freddy36
Posts: 273
Joined: 2008-03-20 17:31

Re: Server Akzeptiert keine Passwörter

Post by freddy36 » 2008-03-24 18:23

Die Logs vom rescue System sind uninteressant...
Die Platte mounten, da wären die logs interessant...
Mounte dir dein system z.B. nach /mnt
Dann haste deine Logs unter /mnt/var/log
Mach nen chroot /mnt
Dann solltest du mit passwd die Passwörter ändern können.
unmounten, reboot, als root einloggen, Problem lösen :)
Wenn du keine Ahnung hast wird das sicherlich ein wenig dauern, such dir jemanden der das für dich erledigt.

lenuweit
Posts: 38
Joined: 2004-12-27 22:04
Location: Edewecht

Re: Server Akzeptiert keine Passwörter

Post by lenuweit » 2008-03-24 19:17

Hallo,
ich gebe auf, bekomme es einfach nicht zum Laufen !

Werde mal Sehen was der Serversupport morgen dazu Sagt.

User avatar
Joe User
Project Manager
Project Manager
Posts: 11138
Joined: 2003-02-27 01:00
Location: Hamburg

Re: Server Akzeptiert keine Passwörter

Post by Joe User » 2008-03-24 19:22

Lenuweit wrote:ich gebe auf, bekomme es einfach nicht zum Laufen !

Aber Kunden hosten? Das passt nicht zusammen und kostet Dich hoffentlich das entsprechende Lehrgeld!
Lenuweit wrote:Werde mal Sehen was der Serversupport morgen dazu Sagt.

Vermutlich das Flachse...


Schuster bleib bei Deinen Leisten!
PayPal.Me/JoeUserFreeBSD Remote Installation
Wings for LifeWings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.

foxviper
Posts: 32
Joined: 2007-04-27 16:47

Re: Server Akzeptiert keine Passwörter

Post by foxviper » 2008-03-24 21:57

hi,
warum nutzt du nicht netKVM? damit solltest Du immer ein Shell/root Zugriff erlangen.
dieses geht aber nur bei root-Servern

greets

mex
Posts: 3
Joined: 2008-03-24 21:54

Re: Server Akzeptiert keine Passwörter

Post by mex » 2008-03-24 22:00

moin,

ich habe so etwas ähnliches mal gesehen, da waren /etc/passwd,shadow,group komplett durch
ein konfigurationstool zerschossen, es gab keine benutzer mehr, ergo konnten keine services
gestartet werden & logins gingen auch nicht; wenn du ins rescue_system bootest und das
system mountest, wie sehen dann passwd/shadow etc aus?

mex


Lenuweit wrote:Hallo,
ich gebe auf, bekomme es einfach nicht zum Laufen !

Werde mal Sehen was der Serversupport morgen dazu Sagt.