Start Diagnostic Agent on satellite systems fails with errors

[Former Member]

Hello,

after installation diagnostic agent on satellite system (linux) didn't start, so I tried manually.

But agent doesn't come up although startup script tells everything is fine.

"sapcontrol -prot NI_HTTP -nr 98 -function GetProcessList" gives status "grey, stopped".

Note 1316652 didn't help, file dev_boostrap is not available on linux.

How can I solve problem?

Logfiles from /usr/sap/DAA/SMDA98/work/:

dev_flightrec:

F

F Fri Mar  7 10:38:49 2014

F  ********************************************************************************

F  Java environment properties

F    root directory    : /usr/sap/DAA/SMDA98/exe/sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_45

F    cpu               : ppc64

F    java vm type      : server

F    java vm version   : 6.1.051 23.5-b02

F    jvm library name  : libjvm.so

F    library path      : /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/ppc64/server:/usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/ppc64

F    executable path   : /usr/sap/DAA/SMDA98/exe/sapjvm_6/bin

F    SAP extensions    : available

F  ********************************************************************************

F  [Thr 17590328044688] *** ERROR => SfEIO: SfChDir: chdir(/usr/sap/DAA/SMDA98/j2ee) failed (errno = 2 No such file or directory)  [sfxxlib.hpp  201]

F  [Thr 17590328044688] *** ERROR => Operation failed: SfEIO: SfChDir: chdir(/usr/sap/DAA/SMDA98/j2ee) failed (errno = 2 No such file or directory)

[sfxxmain_mt. 1173]

F

F  ********************************************************************************

F  *** ERROR => Mutex initialization failed.

F  ***

F  *** Please see section 'Java process initialization issues'

F  *** in SAP Note 1316652 for additional information and trouble shooting advice.

F  ********************************************************************************

F

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

dev_smdagent:

F  ********************************************************************************

J

J  The stack size specified is too small, Specify at least 1280k

F  [Thr 17590205608336] *** ERROR => SfEStartupError: SfCSapVm::createJavaVM: Cannot create Java VM instance from library 'libjvm.so' (rc = -1).  [sfxxjvm.hpp  1166]

F  [Thr 17590205608336] *** ERROR => Java thread failed: SfEStartupError: Cannot create Java VM instance from library 'libjvm.so' (rc = -1).

[sfxxjvm.hpp  1468]

F

F  ********************************************************************************

F  *** ERROR => Cannot connect to parent process.

F  ***

F  *** Please see section 'Java VM shared library issues'

F  *** in SAP Note 1316652 for additional information and trouble shooting advice.

F  ********************************************************************************

F

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

M  [Thr 17590270373008] CCMS: alert/disable_j2ee_monitoring set. CCMS Monitoring of J2EE Engine switched off.

Regards,

Julia

[juan_dearellano · Accepted solution]

Which agent release?  Take into consideration that Diagnostic Agent 7.2 and lower releases are not supported.

I recommend you to:

• uninstall the agent
• clear de installation directory
• download 7.4 agent release
• install it with root user

Also, before uninstall it, please check the existence of the following files:

• /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/ppc64/server
• /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/ppc64

Sometimes the OS users start the agent with wrong user (daaadm) and some files becomes with wrong authorizations, if yes:

• chown -R daaadm:sapsys /usr/sap/DAA
• chmod -R 775 /usr/sap/DAA

Are you sure about ppc64 architecture from your server? you can check it with

• uname -a

If your problem is not solved, please post the output of this command:

• ls -l /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib

Don't hesitate to ask me if you need anything else I can do for you.

Yours faithfully

Juan de la Cruz Arellano Royo

[Former Member · Accepted solution]

Hello Juan,

ok, I uninstalled and reinstalled Diagnostic Agent.

After deinstallation I removed folder /usr/sap/DAA.

Installation I did again with binaries from service.sap.com/sltoolset - SWPM10SP04 and Kernel "Krnl_7.20_LNX_x86_64_PPC_64bit_SP04_".

