Error: "No space left on device" prevents SSO and EM services from starting
search cancel

Error: "No space left on device" prevents SSO and EM services from starting

book

Article ID: 433466

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

After upgrading to DX NetOps Portal version 25․4․5, the SSO and EM services fail to start due to insufficient disk space in the temporary directory․​​​​‌​‍

ERROR MESSAGE: Seen in the services wrapper-<DATE>.log file.

STATUS | wrapper  | 2026/03/16 21:14:25 | Launching a JVM...
INFO   | wrapper  | 2026/03/16 21:14:25 | Java Command Line:
INFO   | wrapper  | 2026/03/16 21:14:25 |   Command: $PORTAL_HOME/jre/bin/java -Djetty.home=$PORTAL_HOME/PerformanceCenter/jetty -Djetty.base=$PORTAL_HOME/PerformanceCenter/sso -Djetty.http.port=8381 -XX:MaxMetaspaceSize=128m -Dorg.apache.jasper.compiler.disablejsr199=true -Dorg.eclipse.jetty.annotations.maxWait=300 -Djetty.logging.filename=$PORTAL_HOME/PerformanceCenter/sso/logs/SSOService.log -Djdk.tls.rejectClientInitiatedRenegotiation=true -Djdk.tls.ephemeralDHKeySize=matched -Dprocess.name=SSO -Djava.io.tmpdir=/tmp -Dwrapper.lang.domain=wrapper -Dwrapper.lang.folder=../lang -Xms64m -Xmx1024m -Dwrapper.disable_console_input=TRUE -Dwrapper.pid=2357964 -Dwrapper.version=3.6.3-st -Dwrapper.native_library=wrapper -Dwrapper.arch=x86 -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 -Djava.library.path=../lib -classpath ../lib/wrapper.jar:$PORTAL_HOME/PerformanceCenter/jetty/start.jar org.tanukisoftware.wrapper.WrapperSimpleApp org.eclipse.jetty.start.Main -XX:-HeapDumpOnOutOfMemoryError
INFO   | jvm 1    | 2026/03/16 21:14:25 | OpenJDK 64-Bit Server VM warning: Insufficient space for shared memory file:
INFO   | jvm 1    | 2026/03/16 21:14:25 |    2358032
INFO   | jvm 1    | 2026/03/16 21:14:25 | Try using the -Djava.io.tmpdir= option to select an alternate temp location.
INFO   | jvm 1    | 2026/03/16 21:14:25 |
INFO   | jvm 1    | 2026/03/16 21:14:25 | WrapperManager: Initializing...
INFO   | jvm 1    | 2026/03/16 21:14:26 | WARN  : Unknown Arguments detected.  Consider using --dry-run or --exec
INFO   | jvm 1    | 2026/03/16 21:14:26 | WARN  :   Argument: -XX:-HeapDumpOnOutOfMemoryError (interpreted as a JVM argument, from <command-line>)
INFO   | jvm 1    | 2026/03/16 21:14:26 | java.io.IOException: No space left on device
...
INFO   | jvm 1    | 2026/03/16 21:14:26 | java.io.IOException: No space left on device

 

SYMPTOMS:

  • The Portal upgrade terminal session times out

  • SSO and EM services remain in a stopped state after the upgrade completes

  • Service wrapper logs display Java IO exceptions related to disk space

Environment

DX NetOps Portal 25․4․5

Cause

CONTEXT: This issue occurs during or immediately after upgrading the portal to version 25․4․5 when the /tmp directory lacks adequate free space

IMPACT: Core architectural services are unavailable, preventing normal portal operations and user access

The /tmp directory has insufficient free space (e․g․, only 2․3 GB free out of 6 GB total) for the Java Virtual Machine to create shared memory files during the startup process 

Resolution

PREREQUISITES:

  • Administrator or root access to the Portal server

  • A new directory located on a partition with sufficient free space

 

STEPS:

1․ IDENTIFY OR CREATE NEW TEMPORARY DIRECTORY

  • Ensure it has sufficient space (8-10 GB)
  • Ensure it has appropriate permissions for install owner access.

2․ UPDATE SERVICE WRAPPER CONFIGURATIONS

  • Modify these user files. Do not edit the wrapper.conf, only the user versions.
    • $PORTAL_HOME/PerformanceCenter/DM/conf/wrapper-user.conf
    • $PORTAL_HOME/PerformanceCenter/EM/conf/wrapper-user.conf
    • $PORTAL_HOME/PerformanceCenter/PC/conf/wrapper-user.conf
    • $PORTAL_HOME/PerformanceCenter/sso/conf/wrapper-user.conf
  • In each file add the following line to redirect it to the new alternative /tmp location.
    • wrapper․java․additional․33=-Djava․io․tmpdir=/<New_tmp_Directory>

3․ RESTART AFFECTED SERVICES

  • Stop the services. Example commands:
    • systemctl stop caperfcenter_sso
    • systemctl stop caperfcenter_eventmanager
  • Confirm the services are down. Example commands:
    • systemctl status caperfcenter_sso
    • systemctl status caperfcenter_eventmanager
  • Start the services. Example commands:
    • systemctl start caperfcenter_sso
    • systemctl start caperfcenter_eventmanager
  • Confirm the services remain running: Example commands:
    • systemctl status caperfcenter_sso
    • systemctl status caperfcenter_eventmanager

 

VERIFY SUCCESS:

  • Review the wrapper logs to confirm the services start without the /tmp directory space error.

  • Verify the portal login page is accessible

Powered by Wolken Software