OServer messages

Message origin

OServer logs messages from various modules, plugins and features. The format of the messages can vary according to the origin.
Message prefix Origin.
DACC defaultAccounting plugin.
DBHD and DBHC Messages related to the database operations.
IBCC InfiniBand module.
OSVC, ROSC, OSDx, OSAx OServer's core
x is an alphanumeric character.
QS1C Security1 plugin.

Message format

[timestamp] <level> message-id [connection-id] message-text
[timestamp] This part is always displayed.
Timestamp is in format [YYYY-MM-DD hh:mm:ss.pppppp], for example [2013-04-26 15:25:58.835795]
<level> This part is always displayed.
Message level can be one of the following:
  • critcal - The most serious and critical error, in most cases OServer will be terminated.
  • error - Errors, but mostly OServer is allowed to continue, only in some cases it can be terminated.
  • warning - Errors, mostly related to the requests, OServer will continue processing. It is worth analyzing and examining the reported issue.
  • notice - It is worth notifying the administrator about some changes or events.
  • info - Normal, reporting level of logging, it is only an informational level but it provides useful data.
  • debug - More detailed information.
  • trace - Even more detailed information.
  • message-id This part is always displayed.
    Message-id has the following format: AAAA-BB-CCC
    where:
  • AAAA is a prefix of a module, plugin or feature, more details about the real origin of messages can be found in the Message origin section.
  • BBmajor message-id
  • CCCminor message-id
  • connection-id This part may or may not be displayed.
    It is a unique identification number incremented by 1 within every new request.
    There are two counters - one for the secondary server and the other for the primary server and subserver
    When the new connection from Client arrives, the same connection ID is passed from the primary server to subserver.
    message-text This part is always displayed.
    The content of the message and its format are depending on the origin, severity of the message and its purpose.
    Some parts of the same message can vary, those variables are marked as {message_variable} in message descriptions.

    Message description

    The following topic shows the format of the message descriptions. Depending on the origin of the message, some of the description fields may or may not be displayed. Message description consist of several parts:

    message-id message-text

    Message type:
    message-type
    message-description
    Authorization required: user-level
    Source: message-origin
    Result: result
    HTTP status code: http-return-code
    User message: user-message
    Solution: solution

    Message part Description
    message-id Message identifier.

    bold text

    message-text The full message text can contain the message variables marked as {message_variable}.

    normal text

    user-level Authorization level required to proceed the request and to display this message, superuser or regular user

    normal text

    http-return-code Expected return code from the request.

    normal text

    user-message Some request can send message to user, user-message is the message that a user is expected to receive.

    normal text

    message-type One of the following labels:
  • critical
  • error
  • warning
  • information
  • debug
  • trace
  • normal text

    message-description Full message description.

    normal text

    message-origin The message origin is correlated with a prefix.

    normal text

    result What GPUServer does in a result of the condition reported by the message. Depending on the level of the message, the results could include: continue processing, request terminated, authorization failed etc.

    normal text

    solution Instructions for the GPUBox administration, including, actions to take, further investigations and decisions to make. When the solution cannot be found or it's expected to not solve the issue on its own, as a last resort solution redirects the administrator to contact the support.

    normal text

    Messages

    DBHC-AG-80A GPU id is not presented, GPU allocation failed

    Message type:
    error
    The allocation request does not contain the GPU id.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: GPU id is not presented, allocation failed
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-80B GPU id has negative value, GPU allocation failed

    Message type:
    error
    The allocation request has a negative GPU id. GPU's id must be an unsigned integer number.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: GPU id has negative value, allocation failed
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-81A Allocation mode is not presented, GPU allocation failed

    Message type:
    error
    The allocation request has no allocation mode specified. It must be either loose or strict.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: Allocation mode is not presented, GPU allocation failed
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-81B Invalid allocation mode. Only 'loose' or 'strict' is acceptable, GPU allocation failed

    Message type:
    error
    The allocation request has invalid allocation mode. Only loose or strict mode is acceptable.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: Invalid allocation mode. Only 'loose' or 'strict' is acceptable. GPU allocation failed
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-82A Usage mode is not presented, GPU allocation failed

    Message type:
    error
    The allocation request have no usage mode specified. It must be either shared or exclusive.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: Usage mode is not presented, GPU allocation failed
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-82B Invalid usage mode, GPU allocation failed

    Message type:
    error
    The allocation request has invalid usage mode. Only shared or exclusive mode is acceptable.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: Invalid usage mode, only 'loose' and 'strict' is acceptable, GPU allocation failed
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-83A Requested invalid number of GPUs, GPU allocation failed

    Message type:
    error
    The allocation request has invalid GPU number. Only unsigned integer numbers are acceptable.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: Requested invalid number of GPUs, only unsigned integer numbers are acceptable, GPU allocation failed
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-740 Number of requested GPUs exceeds the maximum number of allowed GPUs per user: {maxGPU}, GPU allocation failed

    Message type:
    warning
    Request is in strict allocation mode and number of requested GPUs exceeds the maximum number of GPUs allowed per user.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: Number of requested GPUs exceeds the maximum number of allowed GPUs per user: {maxGPU}, GPU allocation failed
    Solution:
    • Decrease the number of requested GPUs or use the default loose allocation mode to let GPUBox lower the value automatically.
    • Check of GPU availability in the GPUBox infrastructure.
    DBHC-AG-650 The number of requested GPUs was {requested_gpu_number} and has been lowered to {allocated_gpu_number}, 'loose' allocation mode was specified

    Message type:
    notice
    The number of requested GPUs exceeds the maximum number of allowed GPUs per user but the request is in the loose allocation mode and allocation was lowered to {allocated_gpu_number}.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    User message: The number of requested GPUs was {requested_gpu_number} and has been lowered to {allocated_gpu_number}, the maximum number of the GPUs allowed per user
    Solution: none
    DBHC-AG-860 User reached the maximum allowable number of GPUs from the same IP address: {exclusive_gpu},{shared_gpu},{oserver_max_gpu_per_user_per_ip} from {client_ip}, GPU allocation failed

    Message type:
    error
    The user reached the maximum number of allowed allocations from the same IP address.
    • {exclusive_gpu} - client's current number of the GPUs in the exclusive allocation mode,
    • {shared_gpu} - client's current number of the GPUs in the shared allocation mode,
    • {oserver_max_gpu_per_user_per_ip} - OServer's parameter, a maximum allowable number of the GPU allocation from the same IP address,
    • {client_ip} - IP address from where the allocation was attempted.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: The maximum allowable number of GPUs from this IP has been reached, GPU allocation failed
    Solution: If necessary, increase the value of oserver_max_gpu_per_user_per_ip in OServer's configurations.
    DBHC-AG-69E Specified GPU with id={gpu_id} does not exist

    Message type:
    notice
    Device with {gpu_id} was not registered.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed.
    HTTP status code: 400 Bad Request
    User message: Specified GPU does not exist
    Solution: Specify the correct GPU id from the DID column based on command gpubox free.
    DBHC-AG-77F Cannot allocate the GPU in 'exclusive' usage mode, name: {gpu_name} , mem: {memory}

    Message type:
    warning
    All of the GPUs with specified parameters i.e. with name {gpu_name} and memory size {memory} are not available at the moment.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed.
    HTTP status code: 400 Bad Request
    User message: Cannot allocate the GPU in 'exclusive' mode, try later or try to allocate it in 'shared' usage mode
    Solution:
    • try letter,
    • try allocation in shared usage mode,
    • check if some of the GPUs can be dropped elsewhere.
    DBHC-AG-780 User specified 'strict' allocation mode but there are too few GPUs: {gpu_free},{gpu_requested}, GPU allocation failed

    Message type:
    warning
    The user tried to allocate the GPU in the strict allocation mode, the number of requested GPUs by user exceeded the number of available GPUs.
    • {gpu_free} - number of available GPUs
    • {gpu_requested} - number of GPUs requested by user
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed.
    HTTP status code: 400 Bad Request
    User message: Requested number exceeds the number of available GPUs, enter new value
    Solution: User must:
    • lower the number of the requested GPUs,
    • change the allocation mode to loose,
    • change to the usage mode to shared,
    • wait until more GPUs are available.
    DBHC-AG-660 User specified 'loose' allocation mode and the number of allocated GPUs was lowered to {gpu_allocated}

    Message type:
    notice
    Requested number of the GPUs by user exceeded the number of FREE GPUs. User allocated in the loose mode so the number of allocated GPUs was constrained to the number of available GPUs.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed.
    User message: The number of allocated GPUs lowered to {gpu_allocated}
    Solution: if more GPUs is required, user must
    • change usage mode to shared or
    • wait until more GPUs are available.
    To make sure that requested number of GPUs is equal to allocated, user must use the strict allocation mode but the requested number of GPUs must be available.
    DBHC-AG-790 All GPUs are in use, name: {gpu_ame} , memory: {memory}, GPU allocation failed

    Message type:
    warning
    All of the available GPU with specified parameters {gpu_name} and {memory} are in use.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed.
    HTTP status code: 400 Bad Request
    User message: All GPUs are in use, try later
    Solution: User must try later or check if some of the GPUs can be dropped elsewhere.
    .
    DBHC-AG-500 Estimated number of available GPUs for allocation in 'shared' usage mode: {_estimatedGPU}

    Message type:
    information
    When user allocates the GPU in shared usage mode, the message displays the current estimated number of the GPUs that can be allocated in shared usage mode.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: processing continue
    User message: none
    Solution: none
    DBHC-AG-79A User specified 'strict' allocation mode but there are too few GPUs: {gpu_free}, {gpu_allocated}, GPU allocation failed

    Message type:
    warning
    In shared usage mode, the user requested GPUs but the request exceeded the number of available GPUs. The user tried to allocate in strict allocation mode and therefore the allocation failed.
    • {gpu_free} - number of available GPUs in free status,
    • {gpu_allocated} - number of GPUs requested by user
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: The number of requested GPUs exceeds the number of available, enter new value
    Solution: User must:
    • lower the number of requested GPUs or
    • change the allocation mode to loose or
    • change the usage mode to shared.
    DBHC-AG-670 User specified 'loose' allocation mode, the number of GPUs was lowered to {gpu_estimated}

    Message type:
    notice
    Number of the GPUs requested by user exceeded the number of free GPUs. User specified loose allocation mode and the number of allocated GPUs was lowered to number of free GPUs.
    • {gpu_estimated} - estimated number of the available GPUs in shared usage mode.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: Number of allocated GPUs lowered to number of available GPUs.
    User message: The number of requested GPUs exceeds the number of available, only {gpu_estimated} GPUs have been allocated.
    Solution: if more GPUs is required, user must
    • change usage mode to shared or
    • wait until more GPUs are available.
    To make sure that requested number of GPUs is equal to allocated, user must use the 'strict' allocation mode but the requested number of GPUs must be available.
    DBHC-AG-89B Invalid usage mode for GPU allocation: {invalid_mode}, GPU allocation failed

    Message type:
    error
    Invalid usage mode was specified, only shared or exclusive mode is acceptable.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed
    HTTP status code: 400 Bad Request
    User message: Invalid usage mode for GPU allocation
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-80Z Unexpected exception occurred while GPU is allocating, GPU allocation failed

    Message type:
    error
    Possibly the database error occurred while the GPU was being allocated.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-71L GPU's name was not specified, GPU allocation failed

    Message type:
    warning
    The GPU's name was not specified in input data.
    This message could be a consequence of usage unauthorized software or unauthorized access.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation request failed.
    HTTP status code: 500 Internal Server Error
    User message: Specify GPU name
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-50L GPU's memory was 0 or less. GPU with any memory size will be considered for allocation

    Message type:
    information
    GPU's memory was 0 or less. GPU with any memory size will be considered for further allocation.
    This message could be a consequence of usage unauthorized software or unauthorized access.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation request failed.
    HTTP status code: 500 Internal Server Error
    Result: GPU allocation continue, any memory size will be considered for allocation.
    User message: GPU's memory was 0 or less
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-51L GPUs with specified parameters and/or number are not available, GPU allocation failed in {usage_mode} usage mode

    Message type:
    information
    The user requested the GPU in exclusive usage mode but the number of available GPUs is 0.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation request failed.
    HTTP status code: 404 Not Found
    User message: GPUs with specified parameters and/or number are not available, GPU allocation failed
    Solution: User must:
    • wait until more GPUs is available,
    • allocate the GPUs in the shared usage mode,
    • allocate different type of GPU if available.
    DBHC-AG-53L GPUs with specified parameters and number are not available, GPU allocation failed in {usage_mode} usage mode

    Message type:
    information
    The user requested the GPU in shared usage mode but the number of available GPU is 0.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation request failed.
    HTTP status code: 404 Not Found
    User message: GPUs with specified parameters and number are not available, GPU allocation failed
    Solution: User must:
    • wait until the GPU is available,
    • allocate different type of GPU if available.
    DBHC-AG-54L GPUs with specified parameters ('shared' or 'strict') and number are not available, GPU allocation failed

    Message type:
    information
    The user requested the GPU in the shared usage mode and the strict allocation mode but the number of available GPUs is lower than requested.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation request failed.
    HTTP status code: 400 Bad Request
    User message: GPUs with specified parameters and number are not available, GPU allocation failed
    Solution: User must:
    • wait until GPUs is available, or
    • allocate different type of GPU if available.
    DBHC-AG-75L Invalid usage mode for GPU allocation: {mode}, GPU allocation failed

    Message type:
    warning
    Invalid mode was specified.
    This message could be a consequence of usage unauthorized software or unauthorized access.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: GPU allocation request failed.
    HTTP status code: 400 Bad Request
    User message: Invalid usage mode for GPU allocation
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-80U Unexpected exception occurred while allocating GPUs

    Message type:
    error
    Likely the database error occurred while allocating the GPU.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GS-05A GPU devices {deviceid} from IP {gpuserver_ip} changed status to {status}

    Message type:
    trace
    Status of device from GPUServer with IP address has been changed to {status}.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 200 OK
    User message: none
    Solution: none
    DBHC-GS-81A Unexpected exception occurred while retrieving GPU status

    Message type:
    error
    Possibly the database error occurred while retrieving GPU status.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-SG-51A GPU {gpu_id} status has been changed to {gpu_new_status}

    Message type:
    information
    The status of the GPU with {gpu_id} has been changed to {gpu_new_status}.
    The GPU status is changed when:
    • GPUServer connects to OServer and the GPU switches from the INIT status (all GPUs are set to the INIT status in the first stage of connecting GPUServer) to
      • FREE when GPU was not previously allocated, OServer's database was initialized or the GPU is newly introduced to the infrastructure
      • SHARED when GPU was previously allocated in SHARED usage mode.
      • EXCLUSIVE when GPU was previously allocated in EXCLUSIVE usage mode by single user.
    • GPUServer was terminated properly then all of the GPU devices switch to the STOPPED status.
    • GPUServer was abended or GPUServer is not reachable, then all of the GPU devices switch to the BROKEN status.
    • An administrator sets the status of the GPU to one of the following:
      • SHARED - GPU can be used in shared usage mode,
      • EXCLUSIVE - GPU can be used only in exclusive usage mode,
      • OFF - GPU cannot be used,
      • FREE - GPU is available for allocation.
      If the GPU cannot be switched immediately into desired status it becomes -PENDING. Depending on the number of allocation, GPU device can get the following status:
      • 0 users - SHARED - YES, EXCLUSIVE - NO, OFF - YES, FREE - YES
      • 1 user - SHARED - YES, EXCLUSIVE - YES, OFF - PENDING, FREE - PENDING
      • 2 users - SHARED - YES, EXCLUSIVE - PENDING, OFF - PENDING, FREE - PENDING
      • 2 and more users - SHARED - YES, EXCLUSIVE - PENDING, OFF - PENDING, FREE - PENDING.
      if GPU's has pending status, the desire state will get when number of user match the status requirements:
      • SHARED - 0 or more users
      • EXCLUSIVE - single user
      • OFF - 0 users
      • FREE - 0 users.
    Authorization required:Superuser
    Source: OServer's database
    Result: processing continue.
    HTTP status code: 200 OK
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-SG-80A Unexpected exception occurred while updating GPU status

    Message type:
    error
    Possibly the database error occurred while updating GPU status.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GR-81A Unexpected exception occurred while retrieving GPUServers status

    Message type:
    error
    Possibly the database error occurred while retrieving GPUServers status.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-CK-86T Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-86X Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-86Y Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-86Z Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-87T Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-87X Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-87Y Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-88T Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-88X Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-88Y Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-86V Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-87V Failed to initialize database, {detailed_error}

    Message type:
    error
    At the start of OServer, the database cannot be initialized due to an error specified by {detailed_error}.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CK-050 Database checked successfully

    Message type:
    trace
    Authorization required:Superuser
    Source: OServer's database
    Result: Continue processing.
    User message: none
    Solution: None.
    DBHC-CK-868 Unexpected exception occurred while checking database

    Message type:
    error
    An unexpected exception occurred during the database connection and checking the consistency.
    Authorization required:Superuser
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. analyze messages from OServer's log
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CL-50A {count} orphans records removed

    Message type:
    info
    The message is displayed in the log only when {count} > 0.
    It presents the number of removed orphan records.
    Authorization required:Superuser
    Source: OServer's database
    Result: orphan records removed.
    HTTP status code: 200 OK
    User message: Removed {count} orphans
    Solution: none.
    DBHC-CL-80B Unexpected exception occurred while removing orphans

    Message type:
    error
    Possibly the database error occurred while removing orphans.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-CD-960 Cannot connect to database, OServer is being terminated: {detailed_message}

    Message type:
    critical
    Connection to the database failed.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution:
    1. examine OServer's log and try to solve the issue according to {detailed_message},
    2. check if the database path exists.
    3. check if OServer has access to the directories on the path and the database file.
    4. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    5. if the cause of the issue cannot be found please contact support
    DBHC-CD-96A Database is not in thread-safe mode, OServer is being terminated

    Message type:
    critical
    Database driver is not in the thread-safe mode.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: OServer is being terminated.
    User message: none
    Solution: Check if the database driver is thread-safe, if not please contact support.
    DBHC-OD-81A Database's open issue, likely lock will happen {open_counter}, {expected_open_counter}

    Message type:
    error
    Number of database openings is not equal to the number of closures. Possibly the database lock can happen with the DBHC-BS-70A message.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: OServer will continue processing but the database can be unavailable due to locks.
    User message: none
    Solution:
    1. the DBHC-BS-70A message is presented - restart OServer with signal SIGQUITE (force to quite)
    2. the DBHC-BS-70A is not presented - continue processing,
      1. analyze messages from OServer's log.
      2. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
      3. if the above step did not help, collect system's details, save log and please contact support
    BDHC-CD-81H {detailed_message}

    Message type:
    error
    Message show an issue of database in {detailed_message}.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: OServer can continue processing but database can be unavailable due errors described in {detailed_message}.
    User message: none
    Solution:
    1. analyze messages from OServer's log.
    2. check if database exists and if not accessed outside the OServer
    3. rename the database in configuration file (parameter 'oserver_db_path') and restart OServer
    4. if the above step did not help, collect system's details, save log and please contact support
    DBHC-CD-961 Unexpected database exception occurred while connecting database, {detailed_message}

    Message type:
    critical
    Unexpected exception occurred while connecting to the database.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: OServer is terminated.
    User message: none
    Solution: Examine OServer's log, when the issue cannot be solved please contact support.
    DBHC-CD-962 Unexpected exception occurred while connecting database

    Message type:
    critical
    Unexpected exception occurred while connecting to the database.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: OServer is terminated.
    User message: none
    Solution: Examine the OServer log, when the issue cannot be solved please contact support.
    DBHC-CG-80G Unexpected exception occurred while counting GPUs for user {userid};

    Message type:
    error
    Possibly the database error occurred while counting the GPUs for the user.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-DG-70A Orphan record detected for {gpu_id}

    Message type:
    warning
    Specified user's GPU id exist but it is in an orphan record.
    GPU was allocated by a user and due to some inconsistent operations the GPU was removed but its counterpart, lease record, was not removed. Now the lease record becomes an orphan pointing to a non-existing GPU.
    Authorization required:Regular user
    Source: OServer's database
    Result: drop GPU request failed.
    HTTP status code: 404 Not Found
    User message: none
    Solution:
    • Run the agpubox maint orphans command to remove the orphan records.
    DBHC-DG-74C Specified GPU cannot be dropped

    Message type:
    warning
    Requested GPU does not exists and cannot be dropped.
    Authorization required:Regular user
    Source: OServer's database
    Result: drop GPU request failed.
    HTTP status code: 400 Bad Request
    User message: Specified GPU cannot be dropped
    Solution: Specify a correct GPU id.
    DBHC-DG-65W GPU in status 'borken' or 'stopped' was dropped {gpu_id}

    Message type:
    notice
    The user dropped a GPU that was in the broken or stopped status.
    • GPUServer must have been forced to stop while some GPUs were allocated from this server.
    • GPUServer was killed with SIGKILL(9) signal or abended and GPU switched to the broken status.
    Authorization required:Regular user
    Source: OServer's database
    Result: GPU has been dropped
    HTTP status code: 200 OK
    User message: GPU in status 'broken' or 'stopped' was dropped
    Solution:
    • If GPU is in the broken status, check why GPUServer was terminated with SIGKILL or abended.
    • If GPU is in the stopped status, check why GPUServer was terminated.
    Restart servers if necessary.
    DBHC-DG-54W Specified GPUs cannot be dropped {gpuid}

    Message type:
    information
    GPU with specified ID does not exist.
    Authorization required:Regular user
    Source: OServer's database
    Result: drop GPU request failed.
    HTTP status code: 404 Not Found
    User message: Specified GPU cannot be dropped
    Solution: The user must specify a correct GPU ID basing on the gpubox list command.
    DBHC-DG-80A Unexpected exception occurred while dropping GPUs

    Message type:
    error
    Possibly the database error occurred while dropping the GPUs.
    Authorization required:Regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-DI-35A GPU with id: {gpub_id} is not allocated

    Message type:
    debug
    GPU {gpu_id} specified by the user is not allocated.
    Authorization required:Regular user
    Source: OServer's database
    Result: empty request
    HTTP status code: 400 Bad Request
    User message: Specified GPU id is not allocated
    Solution: User must specify a correct GPU ID.
    .
    DBHC-DI-80A Unexpected exception occurred while dropping GPUs

    Message type:
    error
    Possibly the database error occurred while dropping the GPUs.
    Authorization required:Regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-DT-300 All GPUs have been already dropped

    Message type:
    debug
    Every previously allocated GPU has already been dropped.
    Authorization required:Regular user
    Source: OServer's database
    Result: empty request
    HTTP status code: 400 Bad Request
    User message: All GPUs have been already dropped
    Solution: User must have currently allocated GPUs in order to drop them.
    .
    DBHC-DT-80A Unexpected exception occurred while dropping GPUs

    Message type:
    error
    Possibly the database error occurred while dropping the GPUs.
    Authorization required:Regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-DU-80A Unexpected exception occurred while dropping GPUs

    Message type:
    error
    Possibly the database error occurred while dropping the GPUs.
    Authorization required:Regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-AG-80V Unexpected exception occurred while searching for GPU

    Message type:
    error
    Possibly the database error occurred while searching for GPU.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GC-350 User does not have allocated GPUs for specified IP

    Message type:
    debug
    The user have no GPUs allocated from the specific IP address and cannot retrieve the configuration.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: empty request
    HTTP return code: 204 No Content
    User message: User does not have allocated GPUs for specified IP
    Solution: User must allocate the GPUs.
    DBHC-GC-351 User does not have allocated GPUs

    Message type:
    debug
    The user have no GPU allocated and cannot retrieve the configuration.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: empty request
    HTTP return code: 204 No Content
    User message: User does not have allocated GPUs
    Solution:User must allocate GPU.
    DBHC-GC-80Z Unexpected exception occurred while retrieving allocated GPUs

    Message type:
    error
    Possibly the database error occurred while the GPU configuration was being retrieved.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GD-51A No devices in repository

    Message type:
    info
    Repository does not have any registered devices yet.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 204 No Content
    User message: none
    Solution: The administrator must start GPUServer to register device.
    DBHC-GD-80D Unexpected exception occurred while getting GPUs allocated by user

    Message type:
    error
    Possibly the database error occurred while getting GPUs allocated by user.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GT-50A User does not have any devices allocated from this GPUServer: {ip_address}

    Message type:
    information
    The user does not have any devices allocated from this GPUServer.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 400 Bad Request
    User message: User does not have any devices allocated from this GPUServer: {ip_address}
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GT-80D Unexpected exception occurred while retrieving GPUs allocated by user

    Message type:
    error
    * * Possibly the database error occurred while retrieving the GPUs allocated by the user.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-BU-80A Unexpected exception occurred while retrieving GPUservers' interfaces

    Message type:
    error
    Possible database error occurred while retrieving GPUservers.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find owner and origin of the request and check if it's correct.
    • If the issue cannot be solved please contact support.
    DBHC-AU-250 User's current allocation, exclusive:{exclusive}, shared: {shared}

    Message type:
    trace
    Display in log the number of currently allocated GPUs by user.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 200 Internal Server Error
    User message: none
    Solution: none.
    DBHC-AU-80D Unexpected exception occurred while retrieving GPUs allocated by user

    Message type:
    error
    Possibly the database error occurred while retrieving the GPUs allocated by the user.
    Authorization required:Regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GG-80A Unexpected exception occurred while retrieving GPUServers

    Message type:
    error
    Possibly the database error occurred while retrieving GPUServers.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GH-80A Unexpected exception occurred while retrieving GPUServers

    Message type:
    error
    * * Possibly the database error occurred while retrieving GPUServers.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GR-80A Unexpected exception occurred while retrieving GPUServers' interfaces

    Message type:
    error
    Possibly the database error occurred while retrieving GPUServers.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-IG-80T Invalid IP address in request

    Message type:
    error
    While the GPU device is being registered, OServer detects an incorrect IP address of GPUServer.
    Authorization required:Superuser
    HTTP status code: 400 Bad Request
    Source: OServer's database
    Result: Request termination.
    User message: none
    Solution: Examine OServer's log, when the issue cannot be solved please contact support.
    DBHC-IG-510 Registered GPU (name: {name}, device: {device}, gdomain: {gdomain} ) from IP: {ip}, hostname {hostname}

    Message type:
    information
    At the start, GPUServer sends configuration of GPU devices. OServer displays information about every registered GPU device.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU device registered.
    User message: none
    Solution: none
    DBHC-IG-840 Registering new device type failed

    Message type:
    error
    Registering new type of device failed.
    Authorization required:Superuser
    Source: OServer's database
    Result: Processing continue, GPU not registered.
    HTTP status code: 400 Bad Request
    User message: none
    Solution:
    • Probably data is inconsistent.
      • Set the new database in the oserver_db_path parameter and restart OServer.
      • Save current database for support review.
      • Any valid allocations will be lost.
      • please contact support
    • when the issue cannot be solved please contact support.
    DBHC-IG-810 Failed to register GPU, unexpected exception occurred

    Message type:
    error
    At the start, GPUServer sends configuration of GPU devices and registration of new type of GPU devices failed due to unexpected exception.
    Authorization required:Superuser
    Source: OServer's database
    Result: Processing continue, GPU not registered.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine OServer's log, when the issue cannot be solved please contact support.
    DBHC-GU-80A Invalid query string {query_string} in URI {uri}

    Message type:
    error
    An incorrect query string user= was given in URI.
    Authorization required:Superuser
    Source: OServer's database
    Result: drop request failed.
    HTTP status code: 400 Bad Request
    User message: none
    Solution: A query string must be in format userid={userid}, a correct query string must match the regular expression ^userid=([0-9a-zA-Z$_@]+)$
    DBHC-GU-31A User does not have GPUs allocated at the moment

    Message type:
    debug
    The user have no GPU allocated at the moment.
    Authorization required:Superuser
    Source: OServer's database
    Result: empty request
    HTTP status code: 204 No Content
    User message: User does not have GPUs allocated at the moment
    Solution: The user must allocate the GPUs.
    .
    DBHC-GU-80E Unexpected exception occurred while retrieving GPUs allocated by user

    Message type:
    error
    Possibly the database error occurred while retrieving the GPUs allocated by the user.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-GU-300 User does not have GPUs allocated at the moment

    Message type:
    debug
    The user have no GPU allocated at the moment.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: empty request
    HTTP status code: 204 No Content
    User message: User does not have GPUs allocated at the moment
    Solution: The user must allocate the GPUs.
    .
    DBHC-GU-80D Unexpected exception occurred while retrieving GPUs allocated by user

    Message type:
    error
    Possibly the database error occurred while retrieving the GPUs allocated by the user.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-LG-31B User does not have GPUs allocated at the moment

    Message type:
    debug
    The user have no GPU allocated at the moment.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: empty request
    HTTP status code: 204 No Content
    User message: Devices are not allocated
    Solution: The user must allocate the GPUs.
    .
    DBHC-LG-80F Unexpected exception occurred while retrieving GPUs allocated by user

    Message type:
    error
    Possibly the database error occurred while retrieving the GPUs allocated by the user.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-RG-82A Error while recovering GPU {deviceid} from {hostname}, {rc}

    Message type:
    error
    OServer could not recover the GPU device from GPUServer {hostname}. Device has ordinal number {deviceid}. {rc} is an internal error code.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU left in init state.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Remove all devices from OServer by sending the agpubox drop command, or from Web Console, and restart GPUServer {hostname}.
    • If the issue cannot be solved please contact support.
    DBHC-RG-82C Error while recovering GPU {deviceid} from {hostname}, {rc}

    Message type:
    error
    OServer could not have recovered the GPU device from GPUServer {hostname}. Device has ordinal number {deviceid}. {rc} is an internal error code.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU left in init state.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Remove all devices from OServer by sending the agpubox drop command, or from Web Console, and restart GPUServer {hostname}.
    • If the issue cannot be solved please contact support.
    DBHC-RG-50A {count} GPU recovered: {gdomain}

    Message type:
    info
    When GPUServer or OServer stops or connection was terminated, the GPU switches to broken or stopped status, after restarting one of the GPUServers, OServer is trying to recover the allocated GPUs and set the correct number of users and the previous status: free, shared or exclusive
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU recovered.
    User message: none
    Solution: none.
    DBHC-RG-82D Unexpected exception occurred while recovering GPU {deviceid} from GPUServer {hostname}

    Message type:
    error
    OServer could not have recovered the GPU device from GPUServer {hostname}. Device has ordinal number {deviceid}.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU left in INIT state.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Remove all devices from OServer by sending the agpubox drop command, or from Web Console, and restart GPUServer {hostname}.
    • If the issue cannot be solved please contact support.
    DBHC-SD-74D Administrator was trying to drop GPU in status 'exclusive' or 'shared', GPU id: {gpuid}

    Message type:
    warning
    The administrator tried to drop GPU devices with Global ID (GID) {gpuid} from OServer but it is allocated by user in shared or exclusive mode.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU is allocated by user and cannot be removed.
    HTTP status code: 400 Bad Request
    User message: GPU is in exclusive or shared status
    Solution: Specify correct GID for device.
    .
    DBHC-SD-51A GPU with GID = {gpuid} removed

    Message type:
    info
    The administrator successfully drops the GPU with {gpuid}. The administrator's drop of GPU is irreversible.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU removed from GPUBox infrastructure.
    HTTP status code: 200 OK
    User message: none
    Solution: In order to revert drop, administrator has to restart GPUServer with the GPU.
    .
    DBHC-SD-74E GPU with GID = {gpuid} does not exist or cannot be removed

    Message type:
    warning
    The administrator tried to drop GPU devices with Global ID (GID) {gpuid} from OServer but it does not exists and cannot be removed.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPU does not exists and cannot be removed.
    HTTP status code: 404 Not Found
    User message: GPU does not exist
    Solution: Specify correct GID for device.
    .
    DBHC-SD-80A Unexpected exception occurred while dropping GPU by superuser

    Message type:
    error
    Possibly the database error occurred while dropping GPU by superuser.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-FG-300 All GPUs are in use

    Message type:
    debug
    The user requested list of available GPUs but the list is empty at the moment.
    Authorization required:Regular user
    Source: OServer's database
    Result: Processing continue, all GPUs are busy.
    HTTP status code: 204 No Content
    User message: All GPUs are in use, please try later
    Solution:
    • recheck on GPUs availability,
    • drop some of users' unused GPUs.
    DBHC-FG-830 Unexpected exception occurred while getting free GPU list

    Message type:
    error
    The user requested the list of available GPUs but the request has failed due to an unexpected exception.
    Authorization required:Regular user
    Source: OServer's database
    Result: request of free GPU failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-SF-30S All GPUs are in use

    Message type:
    debug
    The user requested list of available GPUs but the list is empty at the moment.
    Authorization required:Superuser
    Source: OServer's database
    Result: Processing continue, all GPUs are busy.
    HTTP status code: 204 No Content
    User message: All GPUs are in use, please try later
    Solution:
    • recheck of GPUs availability,
    • drop some of users' unused GPUs.
    DBHC-SF-83S Unexpected exception occurred during getting free GPU list

    Message type:
    error
    The user requested list of available GPUs but the request has failed due to an unexpected exception.
    Authorization required:Superuser
    Source: OServer's database
    Result: failed request for the list of free GPUs.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-SH-810 Unexpected exception occurred while set IP {ip_address} for user {userid}

    Message type:
    error
    Authorization required:Superuser
    Source: OServer's database
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Check if IP address and userid is correct, check if database is not locked.
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHD-BS-70A [{threadid}] {n}th time of claiming db access

    Message type:
    warning
    Thread {threadid} has trying access {n} times but database is locked.
    This message is showed after 50th unsuccessful attempt access to database and showed every 10th attempt.
    Thread will continue retrying in every 0.5sec.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: thread access to database is blocked
    Solution:
    • Examine {detailed_message} to find the cause of issue. Possibly there are too many requests per second.
    • If the problem repeats please contact support.
    DBHC-UG-50A New device {GPU_name} with {total_memory}GB was registered

    Message type:
    informational
    At the start, GPUServer sends configuration of GPU devices. When the device name and memory size is different than those already registered, OServer adds the new device type to an internal list. OServer identifies the GPU devices by {GPU_name} and {total_memory} across entire service e.g. in the gpubox free command
    Authorization required:Superuser
    Source: OServer's database
    Result: New type of GPU was registered and can be used in GPUBox infrastructure.
    User message: none
    Solution: none
    DBHC-UG-810 Registering new type of GPU {_GPUname} with {_totalGlobalMem}GB failed

    Message type:
    error
    Registering the new type of GPU device has failed.
    At the start, GPUServer sends its own GPU devices configuration. When the device name and memory size is different than those already registered, OServer adds the new device type to an internal list. OServer identifies the GPU devices by {GPU_name} and {total_memory} across entire service e.g. in the gpubox free command
    Authorization required:Superuser
    Source: OServer's database
    Result: Processing continue but the GPU is not registered.
    User message: none
    Solution: Examine OServer's log, when the issue cannot be solved please contact support.
    DBHC-RA-82C Error while updating RESTful api {restful_api} for {hostname}, {rc}

    Message type:
    error
    GPUServer was restarted and the gpuserver_rest_bind parameter on {hostname} has been changed to {restful_api} since the last successful connection. Now, OServer has been trying to update GPUServer's interface to new value but it failed.
    {rc} is an internal code
    Authorization required:Superuser
    Source: OServer's database
    Result: GPUServer's RESful api is not updated in OServer and communication between OServer and GPUServer can be corrupted.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Remove GPU devices related to {hostname} from OServer by sending the agpubox drop command, or from Web Console, and restart GPUServer {hostname}. All GPU devices and RESTful api interface should be registered again from scratch.
    • If the issue cannot be solved please contact support.
    DBHC-RA-50A RESTful api for {hostname} changed to {restapi}, server version is {version}, ({count})

    Message type:
    info
    GPUServerwas restarted and the gpuserver_rest_bind parameter on {hostname} has been changed to {restful_api} since last successful connection. Now, OServer registered new GPUServer's interface to new value {restapi}.
    • {version} - GPUServer's version
    • {count} - number of GPU available in GPUServer
    Authorization required:Superuser
    Source: OServer's database
    HTTP status code: 200 OK
    Result: GPUServer's RESful api has been updated.
    User message: none
    Solution: none
    DBHC-RA-82D Unknown exception occurred while while updating RESTful api for {hostname}

    Message type:
    error
    GPUServer was restarted and the gpuserver_rest_bind parameter on {hostname} has been changed to {restful_api} since last successful connection. OServer was trying to update GPUServer's interface to new value but suffered from an unexpected exception.
    Authorization required:Superuser
    Source: OServer's database
    Result: GPUServer's RESFul api is not updated in OServer and communication between OServer and GPUServer will corrupted.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Remove GPU devices related to {hostname} from OServer by sending the agpubox drop command, or from Web Console, and restart GPUServer {hostname}. All GPU devices and RESTful API interface should be registered from scratch.
    • If the issue cannot be solved please contact support.
    DBHC-WA-35A Lease record for GPU id {gpuid} does not exist

    Message type:
    debug
    The GPU was dropped or the status has been changed and OServer is requesting to save the accounting information of leased records if there are any.
    Lease record does not exist for GPU {gpuid}.
    Authorization required:Superuser
    Source: OServer's database
    Result: The accounting information is not saved
    User message: none
    Solution: none
    .
    DBHC-WA-36A Saved {count} accounting records for GPU id {gpuid}

    Message type:
    debug
    The GPU was dropped or changed its status and OServer is requesting to save the accounting information of leased records if there are any.
    {count} lease records accounting information was saved.
    Result: The accounting information is saved.
    User message: none
    Solution: none.
    DBHC-WA-35B Lease record for GPU from IP {ip_address} does not exist

    Message type:
    debug
    More than one GPU was dropped or the status has been changed at once from GPUServer with {ip_address} and OServer is requesting to save the accounting information of leased records if there is any.
    Lease records do not exist for GPUs allocated from {ip_address}.
    Authorization required:Superuser
    Source: OServer's database
    Result: Accounting information is not saved
    User message: none
    Solution: none
    .
    DBHC-WA-36B Saved {count} lease records for GPU from IP {ip_address}

    Message type:
    debug
    More than one GPU was dropped or or the status has been changed at once from GPUServer with {ip_address} and OServer is requesting to save the accounting information of leased records if there is any.
    {count} lease records accounting information were saved.
    Result: Accounting information is saved.
    User message: none
    Solution: none.
    DBHC-ZT-80A Unexpected exception occurred while updating GPU allocation

    Message type:
    error
    Possibly the database error occurred while updating GPU allocation.
    Authorization required:Superuser
    Source: OServer's database
    Result: request failed.
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine OServer's log, find the owner and origin of the request and check if they are correct.
    • If the issue cannot be solved please contact support.
    DBHC-DD-81A Database's close issue, likely lock will happen

    Message type:
    error
    Number of the database closures is not equal to the number of openings. Likely the database locks will happen with the DBHC-BS-70A message.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: OServer will continue processing but the database can be unavailable due to the locks.
    User message: none
    Solution:
    • the DBHC-BS-70A message is presented, try to restart OServer with the SIGQUITE signal (force to quite),
    • the DBHC-BS-70A message is not presented then OServer keeps on processing, however observe OServer's log,
      • examine OServer's log,
      • check if database exists and if it's not accessed outside the OServer
      • if the cause of the issue cannot be found please contact support
    DBHC-DD-81B Cannot close database: {detailed_message},{return_code}

    Message type:
    error
    The database cannot be closed. It must be closed to continue processing of next requests.
    Authorization required:Superuser or regular user
    Source: OServer's database
    Result: Probably database will be locked for next requests but further processing of OServer is being continued.
    User message: none
    Solution:
    • the DBHC-BS-70A message is presented, try restart OServer with signal SIGQUITE (force to quite),
    • the DBHC-BS-70A message is not presented OServer continues processing but observe OServer's log,
      • examine OServer's log,
      • check if the database exists and if it's not accessed from outside the OServer
      • if the cause of the issue cannot be found please contact support
    DACC-WA-79A Cannot open or create output file for accounting: {output_file}

    Message type:
    warning
    Accounting plugin cannot open or create output file specified in oserver_accounting_config configuration parameter.
    File is created when it does not exist yet.
    When {output_file} is empty, OServer displays it as 'empty string used'.
    Authorization required:Superuser
    Source: Accounting plugin
    Result: processing continue but accounting is redirected to OServer's log.
    Solution:
    • check if path to file is correct and OServer has access
    • check if OSerer's user can create files in directory.
    DACC-WA-59A Accounting output file opened successfully: {output_file}

    Message type:
    informaton
    Accounting plugin opened or created successfully {output_file} file by configuration parameter oserver_accounting_config.
    Authorization required:Superuser
    Source: Accounting plugin
    Result: processing continue, accounting is write out to {output_file}.
    Solution: none
    DACC-WA-71A Cannot open output file for accounting: {output_file}, save accounting in log

    Message type:
    warning
    The acounting plugin cannot open the output file. The messages shows about every 5th failure to save the accounting information into file.
    Authorization required:Superuser or regular user
    Source: Accounting plugin
    Result: accounting is output to log with message DACC-WA-50B.
    Solution:
    1. Check if {output_file} path is correct.
    2. Check if user has access to {output_file} and all directories on path.
    DACC-WA-50A Accounting saved for user {userid}, {username}

    Message type:
    information
    The accounting for the user {userid}, {username} has been saved to file indicated by the {oserver_accounting_config} parameter.
    Authorization required:Superuser or regular user
    Source: Accounting plugin
    Result: processing continue.
    Solution: none
    DACC-WA-50B userid:{userid};
    username:{username};
    user_ip:{userip};
    time_start:{time_start};
    time_end:{time_end};
    consumed_seconds:{consumed_seconds};
    gpu_name:{gpu_name};
    gpu_server_ip:{gpu_server_ip};
    gpu_global_domain:{gpu_global_domain};
    gpu_pci_bus_id:{gpu_pci_bus_id};
    gpu_pci_dev_id:{gpu_pci_dev_id}

    Message type:
    information
    This message is preceded by 'DACC-WA-71A' on about every 5th failure of opening output file.

    Message contains several blocks in format:
    • {parameter_name}:{value};
    Facts about message format:
    • {parameter_name} (userid, username,etc.) are followed by a colon,
    • {value} is followed by a semicolon,
    • there is a single space between the message id and the userid,

    Description:
    • userid - the user's account name
    • username - the user's name
    • user_ip - the Client's ip address
    • time_start - time when the GPU was allocated
    • time_end - time when the GPU was dropped
    • consumed_seconds - the difference in seconds between {time_end} and {time_start}
    • gpu_name - the name of the GPUs that the user allocated
    • gpu_server_ip - the GPUServer's ip address
    • gpu_global_domain - the PCI global domain id in a hexadecimal format 0xAABB, where
      • AA is third octet of GPUServer's IP address
      • BB is last octet of GPUServer's IP address
    • gpu_pci_bus_id - the physical GPUServer's PCI bus id
    • gpu_pci_dev_id - the physical GPUServer's PCI device id
    Authorization required:Superuser or regular user
    Source: Accounting plugin
    Result:
    • the accounting information output is redirected to log,
    • processing continues
    Solution: none
    OSRV-OS-91A [{pid}] OServer received unexpected exception

    Message type:
    critical
    OServer received an unknown exception and is being terminated.
    Entire shutdown sequence is skipped.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is being terminated and it returns code 3.
    Solution:
    OSU0 User must be a root to switch to another one

    Message type:
    critical
    The invoker of OServer must be a root.
    Source: OServer
    Result: OServer is terminated, return code 1.
    Solution: Start OServer as root.
    OSU1 user {user} does not exist or cannot retrieve the user's information, {errno message} ({errno_id})

    Message type:
    critical
    Argument '-u' was passed via command line to set new user but the operation failed due to {error_message}.
    Source: OServer
    Result: OServer is terminated, return code 1.
    Solution: analyze {errno_message} to see if the error can be fixed, otherwise please contact support
    OSU2 cannot set user {user} for OServer, {errno message} ({errno_id})

    Message type:
    critical
    Argument '-u' was passed via command line to set new user but the operation failed due to {error_message}.
    Source: OServer
    Result: OServer is terminated, return code 1.
    Solution: analyze {errno_message} to see if the error can be fixed, otherwise please contact support
    OSD1 cannot start daemon for OServer- detaching process failed {errno message} ({errno_id})

    Message type:
    critical
    The OServer cannot start the daemon process. Detaching process has failed. This message is redirected to STDERR and it is not displayed in the log.
    Source: OServer
    Result: OServer is terminated.
    Solution: analyze {errno_message} to see if the error can be fixed, otherwise please contact support
    OSD2 cannot start daemon for OServer- detaching process failed {errno message} ({errno_id})

    Message type:
    critical
    The OServer cannot start the daemon process. Detaching process has failed. This message is redirected to STDERR and it is not displayed in log.
    Source: OServer
    Result: OServer is terminated.
    Solution: analyze {errno_message} to see if the error can be fixed, otherwise please contact support
    OSA1 Configuration file name has zero length

    Message type:
    critical
    The configuration file given by one of the possible ways is empty.
    At this stage of initialization the log is not yet available, the message is redirected to STDERR output.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: The OServer is being terminated and it will return code 3.
    Solution: none
    OSA2 Cannot find configuration file

    Message type:
    critical
    The OServer cannot open the configuration file and it will be terminated.
    At this stage of initialization the log is not yet available, the message is redirected to STDERR output.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: The OServer is being terminated and it will return code 1.
    Solution: none
    OSRV-OS-94B [{pid}] OServer received unexpected exception

    Message type:
    critical
    The OServer has received an unknown exception and is about to be terminated.
    The OServer will try to perform the normal shutdown sequence.
    Authorization required:Superuser
    Source: OServer
    Result: The OServer is being terminated and it will return code 3.
    Solution:
    OSRV-OS-96B [{pid}] Network communication exception occurred, {detailed_message}

    Message type:
    critical
    An exception related to the communication has occurred.
    Authorization required:Superuser
    Source: OServer
    Result: The OServer is being terminated and it will return code 3.
    Solution:
    • Verify if license is set correctly in the configuration file, examine the following parameters:
      • oserver_license_uid
      • oserver_license_key
    • Examine OServer's log, especially messages related to TCP/IP or InfiniBand communication.
    • If the issue cannot be solved please contact support.
    OSRV-OS-94E [{pid}] OServer received other unexpected exception

    Message type:
    critical
    The OServer received an unknown exception and is about to be terminated.
    It will try to perform the normal shutdown sequence.
    Authorization required:Superuser
    Source: OServer
    Result: The OServer is being terminated and it will return code 3.
    Solution:
    OSVC-CH-500 Subprocess ended, pid: {pid}, NORMAL: {status}

    Message type:
    information
    Authorization required:Superuser
    Source: OServer
    Result: Subprocess ended normally.
    Solution: none.
    OSVC-CH-66A Subprocess ended abnormally, pid: {pid}, SIGNAL: {signal}

    Message type:
    notice
    Subprocess received a {signal}.
    Authorization required:Superuser
    Source: OServer
    Result: Subprocess ended abnormally.
    Solution: Verify the cause of the subprocess termination, examine the OServer's log.
    OSVC-CH-66B Subprocess ended abnormally, pid: {pid}

    Message type:
    notice
    Subprocess received abnormal termination signal.
    Authorization required:Superuser
    Source: OServer
    Result: Subprocess ended abnormally.
    Solution: Verify the cause of the subprocess termination, examine the OServer's log.
    OSVC-CH-66C Subprocess received stop signal, pid: {pid}, {status}

    Message type:
    notice
    Subprocess received the stop signal.
    Authorization required:Superuser
    Source: OServer
    Result: Subprocess is paused.
    Solution: none.
    OSVC-CH-66D Subprocess received continue signal, pid: {pid}

    Message type:
    notice
    Subprocess received the continue signal.
    Authorization required:Superuser
    Source: OServer
    Result: Subprocess resume processing.
    Solution: none.
    OSVC-CH-66E Subprocess ended, pid: {pid}, UNKNOWN reason

    Message type:
    notice
    Subprocess ended but the reason of the termination is unknown.
    Authorization required:Superuser
    Source: OServer
    Result: The subprocess of OServer is being terminated.
    Solution: Examine the OServer's messages to find the reason.
    OSVC-OD-96C Parameter 'oserver_db_path' not found in configuration file, OServer is being terminated

    Message type:
    critical
    Working path to the OServer's database is required to continue the OServer's initialization.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is terminated and it returns code 1.
    Solution: Check if the path is correct and the database file is available.
    OSVC-OD-610 Connected to database {database_path}

    Message type:
    notice
    OServer is connected to the database specified by {database_path}.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues processing with {database_path}.
    Solution: none.
    OSVC-OD-50Z Database configuration has been checked successfully

    Message type:
    information
    OServer has checked the database integration successfully and it will continue processing.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues processing
    Solution: none.
    OSVC-OD-84A Cannot connect to database: {oserver_db_path}, OServer will try to fix the issue

    Message type:
    error
    Due to an unexpected database exception OServer cannot connect to database.
    Authorization required:Superuser
    Source: OServer
    Result: OServer will try to fix the issue and continue processing. If the retry fails OServer will be terminated with return code 1.
    Solution:
    -Current database will be removed and OServer will make an attempt to reinitialize the database.
    • if the attempt failed, delete the database {oserver_db_path} and start OServer, database will be reinitialized.
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-OD-84D Cannot remove database: {oserver_db_path}, {reason}

    Message type:
    error
    OServer cannot remove database to fix the issue.
    Authorization required:Superuser
    Source: OServer
    Result: OServer will be terminated with return code 1.
    Solution:
    • Check the reason, likely the authorization does not match.
    • Remove the database {oserver_db_path} manually and start OServer, database will be reinitialized.
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-OD-84C Cannot remove database: {oserver_db_path}

    Message type:
    error
    OServer cannot remove database to fix the issue.
    Authorization required:Superuser
    Source: OServer
    Result: OServer will be terminated with return code 1.
    Solution:
    • Remove the database {oserver_db_path} manually and start OServer, database will be reinitialized.
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-OD-84B Cannot fix the issue related to OSVC-OD-84A

    Message type:
    error
    Due to an unexpected database exception OServer cannot connect to database.
    Authorization required:Superuser
    Source: OServer
    Result: Data base issue is not fixed.
    Solution:
    • Delete the database {oserver_db_path} and start OServer, database will be reinitialized.
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-OD-970 Cannot connect to database: {oserver_db_path}, OServer is being terminated

    Message type:
    critical
    Due to an unexpected database exception OServer cannot continue the processing and started the termination procedure.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is being terminated and it returns code 1.
    Solution:
    • if you changed the license key or/and license UID (parameter oserver_license_key and oserver_license_uid) delete the database {oserver_db_path} and restart OServer.
    • if it is not required to preserve the allocations of the GPUs you can stop OServer, delete the database {oserver_db_path} and start OServer, database will be reinitialized.
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-CF-500 Configuration file was passed by [-c] parameter: {config_file}

    Message type:
    information
    The OServer's configuration file was passed in the command line parameter.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues processing with the {config_file} file.
    Solution: none.
    OSVC-CF-510 Configuration file was passed by environment variable OSERVER_CONF: {config_file}

    Message type:
    information
    The OServer's configuration file was passed in the environment variable 'OSERVER_CONF'.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues processing with the {config_file} file.
    Solution: none.
    OSVC-CF-520 Configuration file: {configuration_file}

    Message type:
    information
    OServer opened the configuration file from the default location.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues processing with the file.
    Linux: /etc/oserver.conf.
    Windows: PROGRAMDATA%.conf
    Solution: none.
    OSVC-GC-900 I/O error while reading configuration file: {detailed_message}

    Message type:
    critical
    An I/O exception occurred while trying to read the configuration file.
    The message is also redirected to STDERR.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is terminated and it returns code 1.
    Solution:
    • Check if the configuration file is accessible by OServer's user.
    • Examine the OServer's log.
    OSVC-GC-910 Parse error in configuration file: {file}:{line}, {detailed_message}

    Message type:
    critical
    OServer detects a syntax error in the configuration file at line {line}.
    Description of the error is in {detailed_message}.
    Message is also redirected to STDERR.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is terminated and it returns code 1.
    Solution: fix the error in the configuration file at line {line} and restart OServer.
    OSVC-GC-510 Configuration file: {config_file}

    Message type:
    information
    The OServer's configuration file name.
    The message is displayed when log file is already opened whereas message OSVC-CF-510 is redirected to standard output.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues processing with the {config_file} file.
    Solution: none.
    OSVC-PA-80A Cannot load accounting plugin: {plugin name}, {detailed_message}

    Message type:
    error
    The accounting plugin {plugin_name} cannot be loaded due to {detailed_message}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • Invalid plugin's name in the 'oserver_accounting_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PA-80B Invalid accounting plugin {plugin_name}, ({error_reason})

    Message type:
    error
    The plugin's library was loaded but has an invalid format. The accounting plugin {plugin_name} cannot be processed due to {error_reason}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • Plugin is corrupted
    • Invalid plugin version - verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in the 'oserver_accounting_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not reinstall OServer.
    OSVC-PA-80C Invalid accounting plugin {plugin_name}, failed to call

    Message type:
    error
    The plugin's library was loaded but has an invalid format. The accounting plugin {plugin_name} cannot be processed due to {error_reason}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • Plugin is corrupted
    • Invalid plugin version - verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in the 'oserver_accounting_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PA-80D Invalid accounting plugin {plugin_name}, ({error_reason})

    Message type:
    error
    The plugin's library was loaded but has an invalid format. The accounting plugin {plugin_name} cannot be processed due to {error_reason}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • Plugin is corrupted
    • Invalid plugin version - verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in the 'oserver_accounting_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PA-500 Plugin {plugin name} loaded

    Message type:
    information
    The accounting plugin has been loaded.
    Authorization required:Superuser
    Source: OServer
    Result: The accounting plugin loaded.
    Solution: none
    OSVC-PA-80E Accounting plugin {plugin name} failed to call

    Message type:
    error
    The createHandler function does not return a correct value. Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution:
    The most common cause of the errors could be:
    • Plugin is corrupted
    • Verify if the plugin is correct:
      • verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in the 'oserver_accounting_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PA-510 Accounting plugin {plugin_name} received the configuration

    Message type:
    information
    The accounting plugin received the configuration string.
    Authorization required:Superuser
    Source: OServer
    Result: The accounting plugin received the configuration and continues initialization.
    Solution: none
    OSVC-PA-710 Accounting plugin {plugin_name} received invalid configuration

    Message type:
    warning
    The accounting plugin received the configuration string but appears to be invalid.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues
    Solution:
    • For defaultAccountin plugin:
      • verify if the 'oserver_accounting_config' parameter is valid,
      • verify if the user related to the OServer process is privileged to access the path
    OSVC-PS-91A Non-empty parameter oserver_security_config is required

    Message type:
    critical
    The security plugin cannot be loaded.
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: Verify the content of the 'oserver_security_config' configuration parameter.
    OSVC-PS-80A Cannot load security plugin: {plugin name}, {detailed_message}

    Message type:
    error
    The security plugin {plugin_name} cannot be loaded due to {detailed_message}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • Invalid plugin's name in the 'oserver_security_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on a search path, issue the 'ldconfig -p | grep {plugin_name}' command
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PS-80B Invalid security plugin {plugin_name}, ({error_reason})

    Message type:
    error
    The plugin's library was loaded but has an invalid format. The security plugin {plugin_name} cannot be processed due to {error_reason}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • The plugin is corrupted
    • Invalid plugin version - verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in configuration parameter 'oserver_security_config'.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on a search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PS-80C Invalid security plugin {plugin_name}, failed to call

    Message type:
    error
    The plugin's library was loaded but has an invalid format. The security plugin {plugin_name} cannot be processed due to {error_reason}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • Plugin is corrupted
    • Invalid plugin version - verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in configuration parameter 'oserver_security_config'.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PS-80D Invalid security plugin {plugin_name}, ({error_reason})

    Message type:
    error
    The plugin's library was loaded but has an invalid format. The security plugin {plugin_name} cannot be processed due to {error_reason}
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: {error_reason} is related to the dynamic linking error
    The most common cause of the errors could be:
    • Plugin is corrupted
    • Invalid plugin version - verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in the 'oserver_security_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from [/etc/ld.so.conf.d
    To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PS-500 The security plugin {plugin name} loaded

    Message type:
    information
    The security plugin has been loaded successfully.
    . Authorization required:Superuser
    Source: OServer
    Result: Plugin loaded, security continues initialization.
    Solution: none
    OSVC-PS-80E The security plugin {plugin_name} failure, cannot initialize security

    Message type:
    error
    The security initialization procedure returned an empty value.
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1.
    Solution: The most common cause of the errors could be:
    • Plugin is corrupted
    • Invalid plugin version - verify if the library {plugin_name} has the same version as OServer.
      • check the OServer version: 'gpuserver -v',
      • check the library: 'strings lib{plugin_name}.so| grep version:',
      Both should have the same version, if they do not - reinstall OServer.
    • Invalid plugin's name in the 'oserver_security_config' configuration parameter.
    • Library's directory is not specified in the 'LD_LIBRARY_PATH' environment variable.
    • Library's directory is not specified in one of the files from '/etc/ld.so.conf.d/'. To verify if the plugin exists on the search path, issue the command 'ldconfig -p | grep {plugin_name}'
    • If the plugin is missing, verify if the library exists in the 'OSERVER_INSTALLATION_DIRECTORY/lib64' directory and if it does not - reinstall OServer.
    OSVC-PS-510 The security plugin {plugin_name} received the configuration

    Message type:
    information
    The security plugin received the configuration string.
    Authorization required:Superuser
    Source: OServer
    Result: The security plugin received the configuration and the initialization continues.
    Solution: none
    OSVC-PS-710 The security plugin {plugin_name} received invalid configuration

    Message type:
    warning
    The security plugin received the configuration but it appears to be invalid.
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues
    Solution:
    • For Security1 plugin:
      • verify if the 'oserver_security_config' parameter has a valid path to the security database
      • verify if the user related to the OServer process is privileged to access the security database
    OSVC-LR-60A Log {log_file} reopened

    Message type:
    notice
    Log was reopen most likely due to received SIGHUP signal.
    {log_file} is a full path to log file or it's STDOUT.
    Authorization required:Superuser
    Source: OServer
    Result: log file reopened.
    Solution: none
    OSVC-LR-80A Log {log_file} failed to reopen

    Message type:
    error
    Likely OServer received SIGHUP signal and tried to reopen log due to normal operation but the reopen failed or log is redirected to STDOUT.
    Authorization required:Superuser
    Source: OServer
    Result: reopen of the log failed.
    Solution: Verify if the path to OServer's log is accessible.
    OSVC-O1-81A Cannot open output file for monitor1 offload: {filename}

    Message type:
    error
    OServer cannot open the output file to offload the data from Monitor1.
    Authorization required:Superuser
    Source: OServer
    Result: Monitor1 will not be able to offload the data into the file, the 'OSVC-O1-81A' message will be displayed within every offload request.
    Solution:
    • Verify if the '{oserver_datafiles_path}/monitor1' directory exists
    • Verify if the user related to the OServer's process has the write access in the '{oserver_datafiles_path}/monitor1' directory.
    OSVC-O1-51A Monitor1 data offloaded to file {filename}

    Message type:
    information
    Monitor1 successfully offloaded data to file {filename}.
    Authorization required:Superuser
    Source: OServer
    Result: Monitor1 data offloaded.
    Solution: none
    OSVC-O1-81B Failed to offload monitor1 to file : {filename}

    Message type:
    error
    OServer was not able to offload the data to {filename}.
    Authorization required:Superuser
    Source: OServer
    Result: Monitor1 data are not offloaded.
    Solution:
    • Examine the OServer's log.
    • Verify if the '{oserver_datafiles_path}/monitor1' directory exists
    • Verify if the user related to the OServer's process has the write access in the '{oserver_datafiles_path}/monitor1' directory.
    OSVC-IC-70B Parameter 'oserver_rest_bind' not found in configuration file, default used: {oserver_rest_bind}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: Default value 127.0.0.1:8080 has been used.
    Solution: Specify the 'oserver_rest_bind' parameter in the configuration file.
    OSVC-IC-70C Parameter 'oserver_security_plugin' not found in configuration file, default used: {oserver_security_plugin}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: Default value 'security1' has been used.
    Solution: Specify the 'oserver_security_plugin' parameter in the configuration file.
    OSVC-IC-80D Parameter 'oserver_security_config' not found in configuration file

    Message type:
    error
    Authorization required:Superuser
    Source: OServer
    Result: This parameter is required to continue OServer's initialization.
    Solution: Specify the 'oserver_security_config' parameter in the configuration file.
    OSVC-IC-70D Parameter 'oserver_accounting_plugin' not found in configuration file, default used: {oserver_accounting_plugin}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: Default value 'defaultAccounting' has been used.
    Solution: Specify the 'oserver_accounting_plugin' parameter in the configuration file.
    OSVC-IC-71C Parameter 'oserver_accounting_config' not found in configuration file, default used

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: An empty string has been used, the account information will be redirected to the OServer's log with the [DACC-WA-50B] message.
    Solution: Specify the 'oserver_accounting_config' parameter in the configuration file.
    OSVC-IC-80E Cannot find infrastructure authorization token

    Message type:
    error
    Authorization required:Superuser
    Source: OServer
    Result: This parameter is required to continue OServer's initialization.
    Solution: Specify infrastructure token 'auth_token' in the configuration file.
    OSVC-IC-70F Parameter 'oserver_max_gpu_per_user' not found in configuration file, default used: {oserver_max_gpu_per_user}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: The default value '5' has been used.
    Solution: Specify the 'oserver_max_gpu_per_user' parameter in the configuration file.
    OSVC-IC-70G Parameter 'oserver_max_gpu_per_user_per_ip' not found in configuration file, default used: {oserver_max_gpu_per_user_per_ip}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: The default value '5' has been used.
    Solution: Specify the 'oserver_max_gpu_per_user_per_ip' parameter in the configuration file.
    OSVC-IC-70H Parameter 'oserver_max_users_per_gpu' not found in configuration file, default used: {oserver_max_users_per_gpu}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: The default value '5' has been used.
    Solution: Specify the 'oserver_max_users_per_gpu' parameter in the configuration file..
    OSVC-IC-70I Parameter 'port' not found in the configuration file, the default used: {oserver_oserver_bind_port}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: The default value '9393' has been used.
    Solution: Specify the 'port' parameter in the configuration file..
    OSVC-IC-71I Configuration parameter 'oserver_gpu_count_info' is invalid, default value used: no

    Message type:
    warning
    Config parameter 'oserver_gpu_count_info' has to be 'yes' or 'no' only.
    Authorization required:Superuser
    Source: OServer
    Result:
    • default value 'no' used
    • OServer start continue
    Solution: Set desired 'oserver_gpu_count_info' parameter according to manual
    OSVC-IC-75J Parameter 'oserver_ssl_cert_path' not found in configuration file, default used: {oserver_ssl_cert_path}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: This parameter is required to continue OServer's initialization.
    Solution: Specify the 'oserver_ssl_cert_path' parameter in the configuration file when the SSL communication is necessary.
    OSVC-IC-74K Parameter 'oserver_webfiles_path' not found in configuration file

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: Default value - empty string.
    Solution: Specify the 'oserver_webfiles_path' parameter in the configuration file when the web user interface is necessary.
    OSVC-IC-74L Parameter 'oserver_installfiles_path' not found in configuration file

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: Default value - empty string.
    Solution: Specify the 'oserver_installfiles_path' parameter in the configuration file.
    OSVC-IC-74N Parameter 'oserver_allocation_option' not found in configuration file, 'shared' is used

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: Default value used - 'shared'.
    Solution: Specify the 'oserver_allocation_option' parameter in the configuration file.
    OSVC-IC-74M Configuration parameter 'oserver_allocation_option' is invalid, default value used: no

    Message type:
    warning
    Config parameter 'oserver_allocation_option' has to be 'free' or 'shared' only.
    Authorization required:Superuser
    Source: OServer
    Result:
    • default value 'no' used
    • OServer start continue
    Solution: Set desired 'oserver_allocation_option' parameter according to manual
    OSVC-IC-84R Parameter 'oserver_datafiles_path' not found in configuration file

    Message type:
    error
    Authorization required:Superuser
    Source: OServer
    Result: This parameter is required to continue OServer's initialization.
    Solution: Specify the 'oserver_datafiles_path' parameter in the configuration file when web interface is to be provided.
    OSVC-IC-60S Parameter 'oserver_discovery_port' not found in configuration file, default used: {oserver_discovery_port}

    Message type:
    notice
    Authorization required:Superuser
    Version: 1.5+
    Source: OServer
    Result: The default value 17400 has been used.
    Solution: Specify the 'oserver_discovery_port' parameter in the configuration file.
    OSVC-IC-60U Parameter 'oserver_discovery_interval' not found in configuration file, default used: {oserver_discovery_interval}

    Message type:
    notice
    Authorization required:Superuser
    Version: 1.5+
    Source: OServer
    Result: The default value 4000 has been used.
    Solution: Specify the 'oserver_discovery_interval' parameter in the configuration file.
    OSVC-IC-50C oserver_rest_bind = {oserver_rest_bind}

    Message type:
    information
    Display the configuration value of the 'oserver_rest_bind' parameter
    . Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50D oserver_security_plugin = {oserver_security_plugin}

    Message type:
    information
    Display the configuration value of the 'oserver_security_plugin' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50W oserver_security_config = {oserver_security_config}

    Message type:
    information
    Display the configuration value of the 'oserver_security_config' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50S oserver_accounting_plugin = {oserver_accounting_plugin}

    Message type:
    information
    Display the configuration value of the 'oserver_accounting_plugin' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50Q oserver_accounting_config = {oserver_accounting_config}

    Message type:
    information
    Display the configuration value of the 'oserver_accounting_config' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50E oserver_max_gpu_per_user = {oserver_max_gpu_per_user}

    Message type:
    information
    Display the configuration value of the 'oserver_max_gpu_per_user' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continuess.
    Solution: none
    OSVC-IC-50F oserver_max_gpu_per_user_per_ip = {oserver_max_gpu_per_user_per_ip}

    Message type:
    information
    Display the configuration value of the 'oserver_max_gpu_per_user_per_ip' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50G oserver_max_users_per_gpu = {oserver_max_users_per_gpu}

    Message type:
    information
    Display the configuration value of the 'oserver_max_users_per_gpu' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50H Infrastructure token presented

    Message type:
    information
    Infrastructure authorization token has been specified.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50I gpu_count_info = {gpu_count_info}

    Message type:
    information
    Display the configuration value of the {gpu_count_info} parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50K oserver_webfiles_path = {oserver_webfiles_path}

    Message type:
    information
    Display the configuration value of the 'oserver_webfiles_path' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50L oserver_installfiles_path = {oserver_installfiles_path}

    Message type:
    information
    Display the configuration value of the 'oserver_installfiles_path' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50M oserver_allocation_option = {oserver_allocation_option}

    Message type:
    information
    Display the configuration value of the 'oserver_allocation_option' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50R oserver_datafiles_path = {oserver_datafiles_path}

    Message type:
    information
    Display the configuration value of the 'oserver_datafiles_path' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50T oserver_discovery_port = {oserver_discovery_port}

    Message type:
    information
    Display the configuration value of the 'oserver_discovery_port' parameter.
    Authorization required:Superuser
    Version: 1.4+
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-50U oserver_discovery_interval = {oserver_discovery_interval}

    Message type:
    information
    Display the configuration value of the 'oserver_discovery_interval' parameter.
    Authorization required:Superuser
    Version: 1.4+
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-IC-90F Unexpected exception occurred while initializing OServer

    Message type:
    critical
    Authorization required:Superuser
    Source: OServer
    Result: OServer is terminated.
    Solution:
    OSVC-SL-70A Parameter 'oserver_log_path ' setting not found in configuration file, log is redirected to STDOUT

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: log messages are redirect to STDOUT
    Solution: Specify the 'oserver_log_path' parameter in the configuration file.
    OSVC-SL-70B Parameter 'oserver_log_level' not found in configuration file, default used: {oserver_log_level}

    Message type:
    warning
    Authorization required:Superuser
    Source: OServer
    Result: 'INFO' is used.
    Solution: Specify the 'oserver_log_level' parameter in the configuration file.
    OSVC-SL-68A Invalid log level, 'TRACE' will be used instead

    Message type:
    notice
    OServer will use default value 'TRACE' for 'oserver_log_level'. The value from configuration file is invalid.
    Source: OServer
    Result: OServer will continue logging with 'TRACE' level'.
    Solution: Value of parameter 'oserver_log_level' must be on of 'TRACE', 'DEBUG', 'INFO', 'NOTICE', 'WARNING', 'ERROR', 'CRITICAL'.
    OSVC-SL-71A Cannot open output file {oserver_log_path}, log redirect to STDOUT

    Message type:
    warning
    OServer cannot open log file {oserver_log_path}, logging will will be redirected to STDOUT.
    Authorization required:Superuser
    Source: OServer
    Result: log messages are redirected to STDOUT.
    Solution:
    • check if {oserver_log_path} is correct path and file is accessible.
    OSVC-SL-50A oserver_log_path = {oserver_log_path}

    Message type:
    information
    Display the configuration value of the 'oserver_log_path' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: log messages are redirected to {oserver_log_path}.
    Solution: none
    OSVC-SL-50B oserver_log_level = {oserver_log_level}
    The log has the following severity order: TRACE DEBUG INFO NOTICE ERROR CRITICAL
    Message type:
    information
    Display the configuration value of the 'oserver_log_level' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Messages with the specified {oserver_log_level} log level and higher severity will be displayed.
    Solution: none
    OSVC-SL-50C Logging started

    Message type:
    information
    Logging has been started with the severity specified by 'oserver_log_level' parameter and it is redirected to the log file specified by 'oserver_log_path' or to STDOUT. Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none
    OSVC-SL-960 Unknown exception occurred while prepare logging, OServer is being terminated

    Message type:
    critical
    Authorization required:Superuser
    Source: OServer
    Result: OServer starts terminating and it will return code 1
    Solution: Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-OS-960 Cannot find infrastructure token, OServer is being terminated

    Message type:
    critical
    The configuration file does not contain an infrastructure token. The token is required due to intercommunication between OServer and GPUServers.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Specify the 'oserver_accounting_plugin' parameter in the configuration file.
    OSVC-OS-96A Path defined in parameter oserver_datafiles_path is not a directory

    Message type:
    critical
    Path defined by the 'oserver_datafiles_path' configuration parameters must be a directory.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Check if the specified path is a directory. create new directory or change path to existing one.
    OSVC-OS-96E Path defined in parameter 'oserver_datafiles_path does' not exist

    Message type:
    critical
    The directory defined by the 'oserver_datafiles_path' configuration parameter must exist.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Create the specified directory or change the path to an existing one.
    OSVC-OS-96B Path defined in parameter 'oserver_webfiles_path' is not a directory

    Message type:
    critical
    Path defined by the 'oserver_webfiles_path' configuration parameters must be a directory.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Check if the specified path is a directory. create new directory or change path to existing one.
    OSVC-OS-96F Path defined in parameter 'oserver_webfiles_path' does not exist

    Message type:
    critical
    The directory defined by the 'oserver_webfiles_path' configuration parameter must exist.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Create the specified directory or change the path to an existing one.
    OSVC-OS-96C Path defined in parameter 'oserver_installfiles_path' is not a directory

    Message type:
    critical
    Path defined by the 'oserver_installfiles_path' configuration parameters must be a directory.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Check if the specified path is a directory. create new directory or change path to existing one.
    OSVC-OS-96G Path defined in parameter 'oserver_installfiles_path' does not exist

    Message type:
    critical
    The directory defined by the 'oserver_installfiles_path' configuration parameter must exist.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Create the specified directory or change the path to an existing one.
    OSVC-OS-31I Configuration parameter 'oserver_ssl_cert_path' is empty

    Message type:
    debug
    Authorization required:Superuser
    Source: OServer
    Result: OServer continues processing.
    Solution: Create specify directory or change path to existing one.
    OSVC-OS-91I SSL port was specified in 'oserver_rest_bind' but parameter 'oserver_ssl_cert_path' is empty

    Message type:
    critical
    The RESTful server to communicate over SSL required valid format of the SSL certificate.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Specify the SSL certificate in the 'oserver_ssl_cert_path' parameter.
    OSVC-OS-93I Cannot open SSL certificate

    Message type:
    critical
    SSL certificate was specified but the file cannot be opened.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Specify valid SSL certificate in parameter 'oserver_ssl_cert_path'.
    OSVC-OS-52I 'oserver_ssl_cert_path' = {oserver_ssl_cert_path}

    Message type:
    information
    The message displays the configuration value of the 'oserver_ssl_cert_path' parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continue.
    Solution: none
    OSVC-OS-70T Port specified by parameter 'oserver_discovery_port' not in range [1..65536], default value used: {oserver_discovery_port}

    Message type:
    warning
    Port number of out of the range [1..65536].
    Authorization required:Superuser
    Version: 1.4+
    Source: OServer
    Result: OServer continues processing with default value.
    Solution: Port numbers must be in range from 1 to 65536. Ports numbers 1 to 1024 are reserved for privileged services and designated as well-known ports and it is not recommended to use this range. Default discovery port for OServer: 17400
    Reference list of common known ports: https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
    OSVC-OS-70U Interval specified by parameter 'oserver_discovery_interval' not in range [1000..15000], default value used: {oserver_discovery_interval}

    Message type:
    warning
    Discovering interval must be 1 second at least and maximum interval between broadcasting is 15 seconds.
    oserver_discovery_interval = 0 discovery is disabled.
    Authorization required:Superuser
    Version: 1.4+
    Source: OServer
    Result: OServer continues processing with default value.
    Solution: OServer broadcasts its presents be sending messages to all computers in local network. The value less than 1sec abuses network resources. More than 15 seconds makes the discovering protocol useless.
    OSVC-OS-60U Discovery protocol is disabled

    Message type:
    notice
    Parameter 'oserver_discovery_interval' equal 0 disables discovery protocol.
    Authorization required:Superuser
    Version: 1.4+
    Source: OServer
    Result: OServer continues processing without discovery protocol.
    Solution: Specify value in range [1000..15000] to enable discovery protocol.
    OSVC-CD-961 Unexpected database exception occurred while connecting database, {detailed_message}

    Message type:
    critical
    An unexpected exception occurred while connecting the database.
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    User message: none
    Solution: Examine the OServer's log, when issue cannot be solved please contact support.
    OSVC-IC-960 Unexpected exception occurred, cannot start OServer

    Message type:
    critical
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution: Examine the OServer's log, when the issue cannot be solved please contact support.
    OSVC-IC-970 Cannot load security plugin:{plugin_name}

    Message type:
    critical
    Cannot load the security plugin specified by the 'oserver_security_plugin' configuration parameter. The security plugin is required to continue the OServer initialization.
    Plugin is a system's dynamic library, the full name of the file is 'lib{plugin_name}.so'
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution:
    • Check if {plugin_name} is correct and the 'lib{plugin_name}.so' library exists.
    • Check if the environment variable 'LD_LIBRARY_PATH' exists and contains OServer's library 'OSERVER_INSTALLATION_DIRECTORY/lib64' or check if the library is on the global library search path. Issue the 'ldconfig -p | grep {plugin_name}' command, note that the command can require system root privileges.
    • Check if the library version is the same as OServer, issue the following commands and compare the versions:
      • 'oserver -v'
      • 'strings lib{plugin_name}.so | grep version:'
    OSVC-IC-99A Infrastructure token is invalid

    Message type:
    critical
    OServer cannot continue initialization due to invalid infrastructure token.
    Authorization required:Superuser
    Source: OServer
    Result: OServer will terminate.
    Solution:
    • Check if the infrastructure token is valid.
    • If the token was generated you can use a different superuser's token as the infrastructure token.
    • Restore the previous infrastructure token value, you can acquire the valid token from:
      • the GPUServers' configuration files.
      • From Clients, if the superuser was logged:
        • on Windows operating system from the file: 'LOCALAPPDATA%.gpubox',
        • on Linux operating system from the file: '$HOME/.gpubox'.
      • From the Security1's database by the sqlite command line.
    • If the security database content is not important you can always recreate it or simply apply a new database name in the 'oserver_security_config' configuration parameter and restart OServer. Content of the old database can be copied with the sqlite utility.
    OSVC-IC-69A Infrastructure token belongs to userid: {userid}, username: {username}

    Message type:
    notice
    At the initialization, OServer checks the infrastructure credentials. The infrastructure token must be a valid token in the security database. Successfully installed OServer and GPUServer has the same default infrastructure token as 'gpubox' user.
    Authorization required:Superuser
    Source: OServer
    Result: OServer will continue processing with {userid} credentials.
    Solution: none
    OSVC-IC-98A Cannot load accounting plugin:{plugin_name}

    Message type:
    critical
    Cannot load the accounting plugin specified by the 'oserver_accounting_plugin' configuration parameter. An accounting plugin is required to continue the OServer initialization.
    Plugin is a system's dynamic library, the full name of the file is 'lib{plugin_name}.so'
    Authorization required:Superuser
    Source: OServer
    Result: OServer is begin terminated and it will return code 1.
    Solution:
    • Check if {plugin_name} is correct and the 'lib{plugin_name}.so' library exists.
    • Check if the environment variable 'LD_LIBRARY_PATH' exists and contains the OServer's library 'OSERVER_INSTALLATION_DIRECTORY/lib64' or check if the library is on the global library search path. Issue the 'ldconfig -p | grep {plugin_name}' command, note that the command can require system root privileges.
    • Check if the library version is the same as OServer, issue the following commands and compare the versions:
      • 'oserver -v'
      • 'strings lib{plugin_name}.so | grep version:'
    OSVC-OS-600 OServer is ready to accept connections

    Message type:
    notice
    At this stage OServer is fully initialized and ready to accept connections.
    Authorization required:Superuser
    Source: OServer
    Result: Processing continues.
    Solution: none.
    OSVC-DE-689 Oserver is shutting down, please wait

    Message type:
    notice
    OServer just started sequence of shutting down. This may take a few seconds.
    Authorization required:Superuser
    Source: OServer
    Result: OServer start shutting down sequence.
    Solution: none
    OSRV-OH-66D [{pid}] OServer stopped

    Message type:
    notice
    OServer has been stopped.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: OServer is about to stop and it returns code 0.
    Solution: none
    OSVC-M1-80A Cannot create 'monitor1' directory in {oserver_datafiles_path}

    Message type:
    error
    Monitor1 to offload data needs a directory and OServer is not able to create the 'monitor1' directory in a location pointed by the {oserver_datafiles_path} parameter.
    Authorization required:Superuser
    Source: OServer
    Result: Monitor1 won't be able to offload data into file, the 'DACC-O1-81A' message will be displayed within every offload request.
    Solution:
    • Examine the OServer's log.
    • Check is user related to OServer's process can create directory in {oserver_datafiles_path} and the path is accessible.
    OSVC-M1-80B 'monitor1' in path {oserver_datafiles_path} is not a directory

    Message type:
    error
    'monitor1' is expected to be a directory but it turns out to be a file.
    Authorization required:Superuser
    Source: OServer
    Result: Monitor1 will not be able to offload the data into the file, the 'DACC-O1-81A' message will be displayed within every offload request.
    Solution: Verify if the '{oserver_datafiles_path}/monitor1' is file or directory. If this is a file delete or rename.
    OSVC-M1-50B Directory {oserver_datafiles_path}monitor1 for Monitor1 created

    Message type:
    information
    OServer creates the '{oserver_datafiles_path}/monitor1' directory to offload the data from Monitor1.
    Authorization required:Superuser
    Source: OServer
    Result: Monitor1 should be able to offload data.
    Solution: none
    OSVC-M1-50A Monitor1 started

    Message type:
    information
    Monitor1 activity started and the snapshoot of the data is taken every 10 seconds.
    Authorization required:Superuser
    Source: OServer
    Result: Monitor1 is up and running.
    Solution: none
    OSVC-DT-81A Cannot retrieve information about ip interfaces, message: {detailed_message}

    Message type:
    error
    OServer tried to analyze parameter 'oserver_rest_bind' and host's ip interfaces but failed due to {detailed_message}.
    Authorization required:Superuser
    Version: 1.4+ Source: OServer
    Result: OServer will not use discovery protool on all ip interfaces.
    Solution: {detailed_message} should explains the cause of the error.
    The most common cause of the errors could be:
    • Error: Host not found (authoritative)
      The DNS servers which were queried along the way did not respond within the time out. The 'host not found' error comes not because it was not in the DNS directory but because some server didn't respond. The error "host not found" is thus non authoritative.
    • Check 'oserver_rest_bind' parameter if it is correct./n
    • User related to OServer does not have enough privileges to read infromation about ip interfaces.
    • Firewall mechanism prevent of such a read.
    • Windows: Disable firewall/virus protection software and restart OServer to verify if this is the cuase.
    • Windows: Add the rule for oserver.exe process and ip address to firewal.
    • Linux: Add rule to iptables for example: # iptables -A OUTPUT -p udp --dport {port} -m state --state NEW,ESTABLISHED -j ACCEPT
    • If the parameter 'oserver_rest_bind' has 0.0.0.0 i.e. OServer is bound to all ip interfaces try to change to single one.
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-DT-81B Error while preparing discovery message: {detailed_message}

    Message type:
    error
    OServer cought exception while preparing message to broadcast.
    Authorization required:Superuser
    Version: 1.4+ Source: OServer
    Result: OServer will not use discovery protool on all ip interfaces.
    Solution: {detailed_message} should explains the cause of the error.
    OSVC-OR-960 Cannot start RESTful server..

    Message type:
    critical
    OServer cannot start RESTful server
    Authorization required:Superuser
    Source: OServer
    Result: OServer is terminated and it returns code 1.
    Solution: Examine the 'OSVC-MN-84A' message in the OServer's log, if you cannot solve the issue, please contact support.
    OSVC-DT-80B Cannot send UDP broadcast on interface: {ip_interface} and port: {port}, message: {detailed_message}

    Message type:
    error
    OServer is already bound to specified ip interface and port but cannot send the UDP broadcast datagram.
    The cause of the errore is specified in {detailed_message}.
    Authorization required:Superuser
    Version: 1.4+ Source: OServer
    Result: OServer will not use discovery protool on specified ip interface.
    Solution: {detailed_message} should explains the cause of the error.
    The most common cause of the errors could be:
    • Check if the ip interface and port are correct.
    • User related to OServer does not have enough privileges to bind to specific ip address and port.
    • Firewall mechanism prevent of such a bind.
    • Windows: Disable firewall/virus protection software and restart OServer to verify if this is the cuase.
    • Windows: Add the rule for oserver.exe process and ip address to firewal.
    • Linux: Add rule to iptables for example: # iptables -A OUTPUT -p udp --dport {port} -m state --state NEW,ESTABLISHED -j ACCEPT
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    OSVC-DT-80A Cannot start discovery protocol on interface: {ip_interface} and port: {port}, message: {detailed_message}

    Message type:
    error
    OServer cannot bind to port specified by (oserver_discovery_port} parameter. OServer uses UDP boradcast protocol.
    OServer tries to bind service UDP broadcast on ip interface {ip_interface} and port {port}.
    The cause of the errore is specified in {detailed_message}.
    Authorization required:Superuser
    Version: 1.4+ Source: OServer
    Result: OServer will not use discovery protool on specified ip interface.
    Solution: {detailed_message} should explains the cause of the error.
    The most common cause of the errors could be:
    • Check if the ip interface and port are correct.
    • User related to OServer does not have enough privileges to bind to specific ip address and port.
    • Firewall mechanism prevent of such a bind.
    • Windows: Disable firewall/virus protection software and restart OServer to verify if this is the cuase.
    • Windows: Add the rule for oserver.exe process and ip address to firewal.
    • Linux: Add rule to iptables for example: # iptables -A OUTPUT -p udp --dport {port} -m state --state NEW,ESTABLISHED -j ACCEPT
    • Examine the previous OServer's messages, if you cannot solve the issue please contact support.
    ROSC-AG-70A [{session_id}] Content length not set, GPU allocation failed

    Message type:
    warning
    User requested the GPU allocation. The HTTP header must contain Content-Length and body must contain data.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 411 Length Required
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-AG-70B [{session_id}] Missing content, GPU allocation failed

    Message type:
    warning
    User requested the GPU allocation, field 'Content-Length' in header exists but it is too small to contain proper data.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-AG-82P [{session_id}] Failed to parse input data, GPU allocation failed

    Message type:
    error
    OServer detected a syntax error in the input data. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Failed to parse input data, GPU allocation failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-AG-730 [{session_id}] GPU allocation failed

    Message type:
    warning
    Superuser requested the GPU allocation but the request failed due to possible database issue.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Search the messages with the DBHC-AG or DBHD-AG prefix to find the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-AG-800 [{session_id}] Unexpected exception occurred while allocating GPU

    Message type:
    error
    User requested the GPU allocation but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while allocating GPU
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-LG-71A [{session_id}] Failed to retrieve list of allocated GPUs, {error_code}

    Message type:
    warning
    User requested the list of allocated GPUs but the request failed due to database issue.
    {error_code} for analysis purposes only.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-GU or DBHD-GU prefix for the cause of the issue.
    It also shows that user does not have allocated GPUs yet.
    If the issue cannot be solved please contact support
    ROSC-LG-81S [{session_id}] Invalid output data

    Message type:
    error
    User requested the list of GPUs allocated to him but the data received from database does not seems to be correct.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-GU or DBHD-GU prefix for the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-LG-800 [{session_id}] Unexpected exception occurred while retrieving list of allocated GPU

    Message type:
    error
    User requested the list of allocated GPUs but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving list of allocated GPU
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-AX-82A [{session_id}] Unexpected exception occurred while authorizing user {userid} to use GPU

    Message type:
    error
    User has requested to use GPU device but an unexpected exception has occurred while authorizing.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while authorizing user
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-AX-80A [{session_id}] Invalid group for user {userid}, {userName}

    Message type:
    error
    During the request authorization, the security module returned an invalid group ID.
    The group ID should be:
    • 0 for superuser,
    • 1 for regular users.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 401 Unauthorized
    User message: none
    Solution:
    • Verify the group ID by sending the agpubox u -l -u={userid} command. Change the group ID to a proper one with the agpubox u -m -u={userid} -g={0|1} command.
    • The most possible reason of occurence of this error is a problem in the security module. The Security1 module accepts only 0 and 1 as the group ID. Verify the group by sending the agpubox u -l -u={userid} command or attach to security database via sqlite3 interface or similar.
    ROSC-AX-51A [{session_id}] Access granted to superuser {username}, {userid}

    Message type:
    info
    Based on token, requesting user was authorized as superuser.
    Authorization required:Superuser
    Source: OServer
    Result: request continue
    HTTP status code: depends on request
    User message: none
    Solution:
    ROSC-AX-51B [{session_id}] Access granted to {username}, {userid}

    Message type:
    info
    Based on token, requesting user was authorized as regular user.
    Authorization required:Regular user
    Source: OServer
    Result: request continue
    HTTP status code: depends on request
    User message: none
    Solution:
    ROSC-AX-700 [{session_id}] Access revoked - illegal token from {request_method}:{remote_ip}:{remote_port}

    Message type:
    warning
    The given authorization token was not accepted - neither as a regular user nor a superuser.
    At sixth invalid token attempt user's account is disabled.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 401 Unauthorized
    User message: none
    Solution: User must provide valid token.
    • User could have generated a new token but did not saved it in Client's configuration file. To retrieve the proper token user has to log in again and save the token via the gpubox token command.
    • Too many failed attempts of accessing the GPUBox infrastructure in short period of time can indicate on trying to break the GPUBox infrastructure's security by unauthorized users.
    ROSC-HH-500 [{session_id}] New session [{thread_id}]: {request_method}:{connection_type}://{oserver_host}/{resource}{query_string}, IP: {remote_ip_address}:{remote port}

    Message type:
    information
    OServer received a new request with the following parameters:
    • {session_id}: all of the related messages are preceded with the same session id. Request ID is incremented within every new request
    • {thread_id}: in some cases, especially those related to the database operations, thread ID is useful for determining the relation between the messages and finding the cause of the issue.
    • {request_method}: HTTP method.
    • {connection_type}: http or https.
    • {oserver_host}: OServer's interface where request arrive to.
    • {resource}: defines resource and actions that OServer should take. It also has arguments for actions.
    • {query_string}: if there is any. it is an URL string after a question mark
    • {remote_ip_address}: remote IP address from where the request comes.
    • {remote port}: the remote port number from where the request comes.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: none
    Result: OServer will check the user's credentials and start proceeding the request.
    HTTP status code: depends on request
    Solution: none
    ROSC-CW-55X [{session_id}] HTTP Status Code {HTTP_rc}

    Message type:
    info
    Shows:
    • redirection 3xx
    • client's error 4xx
    • server's error 5xx
    HTTP code at the end of the request.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: in most cases request is finished
    HTTP status code: 300 or greater
    User message: none
    Solution: none
    ROSC-CW-35X [{session_id}] HTTP Status Code {HTTP_rc}

    Message type:
    debug
    Shows:
    • informational 1xx
    • success 2xx
    HTTP code at the end of the request.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: in most cases request is finished
    HTTP status code: 200 or less
    User message: none
    Solution: none
    ROSC-GC-700 [{session_id}] Problem detected while getting configuration

    Message type:
    warning
    User requested configuration of allocated GPUs but it failed due to the database operations.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-GC or DBHD-GC prefix for the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-GC-81S [{session_id}] Invalid output data

    Message type:
    error
    Superuser requested configuration of allocated GPUs but the data received from database does not seems to be correct.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-LG or DBHD-LG prefix for the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-GC-80E [{session_id}] Unexpected exception occurred while retrieving configuration of allocated GPUs

    Message type:
    error
    User requested the list of allocated GPUs but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving configuration of allocated GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-DU-82A [{session_id}] Empty user passed while deleting user

    Message type:
    error
    Superuser requested to delete user but the request contains invalid input data with empty userid.
    Authorization required:Superuser
    Source: OServer
    User message: Empty user passed while deleting user
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    1. Verify origin of request if it comes from authorized GPUBox infrastructure elements.
    2. Specify userid in URI.
    3. Examine previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-DU-72B User {userid} cannot be deleted, user has allocated GPUs

    Message type:
    warning
    User cannot be deleted while there are still some GPUs allocated to the account.
    Authorization required:Superuser
    Source: OServer
    User message: User has allocated GPUs
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • User has to drop the allocated GPUs.
    • Administrator can drop the user's allocated GPUs.
    ROSC-DU-82B [{session_id}] Cannot delete user {userid}

    Message type:
    error
    Superuser requested to delete user but an error occurred in the security module.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    • Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-D1-82A [{session_id}] Invalid input data to delete Monitor1

    Message type:
    error
    Superuser requested to delete data from Monitor1 but the input query is empty.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: Empty request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-D1-82B [{session_id}] Invalid parameter value to delete Monitor1 data

    Message type:
    error
    Superuser requested to delete data from Monitor1 but the parameter has invalid value.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Invalid parameter's value
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-D1-32A [{session_id}] Zero records deleted from Monitor1

    Message type:
    debug
    Superuser requested to delete data from Monitor1 and zero records were deleted.
    Authorization required:Superuser
    Source: OServer
    Result: request success
    HTTP status code: 204 No Content
    User message: 0 records deleted
    Solution: none
    ROSC-D1-32B [{session_id}] {n} records deleted from Monitor1

    Message type:
    debug
    Superuser requested to delete data from Monitor1 and {n} records were deleted.
    Authorization required:Superuser
    Source: OServer
    Result: request success
    HTTP status code: 200 OK
    User message: {n} records deleted
    Solution: none
    ROSC-D1-800 [{session_id}] Unexpected exception occurred while deleting Monitor1 data

    Message type:
    error
    User requested to retrieve data from Monitor1 but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while deleting Monitor1 data
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-DW-82P [{session_id}] Failed to parse input data, delete webcache for user {userid} failed

    Message type:
    error
    OServer detected a syntax error in the input data. Received data has incorrect format or it is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Failed to parse input data, delete webcache failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-DW-72A [{session_id}] Input data does not have 'key' statement, delete webcache failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'key' statement.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'key' statement, delete webcache failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-DW-800 [{session_id}] Unexpected exception occurred while deleting webcache

    Message type:
    error
    User requested to delete data in webcache but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving webcache
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-GD-700 [{session_id}] Invalid GPU ID {invalid_gpu_id}

    Message type:
    warning
    User requested the GPU drop but gave an invalid GPU ID. GPU ID must be an unsigned integer.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: none
    Solution: Likely user entered invalid number. Verify origin of request.
    ROSC-GD-62A [{session_id}] User {userid} has still active processes and cannot drop GPU

    Message type:
    notice
    User tried to drop GPUs but still have active processes
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Cannot drop, active processes are running
    Solution: To drop the GPUs, user has to finish the processes first.
    ROSC-GD-710 [{session_id}] Drop of GPUs failed

    Message type:
    warning
    User requested the GPUs drop but the drop failed.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. For the detailed description of the issue trace down the messages with the following prefixes:
    • DBHC-DI
    • DBHD-DI
    • DBHC-DT
    • DBHD-DT
    ROSC-GD-510 [{session_id}] GPUs dropped

    Message type:
    information
    All of the specified GPUs have been dropped
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 200 OK
    User message: Inherited, check the previous messages with the same request id
    Solution: none
    ROSC-GD-800 [{session_id}] Unexpected exception occurred while retrieving configuration of allocated GPUs

    Message type:
    error
    User requested the GPUs drop but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while dropping GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-DS-700 [{session_id}] Invalid query string {query_string} in URI {uri}

    Message type:
    warning
    User requested the drop of a set of GPUs but the passed string has invalid format in URI.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Query string must be in the following format:
    id=a1,a2,a3,...
    where 'a1' is single GPU id or a range of GPUs i.e. id1-id2.
    ROSC-GD-62B [{session_id}] User {userid} has still active processes and cannot drop GPU

    Message type:
    notice
    User tried to drop GPUs but still have active processes
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Cannot drop, active processes are running
    Solution: To drop the GPUs, user has to finish the processes first.
    ROSC-DS-710 [{session_id}] Invalid GPU ID {invalid_gpu_id}

    Message type:
    warning
    User requested the drop of a set of GPUs but one of the ID is invalid. GPU ID must be an unsigned integer.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed, OServer will try to drop rest of requested GPUs if any
    HTTP status code: none
    User message: Invalid GPU id
    User will receive the message about which GPUs are dropped and which GPUs has failed to drop.
    Solution: Likely user entered invalid number. Verify origin of request.
    ROSC-DS-650 [{session_id}] GPU: {gpu_id} cannot be dropped

    Message type:
    notice
    User requested the drop of a set of GPUs but drop of one of the GPUs failed.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: Drop of this GPU failed, OServer will try to drop rest of requested GPUs if any
    HTTP status code: none
    User message: Invalid GPU id
    User will receive message about which GPUs are dropped and which of the drops failed.
    Solution: Examine the previous related messages with the same request id. For the detailed description of the issue trace down the messages with the following prefixes:
    • DBHC-DI
    • DBHD-DI
    ROSC-DS-50A [{session_id}] GPUs have been dropped: {gpus_id}

    Message type:
    information
    User requested the drop of a set of GPUs and at least one GPU was dropped.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: At least one GPU dropped.
    HTTP status code: none
    User message:
    User will receive message about which GPUs are dropped and which of the drops failed.
    Solution: if all of the GPUs are not dropped, verify user's input and examine the previous related messages with the same request id. For the detailed description of the issue trace down ROSC-DS-50A the messages with the following prefixes:
    • DBHC-DI
    • DBHD-DI
    ROSC-DS-60B [{session_id}] GPUs have not been dropped: {gpus_id}

    Message type:
    notice
    User requested the drop of a set of GPUs and all of them have not been dropped.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: none of the GPUs have been dropped.
    HTTP status code: none
    User message:
    User will receive message about which GPUs are not dropped.
    Solution: verify user's input and examine the previous related messages with the same request id. For the detailed description of the issue trace down ROSC-DS-50A the messages with the following prefixes:
    • DBHC-DI
    • DBHD-DI
    ROSC-DS-800 [{session_id}] Unexpected exception occurred while dropping set of GPUs

    Message type:
    error
    User requested the drop of a set of GPUs but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while dropping set of GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-DD-700 [{session_id}] Invalid GPU ID {invalid_gpu_id}

    Message type:
    warning
    Superuser requested removing the GPU device from the GPUBox infrastructure but the ID is invalid.
    Global GPU device ID must be an unsigned integer.
    Authorization required:Superuser
    Source: OServer
    Result: request failed, OServer will try to drop rest of requested GPUs if any
    HTTP status code: 405 Method Not Allowed
    User message: Invalid GPU device ID
    Solution: Likely invalid GPU device specified. Verify origin of request.
    ROSC-DD-710 [{session_id}] GPU device {gpu_device_id} drop failed

    Message type:
    warning
    User requested removing the GPU device from the infrastructure but the operation failed.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. For the detailed description of the issue trace down the messages with the following prefixes:
    • DBHC-SD
    • DBHD-SD
    ROSC-DD-510 [{session_id}] GPU device {gpu_device_id} dropped

    Message type:
    information
    Requested GPU device {gpu_device_id} is dropped.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 200 OK
    User message: Inherited, check the previous messages with the same request id
    Solution: none
    ROSC-DD-800 [{session_id}] Unexpected exception occurred while dropping GPU device

    Message type:
    error
    User requested drop of the GPU device but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while dropping set of GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-DR-700 [{session_id}] Invalid query string {query_string} in URI {uri}

    Message type:
    warning
    Superuser requested drop of set of the GPU devices but the passed string has invalid format in URI.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Query string must be in the following format:
    id=a1,a2,a3,...
    where 'a1' is a single GPU's global ID or range of GPU devices i.e. id1-id2.
    ROSC-DR-750 [{session_id}] Invalid device GPU ID: {invalid_gpu_id}

    Message type:
    warning
    Superuser requested drop of set of the GPU devices but one of the ID is invalid. Global GPU ID must be an unsigned integer.
    Authorization required:Superuser
    Source: OServer
    Result: request failed, OServer will try to drop the rest of the requested GPUs if there are any
    HTTP status code: none
    User message: Invalid GPU ID
    User will receive the message about which GPUs are dropped and which GPUs has failed to drop.
    Solution: Likely user entered invalid id. Verify origin of request.
    ROSC-DR-650 [{session_id}] GPU device: {gpu_id} cannot be dropped

    Message type:
    notice
    Superuser requested drop of set of the GPU devices but drop of one of the GPUs failed.
    Authorization required:Superuser
    Source: OServer
    Result: request failed, OServer will try to drop rest of requested GPUs if any
    HTTP status code: none
    User message: Invalid global GPU id
    User will receive the message about which GPUs are dropped and which GPUs has failed to drop.
    Solution: Examine the previous related messages with the same request id. For the detailed description of the issue trace down the messages with the following prefixes:
    • DBHC-SD
    • DBHD-SD
    ROSC-DR-51A [{session_id}] GPU device {gpu_device_id} dropped

    Message type:
    information
    Requested GPU devices {gpu_device_id} are dropped.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 200 OK
    User message: Inherited, check the previous messages with the same request id
    Solution: none
    ROSC-DR-51B [{session_id}] GPUs were not dropped

    Message type:
    information
    None of the requested GPU devices were dropped.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 04 No Content
    User message: Inherited, check the previous messages with the same request id
    Solution: none
    ROSC-DR-800 [{session_id}] Unexpected exception occurred while dropping GPU device

    Message type:
    error
    User requested drop of the GPU device but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while dropping set of GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-DU-710 [{session_id}] Invalid GPU ID {invalid_gpu_id}

    Message type:
    warning
    Superuser requested drop of GPU on behalf of user but the ID is invalid.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Invalid GPU ID
    Solution: Likely invalid GPU specified. Verify origin of request.
    ROSC-DU-62A [{session_id}] Superuser cannot drop GPUs, user {userid} has still active processes

    Message type:
    notice
    Superuser tried to drop GPUs on behalf of user {userid} but user still has active processes
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Cannot drop, user has active processes
    Solution: To drop the GPUs, user has to finish the processes first.
    ROSC-DU-720 [{session_id}] Drop of GPU {gpu_id} for user {userid} failed

    Message type:
    warning
    Superuser requested drop of GPU on behalf of user {userid} but the drop failed.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. For the detailed description of the issue trace down the messages with the following prefixes:
    • DBHC-DU
    • DBHD-DU
    ROSC-DU-510 [{session_id}] GPU for user {userid} dropped by {superuser}

    Message type:
    information
    {superuser} successfully dropped the GPU on behalf of {userid}.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 200 OK
    User message: Inherited, check the previous messages with the same request id
    Solution: none
    ROSC-DU-800 [{session_id}] Unexpected exception occurred while dropping GPU on behalf of user {userid}

    Message type:
    error
    User requested drop of the GPU device but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while dropping
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-WI-82A [{session_id}] Cannot retrieve user's information

    Message type:
    error
    The security plugin could not have retrieved information about the user.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 500 Bad Request
    Solution: Examine messages from security plugin with prefix QS1C for further details.
    ROSC-WI-82B [{session_id}] Unexpected exception occurred while retrieving user's information

    Message type:
    error
    User requested to retrieve information about him, but the request failed due to an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving user's information
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-AL-720 [{session_id}] User {userid} is disabled

    Message type:
    warning
    User's credentials were checked but the account is disabled.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 401 Unauthorized
    User message: Account is disabled, please contact administrator
    Solution: If necessary, enable user's account.
    ROSC-AL-82A [{session_id}] Unexpected exception occurred while authorizing user {userid} to use GPU

    Message type:
    error
    User requested drop of the GPU device but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while authorizing user
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-WI-81A [{session_id}] Cannot retrieve user's information

    Message type:
    error
    The security plugin could not have retrieved information about the user.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 500 Bad Request
    Solution: Examine messages from security plugin with prefix QS1C for further details.
    ROSC-WI-81B [{session_id}] Unexpected exception occurred while retrieving user's information

    Message type:
    error
    User requested to retrieve information about him, but the request failed due to an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving user's information
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-FG-710 [{session_id}] Failed to retrieve list of free GPUs

    Message type:
    warning
    User requested the list of free GPUs but the request failed due to the database issue.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Check the messages with the DBHC-FG or DBHD-FG prefix to find the cause of issue.
    If the issue cannot be solved please contact support
    ROSC-FG-80S [{session_id}] Invalid output data

    Message type:
    error
    User requested the list of free GPUs but the request contains invalid output data.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. Check the messages with the DBHC-FG or DBHD-FG prefix to find the cause of issue.
    If the issue cannot be solved please contact support
    ROSC-FG-800 [{session_id}] Unexpected exception occurred while generating list of free GPUs

    Message type:
    error
    User requested the list of free GPUs but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while generating list of free GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-TG-710 [{session_id}] User's GPUs drop failed while regenerate token

    Message type:
    warning
    User or superuser requested to generate a new token. To prevent losing the allocations, any GPUs allocated to user, must be first dropped. In this case the drop failed.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: message can be inherited from previous messages
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    1. Possibly user has still running processes, to successfully drop the GPUs all processes related to user's client must be terminated first. When user does not have running programs, likely the processes are inactive and administrator must terminate the processes from GPUBox Web Console or by issue the command $ agpubox rprocess {gpuserver} {processid} . When all processes are finished user can retry to generate new token.
    2. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-TG-82B [{session_id}] Cannot generate token, requested by {userid}

    Message type:
    error
    User requested to generate a new token but the request failed due to the security module issue.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: message can be inherited from previous messages
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    • Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-TG-32A [{session_id}] Token for user {userid} generated successfully

    Message type:
    debug
    User requested to generate a new token and the request finished successfully.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: message can be inherited from previous messages
    Result: request finished successfully
    HTTP status code: 200 OK
    Solution: none
    ROSC-TG-800 [{session_id}] Unexpected exception occurred while generating token

    Message type:
    error
    User requested to generate a new token but the request failed due to an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while generating token
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-SF-710 [{session_id}] Failed to retrieve list of free GPUs

    Message type:
    warning
    Superuser requested the list of free GPUs but the request has failed due to the database issue.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Trace down the messages with the following prefixes DBHC-SF or DBHD-SF for the reason of the issue.
    If the issue cannot be solved please contact support
    ROSC-SF-80S [{session_id}] Invalid output data

    Message type:
    error
    Superuser requested the list of free GPUs but the request has invalid output data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. Trace down the messages with the following prefixes DBHC-SF or DBHD-SF for the reason of the issue.
    If the issue cannot be solved please contact support
    ROSC-SF-800 [{session_id}] Unexpected exception occurred while generating list of free GPUs

    Message type:
    error
    Superuser requested the list of free GPUs but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while generating list of free GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-RS-800 [{session_id}] Unexpected exception occurred while retrieving statistics data

    Message type:
    error
    User requested to retrieve the statistics data but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving statistics data
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-HK-85H [{session_id}] Cannot perform housekeeping on users allocation records

    Message type:
    error
    Allocation records become orphans when their relation to the GPUs is lost.
    The housekeeping process cannot detect and remove the orphans from user's allocation table due to some database issue.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    1. Verify messages with the DBHC-CL and DBHD-CL prefixes in OServer's log.
    2. Examine OServer's log, when the issue cannot be solved please contact support.
    ROSC-BU-800 [{session_id}] Unexpected exception occurred while retrieving process list

    Message type:
    error
    Superuser requested the list of processes but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving process list
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-OC-70C [{session_id}] Invalid configuration parameter given

    Message type:
    warning
    User requested to retrieve OServer's configuration but the input data is invalid, or it does not have any valid configuration parameter.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution:
    1. The right parameters that you can display can be obtained by sending the agpubox osconfig command.
    2. Verify if the request comes from an authorized GPUBox infrastructure element.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-OC-80S [{session_id}] Invalid output data

    Message type:
    error
    User requested to retrieve OServer's configuration but the request has invalid output data.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    1. The right parameters that you can display can be obtained when issue command agpubox osconfig.
    2. Verify if the request comes from an authorized GPUBox infrastructure element.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-OC-800 [{session_id}] Unexpected exception occurred while retrieving OServer's configuration

    Message type:
    error
    User requested to retrieve OServer's configuration but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while generating list of free GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-LD-71A [{session_id}] Failed to retrieve list of GPU devices

    Message type:
    warning
    User requested the list of the GPU devices but the request failed due to the database issue.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Trace down the messages with the following prefixes DBHC-GD or DBHD-GD for the reason of the issue.
    If the issue cannot be solved please contact support
    ROSC-LD-80S [{session_id}] Invalid output data

    Message type:
    error
    User requested to retrieve the GPU devices but the request has invalid output data.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    1. Verify if the request comes from an authorized GPUBox infrastructure element.
    2. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-LD-800 [{session_id}] Unexpected exception occurred while retrieving GPU devices

    Message type:
    error
    User requested to retrieve the GPU devices but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving GPU devices
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-LG-76A [{session_id}] Failed to retrieve list of GPUs

    Message type:
    warning
    Superuser requested the list of GPUs but the request failed due to possible invalid database operation.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-LG or DBHD-LG prefix for the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-LG-86S [{session_id}] Invalid output data

    Message type:
    error
    Superuser requested the list of GPUs but the data received from database does not seems to be correct.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-LG or DBHD-LG prefix for the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-LG-860 [{session_id}] Unexpected exception occurred while retrieving list of GPUs

    Message type:
    error
    User requested the list of allocated GPUs but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving list of GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-LT-60V [{session_id}] None of GPUServers is available

    Message type:
    notice
    To retrieve list of GPUServers, at least single GPUServer must be registered.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution: start GPUServer
    ROSC-LT-700 [{session_id}] Invalid output data

    Message type:
    warning
    User requested the list of GPUServers but the request has invalid output data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine the previous related messages with the same request id.
    • If the issue cannot be solved please contact support
    ROSC-LT-800 [{session_id}] Unexpected exception occurred while retrieving list of GPUServers

    Message type:
    error
    Superuser requested to retrieve list of GPUServers but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving list of GPUServers\n Solution:
    ROSC-GC-70V [{session_id}] Specified GPUServer is not connected: {gpuserver_rest_address}

    Message type:
    warning
    Specified GPUServer is not connected and configuration parameters cannot be retrieved.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 404 Not Found
    User message: none
    Solution: Likely user entered invalid GPUServer name. You can obtain the list of available GPUServers from command:
    $ agpubox listserver
    ROSC-GC-80U [{session_id}] Problem while retrieving configuration, GPUServer is not available at address: {gpuserver_address}

    Message type:
    error
    Superuser requested to retrieve the configuration parameters but GPUServer at the {gpuserver_address} address is not available.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    1. Verify if GPUServer is up and running at a specified address, if not - restart GPUServer
      • If GPUServer was started as a service, the # service gpuserver status command must return gpuserver (pid 15870 15779 15762) is running... or similar.
      • If GPUServer was started from command line, issue command $ ps f | grep gpuserver
        12892 pts/2 Sl+ 1:18 /home/bob/gpubox-gpuserver/bin/gpuserver
        12896 pts/2 Sl+ 0:00 /home/bob/gpubox-gpuserver/bin/gpuserver
        13411 pts/2 SLl+ 26:07 /home/bob/gpubox-gpuserver/bin/gpuserver
      In both cases 2 GPUServer's processes must be visible: primary and secondary. In the above exemplary listing:
      • 12892 is a primary GPUServer - root process
      • 12896 is a secondary GPUServer - serves service requests from OServer.
      • 13411 is a subserver - serves GPUBox's clients requests
    2. Verify if secondary server is up and running. Check if GPUServer is listening on the port indicated by the gpuserver_rest_bind parameter: # lsof -Pn -i | grep 8080
    3. Examine OServer's log, when the issue cannot be solved please contact support.
    ROSC-GC-80A [{session_id}] Problem while retrieving configuration from GPUServer: {gpuserver_hostname}, {return_code}

    Message type:
    error
    Superuser requested to retrieve the configuration parameters from GPUServer but it returned invalid return code.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution:
    ROSC-LP-82P [{session_id}] Failed to parse input data, list of processes from {gpuserver_hostname} failed

    Message type:
    error
    OServer detected a syntax error in the input data. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    ROSC-GC-70B [{session_id}] GPUServer is required

    Message type:
    warning
    GPUServer name is required to retrieve GPUServer's configuration parameters.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    Solution: You can obtain the list of available GPUServers from command:
    $ agpubox listserver
    ROSC-GC-80S [{session_id}] Invalid output data

    Message type:
    error
    User requested the list of free GPUs but the request contains invalid output data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. If the issue cannot be solved please contact support
    ROSC-GC-80F [{session_id}] Unexpected exception occurred while retrieving GPUServer's configuration

    Message type:
    error
    Superuser requested to retrieve GPUServer's configuration but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving GPUServer's configuration
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-T2-60V [{session_id}] None of GPUServers is available

    Message type:
    notice
    Specified GPUServer is not connected to retrieve configuration parameters.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution: start GPUServer
    ROSC-T2-700 [{session_id}] Invalid output data

    Message type:
    warning
    User requested the list of the GPUs but the request has invalid output data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. Examine related logs of GPUServers. If the issue cannot be solved please contact support
    ROSC-T2-800 [{session_id}] Unexpected exception occurred while generating list of GPUs

    Message type:
    error
    User requested the list of the GPUs but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while generating list of GPUs
    Solution:
    ROSC-GL-80U [{session_id}] Problem while retrieving GPUServer's log, GPUServer is not available at address: {gpuserver_address}

    Message type:
    error
    Superuser requested to list log of GPUServer but GPUServer at address {gpuserver_address} is not available.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    1. Verify if GPUServer is up and running at a specified address, if not - restart GPUServer
      • If GPUServer was started as a service, the # service gpuserver status command must return gpuserver (pid 15870 15779 15762) is running... or similar.
      • If GPUServer was started from command line, issue command $ ps f | grep gpuserver
        12892 pts/2 Sl+ 1:18 /home/bob/gpubox-gpuserver/bin/gpuserver
        12896 pts/2 Sl+ 0:00 /home/bob/gpubox-gpuserver/bin/gpuserver
        13411 pts/2 SLl+ 26:07 /home/bob/gpubox-gpuserver/bin/gpuserver
      In both cases 2 GPUServer's processes must be visible: primary and secondary. In the above exemplary listing:
      • 12892 is a primary GPUServer - root process
      • 12896 is a secondary GPUServer - serves service requests from OServer.
      • 13411 is a subserver - serves GPUBox's clients requests
    2. Verify if secondary server is up and running. Check if GPUServer is listening on the port indicated by the gpuserver_rest_bind parameter: # lsof -Pn -i | grep 8080
    3. Examine OServer's log, when the issue cannot be solved please contact support.
    ROSC-GL-81U [{session_id}] Empty log from GPUServer: {gpuserver_hostname}

    Message type:
    error
    GPUServer from {gpuserver_hostname} returned an empty log.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution:
    ROSC-GL-81A [{session_id}] Problem while retrieving log from GPUServer: {gpuserver_hostname}, {return_code}

    Message type:
    error
    Superuser requested the log but GPUServer returned invalid return code.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    ROSC-GL-82U [{session_id}] Empty log from GPUServer: {gpuserver_hostname}

    Message type:
    error
    GPUServer from {gpuserver_hostname} returned empty log.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution:
    ROSC-GL-51A [{session_id}] HTTP Status Code 200, {gpuserver_hostname}

    Message type:
    information
    GPUServer from {gpuserver_hostname} returned log.
    Authorization required:Superuser
    Source: OServer
    Result: user will receive GPUServer's log
    HTTP status code: 200 OK
    User message: none
    Solution: none
    ROSC-GL-800 [{session_id}] Unexpected exception occurred while retrieving log from GPUServer

    Message type:
    error
    Superuser requested to retrieve GPUServer's log but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving log from GPUServer
    Solution:
    ROSC-LP-70B [{session_id}] None of GPUServers is available or no process is running at the moment

    Message type:
    warning
    Superuser requested to list running processes but none of GPUServers is available or no process is running at the moment.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: No process is running at the moment
    Solution: none
    ROSC-LP-80S [{session_id}] Invalid output data

    Message type:
    error
    User requested the list of free GPUs but the request contains invalid output data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. If the issue cannot be solved please contact support
    ROSC-LP-800 [{session_id}] Unexpected exception occurred while retrieving process list

    Message type:
    error
    Superuser requested the list of processes but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving process list
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-LL-51E [{session_id}] Log is redirected to STDOUT

    Message type:
    information
    User requested to retrieve OServer's log but the log is redirected to standard output i.e. it is displayed on terminal. Probably OServer is started as non-service process.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: Log is redirected to STDOUT
    Solution: Review the log on terminal or change the oserver_log_path parameter and redirect log to file.
    ROSC-LL-61A [{session_id}] Invalid parameters to retrieve OServer's log

    Message type:
    notice
    User requested to retrieve OServer's log but the parameters are invalid.
    The parameters are passed in URI.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution:
    1. Verify the parameters in URI, message: ROSC-HH-500
    2. Verify if the request comes from an authorized GPUBox infrastructure element.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-LL-81L [{session_id}] HTTP Status Code 500, log too large: {log_size}

    Message type:
    error
    Superuser requested to retrieve OServer's log but the size of the log in file exceeds the maximum size that OServer is capable to proceed.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • You can review the log in the file indicated by the oserver_log_path parameter.
    • Copy current log to archive:
      • Use tool like log rotate. You can find more detail in "GPUBox Administration Guide and Reference".
      • Use linux bash to flush the log to archive as an example you can issue those commands: # cp {log_file_name} `date +"%Y%m%d-%H%M%S"`.log;>{log_file_name};pkill -HUP oserver
      OServer must receive SIGHUP(1) signal to reopen the log file. OServer signals this fact with messages
      • OSRV-OH-76D [{pid}] OServer received signal Hangup(1)
      • OSVC-LR-50A Log /usr/local/gpubox-oserver/log/oserver.log reopened
    ROSC-LL-81D [{session_id}] OServer's log is empty

    Message type:
    error
    Superuser requested to retrieve OServer's log but the log is empty.
    The file pointed by the oserver_log_path parameter must be empty. Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution:
    1. Examine the previous messages in OServer's log to find the messages related to the issue.
    2. Verify if the file and directories permissions allow the OServer to open and write data.
    3. Probably the log file was renamed or moved to different directory, or it was archived but OServer did not receive the SIGHUP signal to reopen the log file.
      In each case try to issue the # pkill -HUP oserver command. There is no need to recreate the log file, OServer will do this automatically.
    4. When the SIGHUP signal does not work, try to restart OServer.
    ROSC-LL-71A [{session_id}] Log's limit must be an integer number

    Message type:
    warning
    User requested to retrieve OServer's log but gave invalid limit number. Limit must be an integer.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Likely user entered invalid OServer's log limit. Verify the origin of the request.
    ROSC-LL-51G [{session_id}] Parameters generate empty output, log not retrieve

    Message type:
    information
    Superuser requested to retrieve OServer's log but the given parameters generated empty output.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution: Specify the correct parameters.
    ROSC-LL-800 [{session_id}] Unexpected exception occurred while retrieving OServer's log

    Message type:
    error
    User requested to retrieve OServer's log but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-M1-82A [{session_id}] Invalid input data for Monitor1

    Message type:
    error
    Superuser requested to retrieve data from Monitor1 but the input query is empty.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: Empty request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-M1-82B [{session_id}] Invalid parameter value to retrieve Monitor1 data

    Message type:
    error
    Superuser requested to retrieve data from Monitor1 but the parameter has invalid value.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Invalid parameter's value
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-M1-82C [{session_id}] Invalid output data

    Message type:
    error
    Superuser requested to retrieve Monitor1 data but the request has invalid output data.
    Authorization required: Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    • Examine the previous related messages with the same request id.
    • If the issue cannot be solved please contact support
    ROSC-M1-800 [{session_id}] Unexpected exception occurred while retrieving Monitor1 data

    Message type:
    error
    User requested to retrieve data from Monitor1 but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving Monitor1 data
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-C1-82A [{session_id}] Invalid input data for Monitor1

    Message type:
    error
    Superuser requested to retrieve data from Monitor1 but the input query is empty.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: Empty request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-C1-82B [{session_id}] Invalid parameter value to retrieve Monitor1 data

    Message type:
    error
    Superuser requested to retrieve data from Monitor1 but the parameter has invalid value.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Invalid parameter's value
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-C1-800 [{session_id}] Unexpected exception occurred while retrieving Monitor1 data

    Message type:
    error
    User requested to retrieve data from Monitor1 but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving Monitor1 data
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-O1-82B [{session_id}] Invalid parameter value to offload Monitor1 data

    Message type:
    error
    Superuser requested to offload data from Monitor1 but the parameter has invalid value.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Invalid parameter's value
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-O1-80E [{session_id}] Unexpected exception occurred while offloading Monitor1 data

    Message type:
    error
    User requested to retrieve data from Monitor1 but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while offloading Monitor1 data
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-AB-81A [{session_id}] Empty user passed while enabling or disabling user

    Message type:
    error
    Superuser requested to enable or disable user but the request contains invalid input data with empty userid.
    Authorization required:Superuser
    Source: OServer
    User message: Empty user passed while enabling or disabling user
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    1. Verify if the request comes from an authorized GPUBox infrastructure element.
    2. Specify enable or disable in URI.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-AB-82A [{session_id}] Cannot enable user {userid}

    Message type:
    error
    Superuser requested to enable user but an error occurred in the security module.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    • Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-AB-82B [{session_id}] Cannot disable user {userid}

    Message type:
    error
    Superuser requested to disable user's account but an error occurred in the security module.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    • Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-AB-82C [{session_id}] Incorrect request, enable or disable required

    Message type:
    error
    Superuser requested to enable or disable user but the request contains invalid input data.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    1. Verify if the request comes from an authorized GPUBox infrastructure element.
    2. In the request, specify the [enable] or [disable] option in URI.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-SC-82B [{session_id}] Unexpected exception occurred while setting comment for user {userid}

    Message type:
    error
    User requested to set comment password but the request failed due to an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while setting comment
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-SC-700 [{session_id}] Content length not set, set comment for user {userid} failed

    Message type:
    warning
    Superuser requested to set a comment for user but it failed due to empty body content.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 411 Length Required
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SC-710 [{session_id}] Missing content, set comment for user {userid} failed

    Message type:
    warning
    Superuser requested to set a comment for user {userid}, field 'Content-Length' in header exists but it is too small to contain proper data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SC-82P [{session_id}] Failed to parse input data, failed to set comment for user {userid}

    Message type:
    error
    OServer detected a syntax error in the input data. Data has incorrect format or it is damaged.
    Authorization required:Superuser
    Source: OServer
    User message: Failed to parse input data, set comment failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SC-72A [{session_id}] Input data does not have 'comment' statement, set comment for user {userid} failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'comment' statement.
    Authorization required:Superuser
    Source: OServer
    User message: Input data does not have 'comment' statement, set comment for user failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SC-72B [{session_id}] Invalid input data, set comment for user {userid} failed

    Message type:
    warning
    OServer detected a syntax error in the input data.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid input
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SC-73A [{session_id}] Set comment for user {userid} failed

    Message type:
    warning
    The security plugin could not change the comment.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid input
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution: Examine messages from security plugin with prefix QS1C for further details.
    ROSC-SC-82A [{session_id}] Unexpected exception occurred while setting username for user {userid}

    Message type:
    error
    User requested to set the username but the request failed due to an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while setting username
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-SG-700 [{session_id}] Invalid group ID {invalid_group_id}

    Message type:
    warning
    Superuser requested to set group ID but gave an invalid group ID. Group ID must be an unsigned integer.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Invalid group ID
    Solution: Likely superuser entered invalid number. Verify origin of request.
    ROSC-SG-82A [{session_id}] Cannot set group {groupid} for user {userid}

    Message type:
    error
    Superuser requested to change group id but an error occurred in the security module.
    Authorization required:Superuser
    Source: OServer
    User message: Cannot set group id
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    • Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-SM-700 [{session_id}] Invalid number of max GPUs, {invalid_max_number}

    Message type:
    warning
    User requested to change the maximum number of the GPUs that user can allocate but the parameter is invalid, it must be an unsigned integer.
    {invalid_max_number} is an invalid number.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: Invalid max GPU
    Solution: Likely maximum number of GPUs is invalid number. Verify origin of request.
    ROSC-SM-73A [{session_id}] Set maximum number of GPUs for user {userid} failed

    Message type:
    warning
    The security plugin could not have changed the maximum number of GPUs.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid input
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution: Examine messages from security plugin with prefix QS1C<> for further details.
    ROSC-SN-700 [{session_id}] Content length not set, set username for user {userid}

    Message type:
    warning
    Superuser requested to set username for user but it failed due to an empty body content.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 411 Length Required
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SN-710 [{session_id}] Missing content, set username for user {userid} failed

    Message type:
    warning
    Superuser requested to set username for user {userid}, field 'Content-Length' in header exists but it is too small to contain proper data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SN-82P [{session_id}] Failed to parse input data, failed to set username for user {userid}

    Message type:
    error
    OServer detected a syntax error in the input data. Data has incorrect format or it is damaged.
    Authorization required:Superuser
    Source: OServer
    User message: Failed to parse input data, set username failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SN-72A [{session_id}] Input data does not have 'username' statement, set username for user {userid} failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'username' statement.
    Authorization required:Superuser
    Source: OServer
    User message: Input data does not have 'username' statement, set username for user failed
    Result: set username for user failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SN-72B [{session_id}] Invalid input data, set username for user {userid} failed

    Message type:
    warning
    OServer detected a syntax error in the input data.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid input
    Result: set username for user failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SN-73A [{session_id}] Set username for user {userid} failed

    Message type:
    warning
    The security plugin could not change the comment.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid input
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution: Examine messages from the security plugin with the QS1C prefix for further details.
    ROSC-SN-82A [{session_id}] Unexpected exception occurred while setting username for user {userid}

    Message type:
    error
    User requested to set the username but the request failed due to an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while setting username
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-VF-82A [{session_id}] Failed to set 'valid from' value for user {userid}

    Message type:
    error
    Superuser requested to set the 'valid from' date and time but an error occurred in the security module.
    Authorization required:Superuser
    Source: OServer
    User message: Failed to set 'valid from' value
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    1. Verify if the date and time format is correct in URI.
    2. Verify if the request comes from an authorized GPUBox infrastructure element.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-VT-82A [{session_id}] Failed to set 'valid to' value for user {userid}

    Message type:
    error
    Superuser requested to set the 'valid to' date and time but an error occurred in the security module.
    Authorization required:Superuser
    Source: OServer
    User message: Failed to set 'valid to' value
    Result: request failed
    HTTP status code: 500 Internal Server Error
    Solution:
    1. Verify if the date and time format is correct in URI.
    2. Verify if the request comes from an authorized GPUBox infrastructure element.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-PS-80A [{session_id}] Invalid GPU ID {invalid_gpu_id}

    Message type:
    error
    Superuser requested to change the GPU status but gave an invalid GPU ID. GPU ID must be an unsigned integer.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 405 Method Not Allowed
    User message: none
    Solution:
    • Verify requested GPU ID in URI.
    ROSC-GW-82P [{session_id}] Failed to parse input data, retrieve webcache for user {userid} failed

    Message type:
    error
    OServer detected a syntax error in the input data. Received data has incorrect format or it is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Failed to parse input data, retrieve webcache failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-GW-72A [{session_id}] Input data does not have 'key' statement, retrieve webcache failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'key' statement.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'key' statement, retrieve webcache failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-GW-800 [{session_id}] Unexpected exception occurred while retrieving webcache

    Message type:
    error
    User requested to retrieve data in webcache but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving webcache
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-SA-700 [{session_id}] Content length not set, create user failed

    Message type:
    warning
    Superuser requested create user but it failed due to empty body content.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 411 Length Required
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SA-710 [{session_id}] Missing content, create user failed

    Message type:
    warning
    Superuser requested to create a user, 'Content-Length' in header exists but it's too small to contains proper data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SA-82P [{session_id}] Failed to parse input data, create user failed

    Message type:
    error
    OServer detected a syntax error in the input data. Data has incorrect format or it is damaged.
    Authorization required:Superuser
    Source: OServer
    User message: Failed to parse input data, set comment failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SA-72A [{session_id}] Input data does not have 'userid' statement, create user failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'userid' statement.
    Authorization required:Superuser
    Source: OServer
    User message: userid is required
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SA-72B [{session_id}] Input data does not have 'username' statement, create user failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'username' statement.
    Authorization required:Superuser
    Source: OServer
    User message: username is required
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SA-72C [{session_id}] Input data does not have 'password' statement, create user failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'password' statement.
    Authorization required:Superuser
    Source: OServer
    User message: password is required
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SA-72D [{session_id}] Invalid input data, create user failed

    Message type:
    warning
    OServer detected a syntax error in the input data.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid input
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify origin of request if it comes from authorized GPUBox infrastructure elements.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SA-62A [{session_id}] User {userid} already exists

    Message type:
    notice
    User with the same {userid} cannot be created twice, it has to be unique.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the user ID is correct, change if necessary.
    ROSC-SA-82B [{session_id}] Cannot create user={userid}, username={username}

    Message type:
    error
    Likely the database error occurred and user cannot be created.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 500 Bad Request
    Solution:
    1. Verify if the request comes from an authorized GPUBox infrastructure element.
    2. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-SA-800 [{session_id}] Unexpected exception occurred while creating user

    Message type:
    error
    User requested to create the user account but the request has failed due to an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while creating user
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-PG-80P [{session_id}] Failed to parse input data, GPU registration failed

    Message type:
    error
    OServer detected a syntax error in the input data. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Failed to parse input data, GPU registration failed, {detailed_message}
    User will receive detailed message about the error. For GPU registration check GPUServer's log for details.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from GPUServer.
    • Verify if OServer and GPUServer have the same versions.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PG-710 [{session_id}] Input data does not have 'ip' statement, GPU registration failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'ip' statement. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not contain the 'ip' statement, GPU registration failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from GPUServer.
    • Verify if OServer and GPUServer have the same versions.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PG-720 [{session_id}] Input data does not have 'port' statement, GPU registration failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'port' statement. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'port' statement, GPU registration failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from GPUServer.
    • Verify if OServer and GPUServer have the same versions.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PG-72A [{session_id}] Input data does not have 'restapi' statement, GPU registration failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'restapi' statement. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'restapi' statement, GPU registration failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from GPUServer.
    • Verify if OServer and GPUServer have the same versions.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PG-72B [{session_id}] Input data does not have 'hostname' statement, GPU registration failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'hostname' statement. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'hostname' statement, GPU registration failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from GPUServer.
    • Verify if OServer and GPUServer have the same versions.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PG-72C [{session_id}] Input data does not have 'version' statement, GPU registration failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'version' statement. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'version' statement, GPU registration failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from GPUServer.
    • Verify if OServer and GPUServer have the same versions.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PG-810 [{session_id}] Cannot find GPU devices in input data, GPU registration failed

    Message type:
    warning
    Data send by GPUServer did not contain any information about GPUs.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Cannot find GPU devices in input data, GPU registering failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if GPUServer:
      • has GPU available devices,
      • has specified devices in the 'gpuserver_gpus' configuration parameter.
      How many GPUs are in use - follow the message GBSC-GI-52A, GBSC-GI-52B, GBSC-GI-52F, GBSC-GI-72A or GBSC-GI-72B.
    • Verify if the request comes from GPUServer.
    • Verify if OServer and GPUServer have the same versions.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PG-800 [{session_id}] Unexpected exception occurred while registration GPU

    Message type:
    error
    OServer received an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: OServer processing continue, request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred, GPU registration failed
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-PW-82P [{session_id}] Failed to parse input data, save webcache for user {userid} failed

    Message type:
    error
    OServer detected a syntax error in the input data. Received data has incorrect format or it is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Failed to parse input data, save webcache failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PW-72A [{session_id}] Input data does not have 'key' statement, save webcache failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'key' statement.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'key' statement, save webcache failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PW-72B [{session_id}] Input data does not have 'data' statement, save webcache failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'data' statement.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Input data does not have 'data' statement, save webcache failed
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-PW-800 [{session_id}] Unexpected exception occurred while saving webcache

    Message type:
    error
    User requested to save data in webcache but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while saving webcache
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-HH-50A [{session_id}] Redirect to {uri}

    Message type:
    information
    Authorization required:Superuser or regular user
    Source: OServer
    User message: none
    Result: Request will be redirect to {uri}.
    HTTP status code: 303 See Other
    Solution: none
    ROSC-KP-70V [{session_id}] Specified GPUServer is not connected: {gpuserver_rest_address}

    Message type:
    warning
    Specified GPUServer is not connected and the process cannot be removed.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: none
    Solution: Likely user entered invalid GPUServer name. You can obtain the list of available GPUServers from command:
    $ agpubox listserver
    ROSC-KP-80U [{session_id}] Problem while removing process, GPUServer is not available at address: {gpuserver_address}

    Message type:
    error
    Superuser requested to remove process but GPUServer at the {gpuserver_address} address is not available.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    1. Verify if GPUServer is up and running at a specified address, if not - restart GPUServer
      • If GPUServer was started as a service, the # service gpuserver status command must return gpuserver (pid 15870 15779 15762) is running... or similar.
      • If GPUServer was started from command line, issue command $ ps f | grep gpuserver
        12892 pts/2 Sl+ 1:18 /home/bob/gpubox-gpuserver/bin/gpuserver
        12896 pts/2 Sl+ 0:00 /home/bob/gpubox-gpuserver/bin/gpuserver
        13411 pts/2 SLl+ 26:07 /home/bob/gpubox-gpuserver/bin/gpuserver
      In both cases 2 GPUServer's processes must be visible: primary and secondary. In the above exemplary listing:
      • 12892 is a primary GPUServer - root process
      • 12896 is a secondary GPUServer - serves service requests from OServer.
      • 13411 is a subserver - serves GPUBox's clients requests
    2. Verify if secondary server is up and running. Check if GPUServer is listening on the port indicated by the gpuserver_rest_bind parameter: # lsof -Pn -i | grep 8080
    3. Examine OServer's log, when the issue cannot be solved please contact support.
    ROSC-KP-80A [{session_id}] Cannot remove process: {process_id}, GPUServer: {gpuserver_address}, {return_code}

    Message type:
    error
    Superuser requested to remove process from GPUServer but GPUServer returned invalid return code.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: inherited from GPUServer
    User message: none
    Solution:
    ROSC-KP-70B [{session_id}] GPUServer and process ID is required

    Message type:
    warning
    GPUServer's name and the process ID are required to remove a process on GPUServer.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • You can obtain the list of available GPUServer and process IDfrom command
      $ agpubox listprocess
    • The list process
    ROSC-LG-75A [{session_id}] Failed to retrieve list of allocated GPUs

    Message type:
    warning
    User requested the list of allocated GPUs but the request failed due to database issue.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: Inherited, check the previous messages with the same request id
    User message: Inherited, check the previous messages with the same request id
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-GU or DBHD-GU prefix for the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-LG-85S [{session_id}] Invalid output data

    Message type:
    error
    User requested the list of GPUs allocated to him but the data received from database does not seems to be correct.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine the previous related messages with the same request id. Find the messages with the DBHC-GU or DBHD-GU prefix for the cause of the issue.
    If the issue cannot be solved please contact support
    ROSC-LG-850 [{session_id}] Unexpected exception occurred while retrieving list of allocated GPUs

    Message type:
    error
    User requested the list of allocated GPUs but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving list of allocated GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-IF-34B [{session_id}] Install files path: {install_path}

    Message type:
    debug
    User requested to download the installation file or to list the content of the installation directory.
    {web_path} can be a full path to a file or a path to a directory, both must be inside the directory pointed by the 'oserver_installfiles_path' configuration parameter.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: processing continue
    HTTP status code: none
    User message: none
    Solution: none
    ROSC-IF-71A [{session_id}] No access to installation path: {installation_path}

    Message type:
    warning
    OServer does not have access to the file specified by {installation_path}.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 404 Not Found
    User message: none
    Solution:
    • Verify if user is related to OServer's process has access to file {installation_path}.
    ROSC-IF-71B [{session_id}] Unprivileged access to installation path: {installation_path}

    Message type:
    warning
    Regular user tried to access the file in the 'admin' directory, only superusers have access to the files in the oserver_installfiles_path/admin directory.
    Authorization required:Only regular user can generate this message.
    Source: OServer
    Result: request failed
    HTTP status code: 401 Unauthorized
    User message: none
    Solution: Examine messages in OServer's log with the same request id. Verify the origin of the request and the user. This can be a security breach.
    GPUBox authorized tool should not produce invalid URL request i.e. regular user should not request files from administrator zone.
    However, if you suspect issue in GPUBox client or GPUBox Web Console please contact support.
    ROSC-IF-05A [{session_id}] Install file: {install_file_path}

    Message type:
    trace
    User requested to download the installation file or to list the content of the installation directory.
    {install_file_path} displays the full path to the file that is accessible publicly.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: processing continue
    HTTP status code: none
    User message: none
    Solution: none
    ROSC-IF-06A [{session_id}] Install file: {install_file_path}

    Message type:
    trace
    Superuser requested to download the installation file or to list the content of the installation directory.
    {install_file_path} displays the full path to the file that is accessible only by superusers.
    Authorization required:Superuser
    Source: OServer
    Result: processing continue
    HTTP status code: none
    User message: none
    Solution: none
    ROSC-IF-74E [{session_id}] Directory /install/admin does not exist

    Message type:
    warning
    Superuser requested to download or list the content of 'admin' directory but the directory does not exists.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: none
    User message: none
    Solution: if necessary, create the 'admin' directory in the directory indicated by the 'oserver_installfiles_path' configuration parameter. Verify if user related to OServer's process has access to the direcotry 'admin'.
    ROSC-IF-80A [{session_id}] Unexpected exception occurred while processing list of installation files

    Message type:
    error
    User requested to download or list the content of 'oserver_installfiles_path' directory but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-IF-80B [{session_id}] Unexpected exception occurred while generating output of installation files

    Message type:
    error
    User requested to download or list the content of the 'oserver_installfiles_path' directory but the request generated an unexpected exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-WF-34A [{session_id}] Web URL request: {url_request}

    Message type:
    debug
    User requested URL. The string of {url_request} does not contain full OServer's address i.e. protocol type (HTTP or HTTPS), domain name and port.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: processing continue
    HTTP status code: none
    User message: none
    Solution: none
    ROSC-WF-05B [{session_id}] Web URL translated from : {url_requested} to: {web_path}

    Message type:
    trace
    User requested URL and the string was translated from {url_request} to {url_translated}. The translation is necessary when {request_url} is a directory, the server adds the 'index.html' string that {web_path} become full path to web resource.
    The string of {url_request} does not contain OServer's full address i.e. protocol type (HTTP or HTTPS), domain name and port.
    The {web_path} is a fully qualified file path to web resources.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: processing continue
    HTTP status code: none
    User message: none
    Solution: none
    ROSC-WF-35C [{session_id}] Web URL request: {web_path}

    Message type:
    debug
    URL requested by user was translated and server will serve the web resource from path {web_path}.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: processing continue
    HTTP status code: none
    User message: none
    Solution: none
    ROSC-WF-71A [{session_id}] No access to web path: {web_path}

    Message type:
    warning
    OServer does not have access to the file specified by {web_path}.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 401 Unauthorized
    User message: none
    Solution:
    • Verify if user is related to OServer's process has access to file {web_path}.
    ROSC-CC-70D [{session_id}] Invalid value for 'oserver_log_level' parameter given

    Message type:
    warning
    User requested to change OServer's configuration parameter 'oserver_log_level' but the input data is invalid.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution:
    Specify one of the following values:
    • trace
    • debug
    • info
    • notice
    • warning
    • error
    • critical
    ROSC-CC-70E [{session_id}] Invalid value for 'oserver_allocation_option' parameter given

    Message type:
    warning
    User requested to change OServer's configuration parameter 'oserver_allocation_option' but the input data is invalid.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution:
    Specify one of the following values:
    • free
    • shared
    ROSC-CC-70F [{session_id}] Configuration parameter value must be an unsigned integer number

    Message type:
    warning
    User requested to change OServer's configuration parameter but gives invalid value number. Value must be an unsigned integer.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Likely user entered invalid OServer's configuration value. Verify origin of the request.
    ROSC-CC-70H [{session_id}] Invalid configuration parameter given

    Message type:
    warning
    User requested to change OServer's configuration but the parameter is invalid.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution:
    1. The list of changeable parameters, can be obtained when issue command agpubox osconfig.
    2. Verify if the request comes from an authorized GPUBox infrastructure element.
    3. Examine the previous messages from OServer's log, if you cannot find the cause of the issue please contact support
    ROSC-CC-50D Parameter {parameter_name} change to value {value}

    Message type:
    information
    User requested to change OServer's configuration and the {parameter_name} parameter was successfully changed to {value}
    Authorization required:Superuser
    Source: OServer
    Result: parameter changed
    HTTP status code: 200 OK
    User message: none
    Solution: none
    ROSC-GS-70V [{session_id}] Specified GPUServer is not connected: {gpuserver_rest_address}

    Message type:
    warning
    Specified GPUServer is not connected and the configuration parameters cannot be changed.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 404 Not Found
    User message: none
    Solution: Likely user entered invalid GPUServer name. You can obtain the list of available GPUServers from command:
    $ agpubox listserver
    ROSC-GS-80U [{session_id}] Problem while changing configuration parameter, GPUServer is not available at address: {gpuserver_address}

    Message type:
    error
    Superuser requested to change the configuration parameter, but GPUServer at the {gpuserver_address} address is not available.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    1. Verify if GPUServer is up and running at a specified address, if not - restart GPUServer
      • If GPUServer was started as a service, the # service gpuserver status command must return gpuserver (pid 15870 15779 15762) is running... or similar.
      • If GPUServer was started from command line, issue command $ ps f | grep gpuserver
        12892 pts/2 Sl+ 1:18 /home/bob/gpubox-gpuserver/bin/gpuserver
        12896 pts/2 Sl+ 0:00 /home/bob/gpubox-gpuserver/bin/gpuserver
        13411 pts/2 SLl+ 26:07 /home/bob/gpubox-gpuserver/bin/gpuserver
      In both cases 2 GPUServer's processes must be visible: primary and secondary. In the above exemplary listing:
      • 12892 is a primary GPUServer - root process
      • 12896 is a secondary GPUServer - serves service requests from OServer.
      • 13411 is a subserver - serves GPUBox's clients requests
    2. Verify if secondary server is up and running. Check if GPUServer is listening on the port indicated by the gpuserver_rest_bind parameter: # lsof -Pn -i | grep 8080
    3. Examine OServer's log, when the issue cannot be solved please contact support.
    ROSC-GS-80A [{session_id}] Problem while changing configuration parameter from GPUServer: {gpuserver_hostname}, {return_code}

    Message type:
    error
    Superuser requested to change the configuration parameters from GPUServer, but it returned invalid return code.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: none
    Solution:
    ROSC-GS-70B [{session_id}] GPUServer is required

    Message type:
    warning
    GPUServer name is required to change GPUServer's configuration parameter.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution: You can obtain the list of available GPUServers from command:
    $ agpubox listserver
    ROSC-GC-800 [{session_id}] Unexpected exception occurred while changing GPUServer's configuration

    Message type:
    error
    Superuser requested to change GPUServer's configuration parameter but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while retrieving GPUServer's configuration
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-SH-52A User {userid} does not have allocate GPU

    Message type:
    information
    User does not have have any GPUs allocates to perform reallocation.
    Authorization required: Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 204 No Content
    User message: GPUs are not allocated
    Solution: User must have allocated GPU to proceed here command.
    ROSC-SH-72B Command here failed, userid: {userid}, ip: {ip}

    Message type:
    warning
    Unsuccessful execution of the here command. Authorization required: Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: inherited but not 200 and 204
    User message: GPUs are not allocated
    Solution: Examine OServer's log to find the issue. Messages with prefixes DBHC-SH and DBHD-SH can point onto the issue.
    ROSC-O1-800 [{session_id}] Unexpected exception occurred while reallocating GPUs

    Message type:
    error
    User requested to reallocate GPUs but the request generated an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while reallocating GPUs
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-SP-700 [{session_id}] Content length not set, set new password for user {userid} failed

    Message type:
    warning
    User requested to set the new password but it failed due to empty body content.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 411 Length Required
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SP-710 [{session_id}] Invalid content, set new password for user {userid} failed

    Message type:
    warning
    User requested the GPU allocation, field 'Content-Length' in header exists but it is too small to contain proper data.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SP-82P [{session_id}] Failed to parse input data, set new password for user {userid} failed

    Message type:
    error
    OServer detected a syntax error in the input data. Received data has incorrect format or it is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Failed to parse input data, set new password failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SP-73A [{session_id}] Empty password given, set new password for user {userid} failed

    Message type:
    warning
    User requested to change password but current password or new password is not given.
    Received data has incorrect format or it is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Empty password given
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SP-52B [{session_id}] Invalid password given, set new password for user {userid} failed

    Message type:
    information
    User requested to change password but current password or new password has invalid format i.e. must be a string of printable character.
    Received data has incorrect format or it is damaged.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Invalid password given
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SP-320 [{session_id}] Current and new passwords are identical, userid: {userid}, change password failed

    Message type:
    debug
    New password entered by user is identical to the old one.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: Current and new passwords are identical
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution: User must enter different password than previously.
    ROSC-SP-510 [{session_id}] Failed to set new password for user {userid}

    Message type:
    information
    Password for user {userid} cannot be changed.
    Authorization required:Superuser or regular user
    Source: OServer
    User message: none
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution: Examine OServer's log and verify the reason of failure. Messages with the QS1C-SP and QS1D-SP prefixes can help to diagnose the issue.
    ROSC-SP-800 [{session_id}] Unexpected exception occurred while changing password for user {userid}

    Message type:
    error
    User requested to change password but the request failed due to exception.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while changing password
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-SS-700 [{session_id}] Content length not set, set password for user {userid} failed

    Message type:
    warning
    Superuser requested to set password for user but it failed due to empty body content.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 411 Length Required
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SS-710 [{session_id}] Missing content, set password for user {userid} failed

    Message type:
    warning
    Superuser requested to set password for user {userid}, field 'Content-Length' in header exists but it is too small to contain proper data.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 400 Bad Request
    User message: none
    Solution: Verify if the request comes from an authorized GPUBox infrastructure component.
    ROSC-SS-82P [{session_id}] Failed to parse input data, failed to set password for user {userid}

    Message type:
    error
    OServer detected a syntax error in the input data. Data has incorrect format or it is damaged.
    Authorization required:Superuser
    Source: OServer
    User message: Failed to parse input data, set password failed, {detailed_message}
    User will receive the detailed message about the error.
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SS-72A [{session_id}] Input data does not have 'npasswd' statement, set password for user {userid} failed

    Message type:
    warning
    OServer detected a syntax error in the input data. The input data does not contain the 'npasswd' statement.
    Authorization required:Superuser
    Source: OServer
    User message: Empty password
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SS-72B [{session_id}] Invalid input data, set password for user {userid} failed

    Message type:
    warning
    OServer detected a syntax error in the input data.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid password
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-SS-73A [{session_id}] Set password for user {userid} failed

    Message type:
    warning
    The security plugin could not change the password.
    Authorization required:Superuser
    Source: OServer
    User message: Invalid input
    Result: request failed
    HTTP status code: 400 Bad Request
    Solution: Examine messages from security plugin with prefix QS1C<> for further details.
    ROSC-SS-82A [{session_id}] Unexpected exception occurred while setting password for user {userid}

    Message type:
    error
    Superuser requested to set password but the request failed due to an unexpected exception.
    Authorization required:Superuser
    Source: OServer
    Result: request failed
    HTTP status code: 500 Internal Server Error
    User message: Unexpected exception occurred while setting comment
    Solution: Examine OServer's log, if the issue cannot be solved please contact support.
    ROSC-T1-80U [{session_id}] Problem while retrieving GPU list, GPUServer is not available at address: {gpuserver_address}

    Message type:
    error
    Superuser requested to retrieve list of GPUs but GPUServer at address {gpuserver_address} is not available.
    Authorization required:Superuser
    Source: OServer
    Result: retrieve list of the GPUs from other GPUServers, if any
    HTTP status code: depends on other GPUServers availability
    User message: none
    Solution:
    1. Verify if GPUServer is up and running at a specified address, if not - restart GPUServer
      • If GPUServer was started as a service, the # service gpuserver status command must return gpuserver (pid 15870 15779 15762) is running... or similar.
      • If GPUServer was started from command line, issue command $ ps f | grep gpuserver
        12892 pts/2 Sl+ 1:18 /home/bob/gpubox-gpuserver/bin/gpuserver
        12896 pts/2 Sl+ 0:00 /home/bob/gpubox-gpuserver/bin/gpuserver
        13411 pts/2 SLl+ 26:07 /home/bob/gpubox-gpuserver/bin/gpuserver
      In both cases 2 GPUServer's processes must be visible: primary and secondary. In the above exemplary listing:
      • 12892 is a primary GPUServer - root process
      • 12896 is a secondary GPUServer - serves service requests from OServer.
      • 13411 is a subserver - serves GPUBox's clients requests
    2. Verify if secondary server is up and running. Check if GPUServer is listening on the port indicated by the gpuserver_rest_bind parameter: # lsof -Pn -i | grep 8080
    3. Examine OServer's log, when the issue cannot be solved please contact support.
    ROSC-T1-80A [{session_id}] Problem while retrieving GPU list from GPUServer: {gpuserver_hostname}, {return_code}

    Message type:
    error
    Superuser requested to retrieve list of GPUs from GPUServer but GPUServer returned invalid return code.
    Authorization required:Superuser
    Source: OServer
    Result: retrieve list of the GPUs from other GPUServers, if any
    HTTP status code: depends on other GPUServers availability
    User message: none
    Solution:
    ROSC-T1-820 [{session_id}] Failed to parse input data, list of GPUs failed

    Message type:
    error
    OServer detected a syntax error in the input data. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser
    Source: OServer
    User message: none
    Result: retrieve list of the GPUs from other GPUServers, if any
    HTTP status code: depends on other GPUServers availability
    Solution:
    • Verify if the request comes from an authorized GPUBox infrastructure component.
    • If the request comes from the GPUBox package please please contact support.
    ROSC-LP-81U [{session_id}] Problem while retrieving process list, GPUServer is not available at address: {gpuserver_address}

    Message type:
    error
    Superuser requested the list of processes but GPUServer at address {gpuserver_address} is not available.
    Authorization required:Superuser
    Source: OServer
    Result: retrieve list of the processes from other GPUServers, if any
    HTTP status code: depends on other GPUServers availability
    User message: none
    Solution:
    1. Verify if GPUServer is up and running at a specified address, if not - restart GPUServer
      • If GPUServer was started as a service, the # service gpuserver status command must return gpuserver (pid 15870 15779 15762) is running... or similar.
      • If GPUServer was started from command line, issue command $ ps f | grep gpuserver
        12892 pts/2 Sl+ 1:18 /home/bob/gpubox-gpuserver/bin/gpuserver
        12896 pts/2 Sl+ 0:00 /home/bob/gpubox-gpuserver/bin/gpuserver
        13411 pts/2 SLl+ 26:07 /home/bob/gpubox-gpuserver/bin/gpuserver
      In both cases 2 GPUServer's processes must be visible: primary and secondary. In the above exemplary listing:
      • 12892 is a primary GPUServer - root process
      • 12896 is a secondary GPUServer - serves service requests from OServer.
      • 13411 is a subserver - serves GPUBox's clients requests
    2. Verify if secondary server is up and running. Check if GPUServer is listening on the port indicated by the gpuserver_rest_bind parameter: # lsof -Pn -i | grep 8080
    3. Examine OServer's log, when the issue cannot be solved please contact support.
    ROSC-LP-31A [{session_id}] Empty process list from GPUServer: {gpuserver_hostname}

    Message type:
    debug
    GPUServer from {gpuserver_hostname} returned empty list of processes. No users are connected at the moment.
    At the same time GPUServer on host {gpuserver_hostname} returns message GBRS-GU-30A.
    Authorization required:Superuser
    Source: OServer
    Result: retrieve list of the processes from other GPUServers, if any
    HTTP status code: depends on other GPUServers availability
    User message: none
    Solution: none
    ROSC-LP-81A [{session_id}] Problem while retrieving process list from GPUServer: {gpuserver_hostname}, {return_code}

    Message type:
    error
    Superuser requested the list of processes but GPUServer returned invalid return code.
    Authorization required:Superuser
    Source: OServer
    Result: retrieve list of the processes from other GPUServers, if any
    HTTP status code: depends on other GPUServers availability
    User message: none
    Solution:
    ROSC-LP-81P [{session_id}] Failed to parse input data, list of processes from {gpuserver_hostname} failed

    Message type:
    error
    OServer detected a syntax error in the input data. Data received from GPUServer has incorrect format or is damaged.
    Authorization required:Superuser
    Source: OServer
    Result: retrieve list of the processes from other GPUServers, if any
    HTTP status code: depends on other GPUServers availability
    Solution:
    QS1C-AU-75A User {userid} already exists

    Message type:
    warning
    User already exists and cannot be created.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: user is not created.
    Solution: verify if user already exists, if not - please contact support
    QS1C-AU-65A User {userid} created

    Message type:
    notice
    User {userid} has been created.
    Examine previous messages from OServer's log with the same request id to find the origin of the request.
    Newly created user has the following defaults:
    • token is a string of randomly generated 32 characters
    • password is stored as a hash generated from password and userid
    • groupid is 1
    • user is disabled by default
    • user can allocate maximum 4 GPUs
    • user's comment is equal to string '<NA>' by default
    • create timestamp is an inaccessible from the commands
    • 'valid from' timestamp is when account was creation
    • 'valid to' timestamp is 2999-12-12 23:59:59
    • last failure login timestamp is 0001-01-01 01:01:01
    • last successful login timestamp is 0001-01-01 01:01:01
    • number of incorrectly entered passwords is zeroized
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} has been created.
    Solution: none
    QS1C-AU-75B Failed to create user {userid}

    Message type:
    warning
    User could not be created.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: user is not created.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • check if user's name, id and password are correct
    • verify if user not already exists
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-DU-64A User {userid} deleted

    Message type:
    notice
    User {userid} has been deleted.
    Examine previous messages from OServer's log with the same request id to find the origin of the request.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} has been permanently deleted.
    Solution: none
    QS1C-DU-74A Failed to delete user {userid}

    Message type:
    warning
    User could not have been deleted.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: user is not deleted.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • check if {userid} exists
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-SS-75A Failed to change token. User {user1_id} tried to change it on behalf of user {user2_id}

    Message type:
    warning
    Non-superuser {user1_id} tried to change password for user {user2_id}. Authorization required: Superuser
    Source: Security1 plugin
    Result: password for {user1_id} is not changed.
    Solution: Verify if:
    • {user1_id} is superuser i.e. belongs to groupid=0,
    • {user2_id} was given, this can be done via verbose mode in agpubox command or debug web user interface,
    If the cause of the message cannot be found please contact support
    QS1C-TG-54A Token for user {userid} generated by {administrator_userid}, {administrator_username}

    Message type:
    notice
    User {userid} token has been generated by superuser {administrator_userid}.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: token changed
    Solution: user needs to re-login
    QS1C-TG-75A Failed to generate token for user {userid} by {administrator_userid}, {administrator_username}

    Message type:
    warning
    {user2_id} tried to generate token for user {user1_id} but the request failed.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: password for {user1_id} is not changed.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, Client's IP address and their origin
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-GT-73A Unsuccessful login for user {userid}

    Message type:
    warning
    User passed invalid {userid} or password. Authorization token cannot be retrieved.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: login unsuccessful, token was not retrieved
    Solution: login with valid userid and password.
    QS1C-GT-78A Cannot update security information for user {userid}

    Message type:
    error
    User passed invalid {userid} or password. Authorization token cannot be retrieved.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: login unsuccessful, token was not retrieved
    Solution: login with valid userid and password.
    QS1C-GT-70Z User {userid} disabled because of entering incorrect password too many times

    Message type:
    warning
    User entered invalid password 5 times in a row and account {userid} has been disabled.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: account {userid} is disabled
    Solution: depending on security policy:
    • enable user's account
    • consider if disabled account is not a consequence of security attack.
    QS1C-RL-90C Cannot create table tusers, {detailed_message}

    Message type:
    critical
    The plugin Security1 has been started for the first time or the {oserver_security_config} configuration parameter has a new value. The security database has been created but cannot create the tusers table.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: Security1 initialization failed
    Solution:
    QS1C-RL-90D Cannot create index xusers, {detailed_message}

    Message type:
    critical
    The plugin Security1 has been started for the first time or the {oserver_security_config} configuration parameter has a new value. The security database has been created but cannot create xusers index.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: Security1 initialization failed
    Solution:
    QS1C-RL-94B User 'gpubox' already exists

    Message type:
    critical
    The plugin Security1 has been started for the first time or the {oserver_security_config} configuration parameter has a new value. Security database has been successfully initialized but user 'gpubox' already exists.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: Security1 initialization failed
    Solution:
    QS1C-RL-64A Security database initialized with user 'gpubox'

    Message type:
    notice
    The plugin Security1 has been started for the first time or the {oserver_security_config} configuration parameter has a new value and was successfully initialized with the user 'gpubox'.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: Security1's database successfully initialized.
    Solution: none
    QS1C-LU-83A Internal error while retrieving user information

    Message type:
    error
    An error occurred while users' data were being retrieved.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: request is terminated.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • check if {maxgpu} has correct number
    If the cause of the message cannot be found please contact support
    QS1C-LU-33A User not found or security database does not contain any users {userid}

    Message type:
    debug
    Specified {userid} does not exist.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: request terminated
    Solution: specify existing userid
    QS1C-LU-83A List of users is empty

    Message type:
    error
    Cannot retrieve list of all users.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: request terminated
    Solution:
    • Examine previous messages in OServer's log.
    • Verify if database is specified by configuration parameter 'oserver_security_config' exists and can be accessed by OServer.
    • Verify if database is not empty.
    If the cause of the message cannot be found please contact support
    QS1C-SM-54A Comment for user {userid} changed

    Message type:
    information
    Comment for {userid} has been changed.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: comment changed.
    Solution: none
    QS1C-SM-74A Failed to change the comment for user {userid}

    Message type:
    warning
    Failed to change the comment for user {userid}.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: Comment is not changed.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-SG-75E Invalid groupid {groupid}, cannot change for user {userid}

    Message type:
    warning
    Group {groupid} could not have been assigned to user {userid}
    Authorization required: Superuser
    Source: Security1 plugin
    Result: group {groupid} was not assigned to {userid}
    Solution: {groupid} is greater than 1, only two values are accepted:
    • 0 - superuser
    • 1 - regular user
    QS1C-SG-75A Failed to assign user {userid} to group {groupid}

    Message type:
    warning
    Group {groupid} cannot be assigned to user {userid}.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: group {groupid} is not changed for user {userid}.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • check if {groupsid} is correct
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-SG-64E User {userid} becomes an administrator

    Message type:
    notice
    Upon the request, user {userid} became an administrator i.e. was assigned to group=0.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} becomes superuser.
    Solution: none
    QS1C-SG-64F User {userid} is now assigned to {groupid}

    Message type:
    warning
    Upon the request, user {userid} was assigned to group=1 and became a regular user.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} belongs to regular users.
    Solution: none
    QS1C-GM-64A Maximum number of GPUs for user {userid} changed to {maxgpu}

    Message type:
    notice
    Maximum number of GPUs for user {userid} has been set to {maxgpu}.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: Maximum GPU changed set to {maxgpu}
    Solution: none
    QS1C-GM-74C Failed to set maximum number of GPUs {maxgpu} for user {userid}

    Message type:
    warning
    Setting limit of number of GPUs was not possible for user {userid}.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: maximum number of GPU was not set for {userid}.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • check if {maxgpu} has correct number
    If the cause of the message cannot be found please contact support
    QS1C-SP-54A Password for user {userid} changed

    Message type:
    information
    User password has been changed.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: password changed but token left untouched
    Solution: none
    QS1C-SP-75A Failed to change password for user {userid}

    Message type:
    warning
    User's password cannot be changed.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: password is not changed.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, Client's IP address and their origin
    • if possible verify if password has a correct format
    If the cause of the message cannot be found please contact support
    QS1C-SS-64A Password for user {userid} changed by {administrator_userid}, {administrator_username}

    Message type:
    notice
    User {userid} password has been changed by superuser {administrator_userid}.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: password is changed but token is left untouched for {userid}
    Solution: none
    QS1C-SS-75A Failed to change password for user {userid} by {administrator_userid}, {administrator_username}

    Message type:
    warning
    User's password cannot be changed by superuser.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: password is not changed.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • if possible verify if password has correct format
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-SN-54A Username for user {userid} changed

    Message type:
    information
    Username for {userid} has been changed.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: username changed.
    Solution: none
    QS1C-SN-74A Failed to change username for user {userid}

    Message type:
    warning
    Username for user {userid} failed to changed.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: Comment is not changed.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-VF-54A "Valid from" timestamp for user {userid} changed to {validfrom}

    Message type:
    information
    "Valid from" attribute for user {userid} has been changed to {validfrom}.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: "Valid from" changed.
    Solution: none
    QS1C-VF-74A Failed to set "Valid from" timestamp for user {userid}

    Message type:
    warning
    "Valid from" attribute for user {userid} failed to be changed.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: "Valid from" is not changed.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-VT-54A "Valid to" timestamp for user {userid} changed to {validto}

    Message type:
    information
    "Valid to" attribute for user {userid} has been changed to {validto}.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: "Valid to" changed.
    Solution: none
    QS1C-VT-74A Failed to set "Valid to" timestamp for user {userid}

    Message type:
    warning
    "Valid to" attribute for user {userid} failed to changed.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: "Valid to" is not changed.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1D-BS-79Z [{threadid}] {n}th time of claiming db access

    Message type:
    warning
    Thread {threadid} has been trying to get an access {n} times but the database is locked.
    This message is shown after 50th unsuccessful access attempt to the database and shows every 10th attempt.
    The thread will keep on retrying in every 0.5sec.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: thread access to the database is blocked
    Solution:
    • Examine {detailed_message} to find the cause of the issue. Possibly there are too many requests per second.
    • If the problem repeats please contact support.
    QS1C-UD-64A User {userid} disabled

    Message type:
    notice
    {userid} is disabled. Previous messages from OServer's log with the same request id shows the origin of the request.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} is disabled.
    Solution: none
    QS1C-UE-74A User {userid} cannot be disabled

    Message type:
    warning
    {userid} failed disable.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} is not disabled but user could have been disabled by previous requests. This request does not check if user is already disabled.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, client's IP address and their origin
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-UE-64A User {userid} enabled

    Message type:
    notice
    {userid} is enabled. Previous messages from OServer's log with the same request id shows the origin of the request.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} is enabled, previous number of incorrect login tries is zeroized.
    Solution: none
    QS1C-UE-74A User {userid} cannot be enabled

    Message type:
    warning
    {userid} failed to enable.
    Authorization required: Superuser
    Source: Security1 plugin
    Result: {userid} is not enabled but user could be enabled be previous requests i.e. this request does not check if user is already enabled.
    Solution: try to examine messages with the same request ID in OServer's log and take a look at:
    • request details i.e. type and name
    • userid, Client's IP address and their origin
    • whether requestor is superuser and has required privileges i.e. belongs to groupid=1
    If the cause of the message cannot be found please contact support
    QS1C-VT-74A Invalid token given

    Message type:
    warning
    An invalid token was passed by user. It was specified with [agpubox] or [gpubox] command or from web user interface.
    There are several possible reasons of an invalid token.
    1. User generated new token but did not save the configuration file
    2. User generated new token from web user interface but token could not have been saved from web browser.
    3. User is disabled (locked).
    4. User's account properties 'valid from' and/or 'valid to' is out of date.
    Authorization required: Superuser or regular user
    Source: Security1 plugin
    Result: request is terminated.
    Solution: Examine messages in OServer's log with the same request ID and verify the source or request i.e. userid, username and client's IP address. Check possible reasons and apply one of the solutions: 1. Re-login user with regenerated token.
    2. Re-login user with regenerated token from command line.
    3. Enable user.
    4. Change user's account properties 'valid from' and/or 'valid to' accordingly to current date and time.
    Token from database must match token in user's configuration file:
    • in Linux operating systems: $HOME/.gpubox
    • in Windows: LOCALAPPDATA%.gpubox
    OSRV-OH-76D [{pid}] OServer received unexpected exception {signal_name}({signal_number})

    Message type:
    warning
    OServer received a signal {signal_name} and took a suitable action.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: Depends on signal OServer:
    • SIGQUITE: force to quite, OServer will be terminated,
    • SIGINT, SIGTERM: OServer will be terminated in normally,
    • SIGFPE, SIGILL, SIGSEGV, SIGBUS, SIGABRT, SIGTRAP, SIGSYS: OServer will be terminated immediately.
    Any other signals are ignored.
    Solution:
    OSRV-OH-77X [{pid}] OServer has {active_connections} active requests, shutdown pending, please wait...

    Message type:
    warning
    OServer receive SIGINT or SIGTERM signal but still has active requests. The shutdown of OServer will continue when all requests are served.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: OServer continue processing until all requests are active
    Solution: Administrator can send SIGQUIT signal to abandon active request and terminate the OServer immediately.
    OSRV-OH-77C [{pid}] OServer received forced-stop (SIGQUIT)

    Message type:
    warning
    OServer received a signal SIGQUIT and will skip the entire shutdown sequence.
    Only log file is closed or other activities are abandoned.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: OServer is being terminated
    Solution: Verify why the OServer was forced to stop.
    OSRV-OH-66C [{pid}] OServer stopped

    Message type:
    notice
    The OServer has been stopped.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: OServer is about to stop and it returns code 2.
    Solution: none
    OSRV-OH-76A [{pid}] OServer received {signal} and it is already stopping, please wait, {termination_count}

    Message type:
    warning
    The OServer received the SIGQUIT, SIGINT or SIGTERM signal and it is being terminated.
    • {signal} - signal number.
    • {termination_count} number of termination calls while OServer is being terminated.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: OServer is being terminated.
    Any other signals are ignored.
    Solution:
    • Wait until the OServer terminates or
    • Send the SIGQUIT signal - if it does not help send the SIGKILL signal.
    OSRV-OH-76C [{pid}] OServer received the stop signal (SIGINT or SIGTERM)

    Message type:
    warning
    The OServer received the SIGINT or SIGTERM signal and will begin the normal shutdown sequence.
    Authorization required:Superuser or regular user
    Source: OServer
    Result: OServer is being terminated
    Solution: none