Skip to Content
0
Apr 07, 2010 at 10:00 AM

DAA instance not starting up

498 Views

Hi All,

We have installed Diag agent 7.11 on managed system ABC. and our solution manager is in EHP1 SP21 support pack. We have not installed sap host agent in managed system. But while starting Diag agent we r getting below error:

sapstart.log::

Starting Programs

-


(27325) New Child Process created.

(27325) Starting local Command:

Command: jc.sapDAA_SMDA95

pf=/usr/sap/DAA/SYS/profile/DAA_SMDA95_usahs141

(27325) Starting: local jc.sapDAA_SMDA95 pf=/usr/sap/DAA/SYS/profile/DAA_SMDA95_usahs141

(27280) Waiting for Child Processes to terminate.

(27280) **** 2010/04/07 03:18:17 Child 27325 terminated with Status 2 . ****

(27325) **** 2010/04/07 03:18:17 No RestartProgram command for program 0 ****

sapstart.log (88%)@41y0C41y0C(27280) **** No more Child Processes to wait for.

Parent Shutdown at 2010/04/07 03:18:17

(27280) Exiting with Return-Code 3. (No more child processes)

dev_jstart::

M [Thr 01] ***LOG Q0I=> NiIBindSocket: 130.175.141.143:65000: bind (227: Can't assign requested address) [nixxi.cpp 3585]

M [Thr 01] *** ERROR => NiIBindSocket: SiBind failed for hdl 1/sock 5

(SI_EADDR_NAVAIL/227; I4; DG; 130.175.141.143:65000) [nixxi.cpp 3585]

M [Thr 01] *** ERROR => NiIWakeupBind: NiIBind failed (rc=-16) [nixxi.cpp 9261]

M [Thr 01] *** ERROR => NiWakeupOpen: NiIWakeupBind failed (rc=-16) [nixxi.cpp 8895]

F [Thr 01] *** ERROR => SfEIO: SfCEventDispatcher::SfCEventDispatcher: NiWakeupOpen() failed (rc = -16 NIEMYHOST_VERIFY) [sfxxevt.hpp 1711]

F [Thr 01] *** ERROR => Operation failed: SfEIO: SfCEventDispatcher::SfCEventDispatcher: NiWakeupOpen() failed (rc = -16 NIEMYHOST_VERIFY)

[sfxxmain_mt. 1155]

F [Thr 01] *** LOG => exiting (exitcode -21001, retcode 2).

startsap SMDA95:

Starting Startup Agent sapstartsrv

-


Instance Service on host started

/usr/sap/DAA/SMDA95/exe/sapcontrol -prot NI_HTTP -nr 95 -function Start

07.04.2010 05:44:26

Start

FAIL: NIECONN_REFUSED (Connection timed out), NiRawConnect failed in plugin_fopen()

startup of Instance failed

we dont know why it is using ip 130.175.141.143:65000 with port 65000.

If anyone has any idea, please throw some point. Let us know if we are missing something.

Thanks,

Rohan