#ABAP_Trial - SAPINST_START_GUI Error - kernel os_create_region: can't allocate %d bytes"

[Former Member]

Hi all,

I am trying to install the SAP ABAP Trial version 7.51 on openSuSE. Running into this issue now that I seem to be stuck on:

"To solve that problem start the installation without using SAPINST_START_GUI option.."

This occurs if I try it in XTerm, or in a terminal by using Ctrl+Alt+F1 after logging off from my XWindows session. If I try adding the -g flag, it doesn't allow me to do the web instlal, simply returning that OpenSuSE is not a supported OS.

Please advise!

EDIT - So to update this, I had to run the installation with the -g flag and do it through the interface. Now, however, I'm getting a problem with it setting the sa password:

"kernel os_create_region: can't allocate 1909592064 bytes" seems to be stopping the installation. I've tried the following steps:

- mount -o remount,size=5G /dev/sh
- Verified that the timezone is set to UTC
- unset LANG
- export LANG=en_US.UTF-8
- sysctl -a | grep shmmax = 9223372036854775807
- sysctl -a | grep sem = 32000 1024000000 500 32000
- sysctl -a | grep shmall = 1152921504606846720
- sysctl -a | grep max_map_count = 1000000

Now, the only difference between my guide and Julie's guide is that I'm running this on VMWare instead of VirtualBox. Other than that, everything else is the same.

Any further ideas?

[Former Member]

Any ideas? More information that's needed?

[julieplummer20]

Hi Keith,

Really sorry about the delay; I have been ill.

I found the following in the Sybase Infocenter: http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00729.1500/html/errMessag...

1. Accroding to Sybase "...could be a HW error...". Can you please follow their instructions and let me know how you get on. (as appropriate for openSUSE).

2. If you run df -h , what value do you get?
Thanks Julie.

[Former Member]

Not a problem - been a nasty season for getting sick.

df -h results in this output:

vhcalnplci:~ # df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        351M     0  351M   0% /dev
tmpfs           5.0G  124K  5.0G   1% /dev/shm
tmpfs           358M  2.4M  356M   1% /run
tmpfs           358M     0  358M   0% /sys/fs/cgroup
/dev/sda2        98G   46G   51G  48% /
vmhgfs-fuse     2.8T  1.5T  1.3T  55% /mnt/hgfs
tmpfs            72M   20K   72M   1% /run/user/1000
/dev/sr0         56M   56M     0 100% /run/media/mainuser/VMware Tools
tmpfs            72M     0   72M   0% /run/user/0

As far as the sybase article... I took a brief look at it, and got this output when I ran ipcs -m:

vhcalnplci:npladm 54> ipcs -m
------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x00004dc4 327680     sapadm     760        40141728   1
0x00004dbe 360449     root       777        629458     1

vhcalnplci:npladm 55> ipcs -ma
------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages
------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x00004dc4 327680     sapadm     760        40141728   1
0x00004dbe 360449     root       777        629458     1
------ Semaphore Arrays --------
key        semid      owner      perms      nsems
0x0000752f 32768      sapadm     777        5

I'll take a further look at that configuring memory article tomorrow or later in the week.

[julieplummer20]

Great, let us know how you get on.

Julie

[former_member402443]

Hi Julie Plummer ,

I am trying to install the SAP ABAP Trial version 7.50 SP02 (download from

https://www.sap.com/developer/trials-downloads/additional-downloads/sap-netweaver-as-abap-developer-... on

openSUSE-Leap-42.3 Running into this issue now that I seem to be stuck on:

"To solve that problem start the installation without using SAPINST_START_GUI option.."

Attached the log file for your reference.141757-sapinstlog-error-log.txt

Please advise!

[alfredo_gomezripoll]

Hello Manoj

Did you solve the problem ? I have the same error .

Thanks

[lgdumlao]

In case anyone is still having the same issue - I found it to be caused by having too little RAM. Make sure to increase amount of available RAM if possible and disable ballooning if enabled (I was using this option in Proxmox)