Can't start SAP Solution Manager 7.2 back-end (disp+work in ABAP and jstart in Java both stopped)

[former_member693955]

Hello experts,

During the last weeks, I've been configuring a Solution Manager 7.2 SP05 instance. It was all running smoothly until I had to install and configure Diagnostic Agent. After some failed attempts at setting it up through SWPM 1.0, I started receiving an error that said "error in writing extracted file: No space left on device" whenever I tried to run sapinst. I thought it should be no big deal, until I tried accessing my instance through SAP GUI 750 and found out I couldn't.

At first, for some reason, the front-end was being unable to solve the instance hostname. I solved this by editing the host file on my front-end machine and the hostname was, once again, able to resolve.

However, I'm now getting a "connection refused" warning. I went a bit further and decided to check my intances' state in MMC, just to find out that both my Java and my ABAP stack weren't working. Checking their processes list, I found out that:

1. In the ABAP stack, disp+work process is grey (showing status as "stopped");
2. In the Java stack, jstart process is grey (showing status as "stopped").

I did some research and found out that both problems may be related to the lack of space left on device. However, when looking at the log files dev_disp and dev_w0, I couldn't find any mention of lack of free space. Nevertheless, the "No space left on device" error keep appearing when I try running sapinst and I still can't connect to my instance.

Right now, I don't even know what to check to discover what is going on. Where should I look or what should I do to solve these issues?

You may find in the attachment my dev_disp and my dev_w0 files:

[AtulKumarJain]

Hi Pedro,

Is it worked for you.

Best Regards,

Atul

[AtulKumarJain]

It looks root dir is complete full.

you have to free some space in it.

also you can change installation dir where you have more space left to avoid issue on this.

Best Regards,

Atul

[former_member693955]

Hi Atul! Yes, the storage problem was solved, but my instance still isn't running. Apparently, HANA is not initializing. It seems to be a problem with nameserver, but I don't know exactly what it could be. If you are familiar with it, I can share some more details about it.
In any case, thanks for the help you provided so far! 🙂

[AtulKumarJain]

Hi Pedro,

Yes please share the error log and screenshot where you stuck.

I will happy to help here.

Best Regards,

[AtulKumarJain]

Hi Pedro,

Which operating system you are using ?

Could you please check all the dir at server where SAP application running on.

for exmple Linux you can use df -kh and figure out.

which dir is full.

Best Regards,

Atul

[former_member693955]

Hey Atul,

Thanks for your quick answer. My OS is a "SUSE Linux Enterprise Server 12 SP3" (provided by Amazon EC2).

I just ran the command you mentioned and the result was:

So I believe the source of the issue is xvda1, right?

[warren_angerstein3]

My guess is the /tmp is where sapinstdir is and is on /. That will fill up quickly and cause issues. You can create a new location for sapinstdir by using an env variable. SAPinst normally creates the installation directory sapinst_instdir directly below the temporary directory. SAPinst finds the temporary directory by checking the value of the environment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as default directory.