Skip to Content
0
Former Member
Apr 03, 2008 at 09:46 PM

SAP error on startup - ***ERROR: /tmp is too small (6072 MB required)

141 Views

I am having a problem starting my ABAP Stack (version 7.1 in ramp-up). I get the following error in the dev_disp trace

-


Es2ResGetFreeBlocks: Get 512 free blocks from resource in slot 0

Es2ResCreateFiles: Extend the memory of resource slot 0 to 384 MB

Es2ResCreateFiles: Using fileslot 1 of resource in slot 0 (128 MB)

Es2IResCreate: Create /SAP_ES2_00_001 (128 MB)

Es2ResCreateFiles: Extend the memory of resource slot 0 to 512 MB

Es2ResCreateFiles: Using fileslot 2 of resource in slot 0 (128 MB)

Es2IResCreate: Create /SAP_ES2_00_002 (128 MB)

  • ERROR => Es2IResCreate: ftruncate failed (size= 134217728. Check whether /tmp is mounted in sufficient size (2: No such

file or directory) [es2ux.c ; 205]

  • ERROR => Es2ResCreateFiles: Es2IResCreate failed [es2xx.c ; 1283]

  • ERROR => Es2ResGetFreeBlocks: Es2ResCreateFiles failed [es2xx.c ; 1822]

  • ERROR => Es2CtxCreate: Es2ResGetFreeBlocks failed [es2xx.c ; 2530]

  • ERROR => Eg2CtxCreate: Es2CtxCreate failed [eg2xx.c ; 807]

  • ERROR => DpEmInit: Eg2HeapCtxCreate (2) [dpxxdisp.c ; 10117]

  • ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c ; 9948]

  • DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

  • DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

  • DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

NiWait: sleep (10000ms) ...

NiISelect: timeout 10000ms

NiISelect: maximum fd=1

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Wed Apr 2 19:47:57 2008

NiISelect: TIMEOUT occured (10000ms)

dump system status

Workprocess Table (long) Wed Apr 2 23:47:57 2008

-


Our /tmp is set at 500 MB. To set it at 6GB is a lot on a Solaris box.

(below is from the sappfpar check pf=....)

***ERROR: /tmp is too small (6072 MB required, 496 MB configured)

***INFO: Temporary create ES2 resource /SAP_ES2_sappfpar_0 with 2047 MB

***ERROR: sizing of ES2 resource failed (No space left on device)

Shared memory disposition overview

--

It seems that SAP is ignoring the rest of the swap space and concentrating on the /tmp (we have 20GB of swap). Has anyone seen anything like this before? We are on a Unicode 7.1 kernel version 86.

If anyone has see this before I'd appreciate the help. Thanks!