SAP PRD Instance stopped (yellow color)

[Former Member]

Hello all,

Our Sap System stopped yesterday (08.09.09) between 15:00 and 15:30 hours. (The SAP instance changed from green color to yellow color in OS system)

The log of this time in the SM21 are:

15:26:34 DP Q0 4 Connection to user 5587 ( ), terminal 71 (Unisordk53a ) lost

15:27:09 DP Q0 I Operating system call recv failed (error no. 10054)

15:27:09 DP Q0 4 Connection to user 5584 ( ), terminal 77 (unisordk82 ) lost

15:27:09 DP Q0 I Operating system call recv failed (error no. 10054)

15:27:09 DP Q0 4 Connection to user 5588 ( ), terminal 40 (unisordk82 ) lost

15:28:35 RD Q0 I Operating system call recv failed (error no. 10054)

15:28:51 UP2 017 Q0 2 Stop Workproc17, PID 5148

15:28:51 UP1 011 Q0 2 Stop Workproc11, PID 5812

15:28:52 ENQ 012 Q0 2 Stop Workproc12, PID 5400

15:29:52 BTC 015 500 INTERFACE Q0 2 Stop Workproc15, PID 5484

15:29:52 DIA 002 500 PRICORREA FBL5 Q0 2 Stop Workproc 2, PID 5432

15:29:52 DIA 004 Q0 2 Stop Workproc 4, PID 7888

15:29:52 DIA 005 500 JSANTOS STAR Q0 2 Stop Workproc 5, PID 5124

15:29:52 BTC 013 500 INTERFACE Q0 2 Stop Workproc13, PID 5084

15:29:53 DIA 001 500 IMELLO J1B3 Q0 2 Stop Workproc 1, PID 5088

15:29:53 BTC 014 500 INTERFACE Q0 2 Stop Workproc14, PID 5640

15:29:53 DIA 003 500 FATURASOR ZSD0 Q0 2 Stop Workproc 3, PID 3580

15:29:53 DIA 007 500 BASIS STAR Q0 2 Stop Workproc 7, PID 5300

15:29:53 SPO 016 000 SAPSYS Q0 2 Stop Workproc16, PID 632

15:29:53 DIA 008 500 SNUNES SESS Q0 2 Stop Workproc 8, PID 5236

15:29:53 DIA 009 500 SNUNES SESS Q0 2 Stop Workproc 9, PID 3924

15:29:53 RD S3 0 SAP gateway was closed

15:30:54 DP Q0 M Message server disconnected

15:30:54 DP Q0 5 Stop SAP System, Dispatcher Pid 29

15:30:57 MS Q0 2 Stop Msg Server, PID 1864

15:32:01 DP E1 0 Buffer SCSA Generated with Length 4096

15:32:01 DP Q0 0 Start SAP System, SAPSYSTEM 02, Dispatcher Pid 6448

15:32:15 DP GZ Z > 1 possible network problems detected - check tracefile and adjus

15:32:15 DP Q0 K Connection to message server (on unisp05) established

15:32:15 WRK 000 Q0 Q Start Workproc 2, Pid 3824

15:32:15 RD S0 0 SAP Gateway Started (PID: 1840)

15:32:15 WRK 000 Q0 Q Start Workproc 0, Pid 6268

15:32:15 WRK 000 Q0 Q Start Workproc 5, Pid 3584

15:32:16 WRK 000 Q0 Q Start Workproc 7, Pid 5432

15:32:16 WRK 000 Q0 Q Start Workproc 1, Pid 6872

15:32:16 WRK 000 Q0 Q Start Workproc 3, Pid 7768

15:32:16 DP Q1 C MsgServer Hardware ID Was Determined

15:32:16 WRK 000 Q0 Q Start Workproc15, Pid 6580

15:32:16 WRK 000 Q0 Q Start Workproc10, Pid 5300

15:32:16 WRK 000 Q0 Q Start Workproc 6, Pid 7888

15:32:16 WRK 000 Q0 Q Start Workproc12, Pid 7228

15:32:16 WRK 000 Q0 Q Start Workproc 4, Pid 7692

