How to resolve "No space left on device (28)" error on SunOS?
search cancel

How to resolve "No space left on device (28)" error on SunOS?

book

Article ID: 50665

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

Description:

Customer is getting the following errors when more than 1 web agent is running on one Solaris 10 machine

[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr: 
[26/Jan/2011:02:01:07] [Error] [CA WebAgent IPC] [19663] [CSmSharedSegment::smalloc] Error allocating shared memory segment using key 0x6353e581 - No space left on device (28)
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr: CSmSharedMallocator::CSmSharedMallocator - shared segment is NULL
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr: : No space left on device
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr:
[26/Jan/2011:02:01:07] [Warning] SiteMinder Agent
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr: Session cache failed to initialize.
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr: Unable to create shared memory segment. The segment may already exist, or this process requires appropriate permissions.
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr:
[26/Jan/2011:02:01:07] [Warning] SiteMinder Agent
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr: Session cache failed to initialize.
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr: LLAWP unable to create the authorization cache.
[26/Jan/2011:02:01:06] warning (19661): CORE3283: stderr:
[26/Jan/2011:02:01:07] [Info] [CA WebAgent IPC] [19663] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x6653e581

Environment

Web Agent R12.52 SP##
Applies to SunOS 10

Cause

The issue is due to shared memory.

You need to tune the following parameters on Solaris 10 machine

  • project.max-shm-ids
  • project.max-sem-ids

Resolution

Original values were:

 

->sudo prctl -n project.max-shm-ids -i project 1
project: 1: user.root
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-ids
privileged 400 - deny -
system 16.8M max deny

->sudo prctl -n project.max-sem-ids -i project 1
project: 1: user.root
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-sem-ids
privileged 800 - deny -
system 16.8M max deny

 

 

The shared memory and semaphores were tuned as follows:

prctl -n project.max-shm-ids -i -r -v 800 project 1


prctl -n project.max-sem-ids -i -r -v 1200 project 1

 

->sudo prctl -n project.max-shm-ids -i project 1
project: 1: user.root
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-ids
privileged 800 - deny -
system 16.8M max deny

->sudo prctl -n project.max-sem-ids -i project 1
project: 1: user.root
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-sem-ids
privileged 1200 - deny -
system 16.8M max deny

 

Additional Information

11/25/24 - David Macedo - formatted logs and commands properly, restructured KB per current guidelines