# The system automatically restart **URL:** \ **Category:** SLED Configure-Administer\ **Created:** [August 6, 2013, 11:00am UTC](https://forums.suse.com/t/the-system-automatically-restart/24237 "2013-08-06T11:00:07Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![andyleigood](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@andyleigood](https://forums.suse.com/u/andyleigood)\ **Post date:** [August 6, 2013, 11:00am UTC](https://forums.suse.com/t/the-system-automatically-restart/24237/1 "2013-08-06T11:00:07Z")
1 I use Suse 10 SP4 system using servers are HP ProLiant BL680c G7. 2 yesterday at 11:40 minutes after the server automatically restart. 3 I want to know why will automatically restart, and how to solve. Given the following information: Kernel Taint Status [Red] \*Kernel Tainted: 192\> 0 \<7\> aer\_init: AER / PCI-Express error reporting disabled Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: engine\_open\_object: Open of / dev/evms/.nodes/ram0 failed with error code 22: Invalid argument Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: engine\_open\_object: Open of / dev/evms/.nodes/ram1 failed with error code 22: Invalid argument Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: engine\_open\_object: Open of / dev/evms/.nodes/ram10 failed with error code 22: Invalid argument Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: engine\_open\_object: Open of / dev/evms/.nodes/ram11 failed with error code 22: Invalid argument Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: engine\_open\_object: Open of / dev/evms/.nodes/ram12 failed with error code 22: Invalid argument Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: engine\_open\_object: Open of / dev/evms/.nodes/ram13 failed with error code 22: Invalid argument Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: engine\_open\_object: Open of / dev/evms/.nodes/ram14 failed with error code 22: Invalid argument Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: evms\_create\_task: Error initializing options. Aug 05 12:01:57 pdccsfudssvr066 _3_ Engine: evms\_create\_task: Error initializing options. Aug 05 12:01:57 pdccsfudssvr066 _2_ Engine: isa\_valid\_task: Command 10 cannot be targeted at a plug-in. Capabilities: [100] Advanced Error Reporting UESta: DLP-SDES-TLP-FCP-CmpltTO-CmpltAbrt-UnxCmplt-RxOF-MalfTLP-ECRC-UnsupReq-ACSViol- UEMsk: DLP-SDES-TLP-FCP-CmpltTO-CmpltAbrt-UnxCmplt-RxOF-MalfTLP-ECRC-UnsupReq + ACSViol- UESvrt: DLP + SDES + TLP + FCP + CmpltTO + CmpltAbrt + UnxCmplt + RxOF + MalfTLP + ECRC-UnsupReq + ACSViol- CESta: RxErr-BadTLP-BadDLLP-Rollover-Timeout-NonFatalErr- CEMsk: RxErr-BadTLP-BadDLLP-Rollover-Timeout-NonFatalErr- AERCap: First Error Pointer: 00, GenCap-CGenEn-ChkCap-ChkEn- Capabilities: [150] Access Control Services Aug 5 12:01:57 pdccsfudssvr066 kernel: device-mapper: ioctl: error adding target to table (WW) warning, (EE) error, (NI) not implemented, (??) Unknown (Gnome-panel: 9620): GdkPixbuf-CRITICAL \*\*: gdk\_pixbuf\_scale\_simple: assertion `dest\_width\> 0 'failed (Gnome-panel: 9620): GdkPixbuf-CRITICAL \*\*: gdk\_pixbuf\_scale\_simple: assertion `dest\_width\> 0 'failed Initializing nautilus-open-terminal extension Initializing nautilus-share extension Window manager warning: Fatal IO error 104 (Connection reset by peer) on display ‘: 0.0’. gnome-panel: Fatal IO error 104 (Connection reset by peer) on X server: 0.0. nautilus: Fatal IO error 104 (Connection reset by peer) on X server: 0.0. SoftwareUpdater: Fatal IO error 104 (Connection reset by peer) on X server: 0.0. application-browser: Fatal IO error 104 (Connection reset by peer) on X server: 0.0.