Same error.

Agentrelease is as dev_smdagent says:

Agentrelease dev_smdagent

---------------------------------------------------

trc file: "dev_smdagent", trc level: 1, release: "720"

---------------------------------------------------

sysno      98

sid        DAA

systemid  391 (IBM pSeries with Linux)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make      multithreaded, Unicode, 64 bit, optimized

profile    /usr/sap/DAA/SYS/profile/DAA_SMDA98_soloc01

pid        3800

After installation I found directory /usr/sap/DAA/SMDA98/exe/sapjvm_6/, but no directory /usr/sap/DAA/SMDA98/exe/sapjvm_6/server. Directory /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/ppc64  is available.

uname -a gives:

Linux hostname 3.0.42-0.7-ppc64 #1 SMP Tue Oct 9 11:58:45 UTC 2012 (a8dc443) ppc64 ppc64 ppc64 GNU/Linux

Which logfiles do you need?

I attached dev_flighrec, dev_smdagent and content of directory /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib.

Regards,

Julia

dev_flightrec.txt.zip

dev_smdagent.txt.zip

lib.txt.zip

[juan_dearellano · Accepted solution]

Can you attach the installation logs?

also please attach the following:

• /usr/sap/DAA/SMDA98/SMDAgent/log
• /usr/sap/DAP/SMDA98/work
• /usr/sap/DAP/SYS/profile

Please, post the output with daaadm of following command:

• find /usr/sap/DAA/SMDA98/exe/sapjvm_6 -name libjvm.so

Kind regards!

[Former Member · Accepted solution]

Hello Juan,

whichs logs from work and profile you want? It's too much to add it all.

I attached sapinst.log and sapinst_dev.log

hostname:~ # find /usr/sap/DAA/SMDA98/exe/sapjvm_6 -name libjvm.so

/usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/ppc64/server/libjvm.so

Regards,

Julia

sapinst_dev.txt.zip

sapinst.txt.zip

[juan_dearellano · Accepted solution]

Dear Julia,

According to the error displayed in dev_smdagent file, I think the issue comes from the limits of the daaadm user which do not follow the recommentations described here:

ulimit

• Logon with the agent OS user ‘su – daaadm’
• Open an sh shell with the command ‘sh’
• Execute the command ‘ulimit -a’
• Compare the values with the following recommended values
• In case limits have been adjusted, remember to stop the Diagnostics Agent (sapstop), kill the Diagnostics Agent processes (sapstartsrv) and start again the Agent (sapstart)
  This way the Diagnostics Agent will take into account the new settings.

Current recommendations for the limit parameters must be taken from the setup guide for the most recent installer. For the SAP Note and the setup guide for the most recent installer please refer toSAP Note 1833501.

If the user’s limit parameters for the OS Diagnostics Agent user are not correct, high CPU consumption situations or OutOfMemory errors in the Diagnostics Agents logs can be experienced.

umask

Please refer to SAP note 1163751.

May you please apply this recommendations and restart the agent (do not forget to restart sapstartsrv process as well). With daaadm user:

• stopsap
• sapcontrol -nr 98 -function StopService
• cleanipc 98 remove
• startsap

If everything is OK, please upgrade your SAP JVM if possible following #1449879 - SAP JVM Patch Collection 38 (build 5.1.052).

If the problem persist, attach the std_smdagent.out file from work directory   

Don't hesitate to ask me if you need anything else I can do for you.

Yours faithfully

Juan de la Cruz Arellano Royo

[Reagan · Accepted solution]

The errors in the dev_flightrec is not the reason for the SMD not starting.

Check the logs jvm_smdagent.out, jstart.jvm and dev_jstart

Regards

RB

[juan_dearellano · Accepted solution]

As an overview of the solution:

1. Stop the Agent (with daaadm user at OS level)
   • stopsap
   • sapcontrol -nr 98 -function StopService
   • cleanipc 98 remove