15:32:16 WRK 000 Q0 Q Start Workproc13, Pid 6228

15:32:16 WRK 000 Q0 Q Start Workproc 8, Pid 3580

15:32:16 WRK 000 Q0 Q Start Workproc16, Pid 5744

15:32:16 WRK 000 Q0 Q Start Workproc14, Pid 6860

15:32:16 WRK 000 Q0 Q Start Workproc11, Pid 1688

15:32:16 WRK 000 Q0 Q Start Workproc 9, Pid 5484

15:32:16 WRK 000 Q0 Q Start Workproc17, Pid 8152

Anybody know what should be the problem and besides where should i search for the problem?

Best Regards,

Fábio Karnik Tchobnian

Edited by: Fio Tchobnian on Sep 9, 2009 5:22 PM

[former_member185031]

Only log file can tell you exactly what happened. Please check the log files under work directory starting with

dev_w*

dev_disp

and dev_w*.old

dev_disp.old

Regards,

Subhash

[Former Member]

The dev_disp log near the error is :

Tue Sep 08 15:27:09 2009

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer)

• ERROR => NiIRead: SiRecv failed for hdl 58 / sock 732

(SI_ECONN_BROKEN/10054; I4; ST; 192.168.1.114:1508)

Network error of client T77, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Client address of T77 is 192.168.1.114(unisordk82.unimetalcoque.intra)

***LOG Q04=> DpRTmPrep, NiBufReceive (5584 77 unisordk82 )

RM-T77, U5584, , unisordk82, 15:21:46, M0, W-1, , 1/0

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer)

• ERROR => NiIRead: SiRecv failed for hdl 14 / sock 1272

(SI_ECONN_BROKEN/10054; I4; ST; 192.168.1.114:1519)

Network error of client T40, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Client address of T40 is 192.168.1.114(unisordk82.unimetalcoque.intra)

***LOG Q04=> DpRTmPrep, NiBufReceive (5588 40 unisordk82 )

RM-T40, U5588, , unisordk82, 15:23:38, M0, W-1, , 1/0

Tue Sep 08 15:27:18 2009

DpEnvCheck: set dp_high_prio_state to DP_HPRIO_TIMEOUT (1 rqs)

Tue Sep 08 15:27:58 2009

DpEnvCheck: set dp_high_prio_state to DP_HPRIO_TIMEOUT (1 rqs)

Tue Sep 08 15:28:38 2009

DpEnvCheck: set dp_high_prio_state to DP_HPRIO_TIMEOUT (1 rqs)

Tue Sep 08 15:28:50 2009

DpSigInt: caught signal 2

DpHalt: shutdown server >unisp05_PRD_02 < (normal)

DpModState: change server state from ACTIVE to SHUTDOWN

Stop work processes

Any idea of what is the problem?

Best Regards,

Fábio Karnik Tchobnian

[anindya_bose]

Was there a server automatic reboot?

Check from Windows Event Viewer.

My Computer>right Click>Manage>System Tools>Event Viewer

[Former Member]

The problem appear in 31.08.2009

There was a reboot in 31.08.2009 an the problem was solved.

The problem come back in 08.09.2009

There was a reboot in 08.08.2009 an the problem was solved.

[Former Member]

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) http://nixxi.cpp 4361
*** ERROR => NiIRead: SiRecv failed for hdl 14 / sock 1272
(SI_ECONN_BROKEN/10054; I4; ST; 192.168.1.114:1519) http://nixxi.cpp 4361
Network error of client T40, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Looks like you have some network problem. Check windows event log too for more information.

[Former Member]

Hello

How can i check my network?

I found the note 155147 to check but the niping did not work or maybe i am not doing correctly.

Do you know another way ?

Best Regards,

Fábio Karnik Tchobnian

[markus_doehr2]

> How can i check my network?

Contact your network guy

Make sure the switches/hubs the server is connected to are working as expected, check their logfiles.

Markus

[Former Member]

Dear All,

We applied the note 155147 and the problem was in our network( The niping comand detected the problem).

Thanks

Best Regards,

Fábio Karnik Tchobnian