Servereboot didnt work

Hi together,

ive tryed to restart my server,
but it didnt come back,
i can access the server only with the rescueconsole from my hoster,
before i restart the server i saw that i cant access the yast2, thats are the last entries at the time where i want to start yast2 from y2log



2010-09-13 10:44:11 <3> G041(23864) [liby2] genericfrontend.cc(signal_handler):196 got signal 11 at YCP file :0
2010-09-13 10:44:11 <3> G041(23864) [liby2] genericfrontend.cc(log_stored_debug):120 Liberating suppressed debugging messages:
2010-09-13 10:44:11 <3> G041(23864) [liby2] genericfrontend.cc(log_stored_debug):122 End of suppressed debugging messages
2010-09-13 10:44:11 <3> G041(23864) [liby2] genericfrontend.cc(log_backtrace):144 Back trace:

   Frame  0: /usr/lib64/liby2.so.2  log_backtrace()
   Frame  1: /usr/lib64/liby2.so.2  signal_handler(int)
   Frame  2: /lib64/libc.so.6 [0x7f744c6d36e0]
   Frame  3: /usr/lib64/liby2.so.2(main+0x20e) [0x7f744ec3cb7e]
   Frame  4: /lib64/libc.so.6(__libc_start_main+0xe6) [0x7f744c6bf586]
   Frame  5: /usr/lib/YaST2/bin/y2base [0x4006b9]

== End of back trace ===


thats what i have in my bootmsg



Boot logging started on /dev/tty1(/dev/console) at Mon Sep 13 10:46:22 2010

Master Resource Control: previous runlevel: 3, switching to runlevel: 6
Shutting down httpd2 (waiting for all children to terminate) <notice>startproc: execve (/usr/bin/fail2ban-client)  /usr/bin/fail2ban-client -q stop ],  CONSOLE=/dev/console ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 REDIRECT=/dev/tty1 COLUMNS=124 PATH=/usr/sbin:/usr/bin:/usr/sbin:/sbin:/usr/sbin:/usr/bin:/bin vga=0x317 RUNLEVEL=6 PWD=/ SPLASHCFG=/etc/bootsplash/themes/openSUSE/config/bootsplash-1024x768.cfg PREVLEVEL=3 LINES=44 HOME=/ SHLVL=2 SPLASH=yes ROOTFS_BLKDEV=/dev/sda1 _=/sbin/startproc DAEMON=/usr/bin/fail2ban-client ]
Shutting down java.binfmt_misc done
Shutting down auditd done
<notice>killproc: kill(3040,15)
<notice>killproc: kill(2904,15)
<notice>killproc: kill(2903,15)
<notice>killproc: kill(2902,15)
<notice>killproc: kill(2900,15)
<notice>killproc: kill(2872,15)
Shutting down CRON daemondone
Shutting down Fail2ban done
Shutting down service saslauthddone
Saving random seeddone
done
<notice>killproc: kill(2813,3)
Shutting down xinetd:done
<notice>killproc: kill(2891,15)
Shutting down SSH daemondone
Killing ossec-monitord .. 
Killing ossec-logcollector .. 
Killing ossec-syscheckd .. 
Killing ossec-analysisd .. 
Killing ossec-maild .. 
Killing ossec-execd .. 
OSSEC HIDS v1.6.1 Stopped
Shutting down (remotefs) network interfaces:
ERROR  No section: 'Definition'
ERROR  Unable to contact server. Is it running?
<notice>killproc: kill(1740,15)
Shutting down HAL daemondone
done
<notice>killproc: kill(2946,15)
Shutting down mail service (Postfix)done
Shutting down service MySQL done
Not stopping NFS client services:unused
Shutting down rpcbind <notice>killproc: kill(2327,15)
done
Shutting down syslog services<notice>killproc: kill(2219,15)
<notice>killproc: kill(2216,15)
done
Shutting down (localfs) network interfaces:
    eth0      device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
    eth0     
doneShutting down service (localfs) network  .  .  .  .  .  .  .  .  .done
Shutting down D-Bus daemon<notice>killproc: kill(1710,15)
done
<notice>killproc: kill(24524,3)


im not a real linuxprof so how could i see why my system didnt start right? :slight_smile:

thanks and best regards

What OpenSuse version?

This happened when? First reboot after install? After an update? something else?

This appears to be a bad install or update.