2. Modify the daaadm user limits. You can check it with
   1. /etc/security/limits.conf
   2. ulimit or limit command depends on OS
3. Check the umask as per note 1163751

If it's not work, please upgrade your SAP JVM if possible following #1449879 - SAP JVM Patch Collection 38 (build 5.1.052).

try again restarting the agent with point 1.

If it doesn't work, attach the std_smdagent.out file from work directory  

Please, do not take in consideration the output of dev_flightrec file log. I think you will solve the problem if you follow my recommendations

Don't hesitate to ask me if you need anything else I can do for you.

Yours faithfully

Juan de la Cruz Arellano Royo

[juan_dearellano · Accepted solution]

Dear Julia,

Did you follow my recommendations?

Did you resolve your issue?

Please, like and report the post that help you in order to other users with same problem can learn about it.

Kind regards

Juan de la Cruz Arellano Royo

[Former Member · Accepted solution]

Hello Juan,

I stopped agent, sapstartservice and cleaned ipc.

I compared ulimit parameters with documument "SWPM10SP4_Diag_Agent_Setup_Guide.pdf" attached in note 1858920. Page 13 contains a few recommendations, but I coudn't find all of them on my server.

Parameter - recommendation - my server

cputime - unlimited - unlimited

filesize - unlimited - unlimited

datasize - unlimited - ??? data seg size - unlimited

stacksize - 8192kb - 8192kb

coredumpsize - unlimited - ??? corefilesize - 0

descriptors - 8192 - ???

memorysize - unlimited - ??? maxmemorysize - unlimited

For datasize, coredumpsize and memorysize I couldn't find the entries on my server.

I think this should be ok?!

hostname:~> ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 11047

max locked memory       (kbytes, -l) 64

max memory size         (kbytes, -m) unlimited

open files                      (-n) 32800

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 8192

cpu time               (seconds, -t) unlimited

max user processes              (-u) 11047

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

"umask" as daaaadm gives "0022".

I edited /home/daaadm/.bashrc and inserted line "umask 027".

After that I restarted agent again.

Agent doesn't come up.

/usr/sap/DAA/SMDA98/work/std_smdagent.out

--------------------------------------------------------------------------------

stdout/stderr redirection

--------------------------------------------------------------------------------

node name   : SMDAgent

host name   : hostname

system name : DAA

system nr.  : 98

started at  : Tue Mar 11 14:58:05 2014

The stack size specified is too small, Specify at least 1280k

What does this mean "stack size specified is too small"? Where can I change this??

Regards

Julia

[juan_dearellano · Accepted solution]

Dear Julia,

You must to change the limit size for daaadm in the user profile:

• su - daaadm
• bash -c "ulimit -s unlimited"

Depends on the Linux release you will found the configuration file in some of following files:

• /etc/security/limits.conf
• /etc/security/limits.d

For details please read the manpage by running "man limits.conf" on your system

This is my diagnostic agent limit settings:

12CODESOLMAN:daaadm 11> bash -c "ulimit -a"

Limit	Measure	Modificator	Size
core file size	blocks	-c	0
data seg size	kbytes	-d	unlimited
scheduling priority		-e	0
file size	blocks	-f	unlimited
pending signals		-i	204800
max locked memory	kbytes	-l	32
max memory size	kbytes	-m	unlimited
open files		-n	32800
pipe size	512 bytes	-p	8
POSIX message queues	bytes	-q	819200
real-time priority		-r	0
stack size	kbytes	-s	10240
cpu time	seconds	-t	unlimited
max user processes		-u	204800
virtual memory	kbytes	-v	unlimited
file locks		-x	unlimited

If you want to change any of the limits, you can do it with following command:

• bash -c "ulimit <modificator> <value>"

Please, take into consideration to add the user to limit files or modify the daaadm user's profile in order to avoid failling agent starts due missing limit configuration (session values).

Modifications to the limit files require a logout for the setting to take effect for newly started programs. With daaadm user:

• stopsap
• sapcontrol -nr 98 -function StopService
• cleanipc 98 remove
• exit
• su - daaadm
• bash -c "ulimit -s" or  bash -c "ulimit -a"
• check the value/s. If all limits is OK, you can start the agent
  • startsap

Kind regards

Juan de la Cruz Arellano Royo

[Former Member · Accepted solution]

Hello Juan,

thank you very much for your help, but unfortunately it still doesn't work.

I stopped agent, stopped sapcontrol Service, cleaned ipc.

I added following entry in /etc/security/limits.conf:

daaadm

soft

stack

10240

I did command "bash -c "ulimit -s"" as user daaadm with result 10240.

But still error message after restarting DAA Agent is the same - stack size is too small.

Do I have to restart system or add it as "hard" in limits.conf? It's a SLES 11 PL 2.

Any other ideas?

Regards,

Julia

[juan_dearellano · Accepted solution]

Hi Julia,

Sure!

Please do the following and try to identify the problem:

With daaadm user:

• stopsap
• sapcontrol -nr 98 -function StopService
• cleanipc 98 remove
• bash -c "ulimit -s unlimited"
• bash -c "ulimit -m unlimited"
• bash -c "ulimit -d unlimited"
• startsap

And let us know if the problem persist

Kind regards

[juan_dearellano]

Did your problem resolved?

Thank you very much for your collaboration

[Former Member]

Hi

For very initial error "The stack size specified is too small, Specify at least 1280k" please try the below step..

1680045 - Release Note for Software Provisioning Manager 1.0

------------------------< D022256, 20/AUG/13 >-------------------------

LinuxPPC only: Installation aborts with the error "stack size specified is too small, Specify at least 1280k"

When installation aborts with the error "stack size specified is too small, Specify at least 1280k", set the following parameter in /sapmnt/<SID>/profile/DEFAULT.PFL: "jstartup/native_stack_size=2097152". Afterwards, stop and restart the tool and then continue with the installation.

Regards

Raj

[juan_dearellano]

Did you resolve the problem ???

Kind regards!

[Former Member]

Hello Juan,

As root I edited /etc/security/limits.conf to:

daaadm	soft	stack	unlimited
daaadm	soft	memory	unlimited
daaadm	soft	data	unlimited

As daaadm " bash -c "ulimit -s/d/m"" gives back unlimited.

Still the same error: "The stack size specified is too small, Specify at least 1280k".

Is there another stacksize that can be edited?

Regards,

Julia

[juan_dearellano]

Dear Julia,

Please, logon with daaadm user and paste here the output of this command:

