ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

The UVMS suddenly stops after a specific user action on Unix

book

Article ID: 87352

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Error Message :
Derby.log :
------------ BEGIN SHUTDOWN ERROR STACK -------------

ERROR XSDG1: Page Page(145,Container(0, 2256)) could not be written to disk, please check if the disk is full, or if a file system limit, such as a quota or a maximum file size, has been reached.

Upon startup in unistart.log :
Caused by: com.orsyp.InitializationException: Failed initializing server: Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection

Upon startup in uvserver.log :
| 2017-11-02 11:12:09 |INFO | main | com.orsyp.central.server.CheckCentralServer | UniverseException: Central IO Connection problem - Connection refused [UJCENT/dollaru_ppd_MgtServer/X]
| 2017-11-02 11:12:11 |ERROR| main | org.hibernate.util.JDBCExceptionReporter | Cannot create PoolableConnectionFactory (Failed to start database '/opt/AUTOMIC/univiewer_server/dollaru_ppd_MgtServer/data/data/uvmsdb' with class loader [email protected], see the next exception for details.)

Patch level detected:Univiewer Management Server 6.2.00
The UVMS on Linux stops after doing a specific action or can't be started at all.
For example, during package creation.
The user starting the UVMS is not root.

Cause

Cause type:
Configuration
Root Cause: UVMS stops itself when the user starting it has a "ulimit -n" inferior to 8000

Environment

OS: Linux

Resolution

The most recent version of UVMS 6.x increased the default value of the variable UXMAXFD from 256 to 8000.
As a result, on Linux where the user launching UVMS has not enough maximum file-descriptors, the UVMS stops when reaching the limit.

In order to fix the issue there are two options:

1. Reduce the value of the variable UXMAXFD within the values.xml via the command unisetvar
We recommend a value of at least 2048.
Check with ulimit -n / ulimit -Hn that the value set is within this marge.

2. Increase the hard / soft limits for the user launching UVMS / any other user different of root /etc/security/limits.conf

You can append the following two lines, in order to increase both soft / hard limits for any user to 4096 / 8192
* soft nofile 4096
* hard nofile 8192

Automic recommends option 2.

Fix Status: No Fix

Additional Information

Workaround :
N/A