• bash -c "ulimit -a"
• cat /etc/*-release
• env

Please, attach the DAA_SMDA98_<HOSTNAME> profile located in /usr/sap/DAA/SYS/profile

Also please, do the following:

• cd /usr/sap/DAA/SMDA98/script/
• stopsap
• sapcontrol -nr 98 -function StopService
• cleanipc 98 remove
• Update in Solution Manager SLD the CIM
  
• Update in Solution Manager SLD the CR Content
• ./smdsetup.sh managingconf hostname:"sapms://yourSolManHost.FQDN" port:"your_port" user:"SMD_ADMIN" pwd:"your_password"
• startsap

Kind regards

[Former Member]

Hello Juan,

bash -c "ulimit -a"

hostname:daaadm 52> bash -c "ulimit -a"

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 11047

max locked memory       (kbytes, -l) 64

max memory size         (kbytes, -m) unlimited

open files                      (-n) 32800

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) unlimited

cpu time               (seconds, -t) unlimited

max user processes              (-u) 11047

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

hostname:daaadm 53> cat /etc/SuSE-release

SUSE Linux Enterprise Server 11 (ppc64)

VERSION = 11

PATCHLEVEL = 2

env

hostname:daaadm 55> env

TERM=xterm

HOME=/home/daaadm

SHELL=/bin/csh

USER=daaadm

LOGNAME=daaadm

PATH=/home/daaadm/bin:/usr/local/bin:/bin:/usr/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/opt/gnome/bin:/usr/sap/DAA/SYS/exe/uc/linuxppc64:/usr/sap/DAA/SYS/exe/run:/home/daaadm:.

HOSTTYPE=ppc64

VENDOR=suse

OSTYPE=linux

MACHTYPE=ppc64-suse-linux

SHLVL=1

PWD=/home/daaadm

GROUP=sapsys

HOST=hostname

CSHEDIT=emacs

MAIL=/var/spool/mail/daaadm

CPU=ppc64

HOSTNAME=hostname.xx.xx.xx

INPUTRC=/etc/inputrc

LESS=-M -I

LESSOPEN=lessopen.sh %s

LESSCLOSE=lessclose.sh %s %s

LESS_ADVANCED_PREPROCESSOR=no

LESSKEY=/etc/lesskey.bin

PAGER=less

MORE=-sl

MINICOM=-c on

MANPATH=/usr/local/man:/usr/share/man:/opt/gnome/share/man

INFODIR=/usr/local/info:/usr/share/info:/usr/info

INFOPATH=/usr/local/info:/usr/share/info:/usr/info:/opt/gnome/share/info

XKEYSYMDB=/usr/share/X11/XKeysymDB

XNLSPATH=/usr/share/X11/nls

COLORTERM=1

XCURSOR_THEME=Industrial

QT_HOME_DIR=/usr/share/desktop-data

LANG=en_US.UTF-8

ACLOCAL_FLAGS=-I /opt/gnome/share/aclocal

PKG_CONFIG_PATH=/opt/gnome/lib64/pkgconfig:/opt/gnome/share/pkgconfig

GNOME2_PATH=/usr/local:/opt/gnome:/usr

FROM_HEADER=

NNTPSERVER=news

WINDOWMANAGER=/usr/bin/gnome

PYTHONSTARTUP=/etc/pythonstart

XDG_DATA_DIRS=/usr/local/share:/usr/share:/etc/opt/kde3/share:/opt/gnome/share:/opt/kde3/share:/usr/share/gnome/help

XDG_CONFIG_DIRS=/etc/xdg

G_BROKEN_FILENAMES=1

G_FILENAME_ENCODING=@locale,UTF-8,ISO-8859-1,CP1252

ENV=/etc/bash.bashrc

CSHRCREAD=true

LS_COLORS=no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=41;33;01:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tbz=00;31:*.tgz=00;31:*.rpm=00;31:*.deb=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lzma=00;31:*.zip=00;31:*.zoo=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.tb2=00;31:*.tz2=00;31:*.tbz2=00;31:*.avi=01;35:*.bmp=01;35:*.fli=01;35:*.gif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mng=01;35:*.mov=01;35:*.mpg=01;35:*.pcx=01;35:*.pbm=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.tga=01;35:*.tif=01;35:*.xbm=01;35:*.xpm=01;35:*.dl=01;35:*.gl=01;35:*.wmv=01;35:*.aiff=00;32:*.au=00;32:*.mid=00;32:*.mp3=00;32:*.ogg=00;32:*.voc=00;32:*.wav=00;32:

LS_OPTIONS=-N --color=tty -T 0

SAPSYSTEMNAME=DAA

DIR_LIBRARY=/usr/sap/DAA/SYS/exe/run

RSEC_SSFS_DATAPATH=/usr/sap/DAA/SYS/global/security/rsecssfs/data

RSEC_SSFS_KEYPATH=/usr/sap/DAA/SYS/global/security/rsecssfs/key

rsdb_ssfs_connect=0

LD_LIBRARY_PATH=/usr/sap/DAA/SYS/exe/run:/usr/sap/DAA/SYS/exe/uc/linuxppc64

DAA_SMDA98_<HOSTNAME>

SAPSYSTEMNAME = DAA

SAPSYSTEM = 98

INSTANCE_NAME = SMDA98

DIR_CT_RUN = $(DIR_EXE_ROOT)$(DIR_SEP)$(OS_UNICODE)$(DIR_SEP)linuxppc64

DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

DIR_PROFILE = $(DIR_INSTALL)/profile

_PF = $(DIR_PROFILE)/DAA_SMDA98_hostname

SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)

SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)

SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)

SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)

SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)

#-----------------------------------------------------------------------

# Copy SAP Executables

#-----------------------------------------------------------------------

_CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst

Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)

_CPARG1 = list:$(DIR_CT_SAPJVM)/sapjvm_6.lst

_CPARG2 = source:$(DIR_CT_SAPJVM)

Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1) $(_CPARG2)

#-----------------------------------------------------------------------

# JStart configuration

#-----------------------------------------------------------------------

SAPJVM_VERSION = 6.1.051

DIR_SAPJVM = $(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6

jstartup/vm/home = $(DIR_SAPJVM)

jstartup/bootstrap = no

alert/disable_j2ee_monitoring = 1

jstart/checkVersion = false

#-----------------------------------------------------------------------

# Start SMD Agent

#-----------------------------------------------------------------------

_JC = jc.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)

Execute_02 = local rm -f $(_JC)

Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/jstart$(FT_EXE) $(_JC)

Start_Program_00 = local $(_JC) pf=$(_PF)

SAPGLOBALHOST = hostname

smd/agent/type = 710

jstartup/instance_properties = $(DIR_INSTANCE)/SMDAgent/smdagent.properties

Autostart = 1

SLD and CR Content are up to date in solution manager.

Regards,

Julia

[juan_dearellano]

Dear Julia,

I recommend you to implement carefully the following notes:

• 1275776 - Linux: Preparing SLES for SAP environments
• 1310037 - SUSE LINUX Enterprise Server 11: Installation notes

I think the problem is caused due the virtual machine can't allocate in the OS. The previous notes talk about some patches and parameters at OS level like

• kernel.shmmax
• kernel.shmall
• TMPFS

In order to do a deep analysis of your problem while you are reading those notes, could you kinkdly attach here the output of the following command:

• bash
• bash -c "ulimit -i 172032"
• bash -c "ulimit -s unlimited"
• bash -c "ulimit -d unlimited"
• bash -c "ulimit -m unlimited"
• strace -o output.txt startsap

Also attach the files:

• output.txt
• std_smdagent.out
• jvm_smdagent.out
• jstart.jvm
• dev_jstart

Kind regards!

Juan de la Cruz Arellano Royo

[RolandKramer]

Hi,

Check the Start Section in the following Document

SAP First Guidance - Business Warehouse on SAP HANA Installation

Best Regards Roland

[Former Member]

Hello Roland,

I couldn't find anything helpful.

Just:

SLES 11 SP2: With SLES 11 SP2 no further uuidd activation is needed. The sapconf is not needed

for uuidd purposes, but still recommended for something different (refer note 1310037).

Other things seem to be HANA specific. It's not a HANA system.

Regards

Julia

[Former Member]

Can you attach full log files (preferably as attachments).

[Former Member]

as per the log, see below issue, there is no directory called /usr/sap/DAA/SMDA98/j2ee

ERROR => SfEIO: SfChDir: chdir(/usr/sap/DAA/SMDA98/j2ee) failed (errno = 2 No such file or directory

[Former Member]

Hello Sunil,

thats right, but on other systems with running SMDA98 agent ther is noch directory /usr/sap/DAA/SMD98/j2ee too...

I think the problem is in stack size, but I don't know what and how to increase.

Regards,

Julia

[Former Member]

is this same as discussed under

[bala2104]

Please uninstall and install it again and see...

[Former Member]

Hello Sunil,

I read this thread before my posting - it's no user/password problem and there is another returncode than 11112 in my logs.

Any other ideas?

Regards,

Julia