Skip to content

Outputting information to logs#

This section describes additional information that can help you when working with FaceStream logs or the logs of the services required for it.

FaceStream log output format#

FaceStream logs have the following format:

I0317 16:27:07.375125    57 LunaBaseClient.cpp:45] [client] Request

Where:

  • I0317:

    • I - logging level. 4 levels can be displayed in the logs - I (Info), W (Warning), E (Error), F (Fatal). If necessary, you can set the logging level (see "severity" parameter);
    • 0317 - day and month, i.e. March 17.

  • 16:27:07.375125 - timestamp.

  • 57 - process PID ID.

  • LunaBaseClient.cpp - file name that caused this log line to occur.

  • 45 - log string number.

  • [client] - tag associated with logging the relevant information (see "tags" parameter).

  • Request - description of the log string.

FaceStream errors are not covered in this section.

Additional services API errors#

This section describes the errors returned by the LUNA Streams and LUNA Licenses services, as well as general errors that may occur when interacting with these services. Each of the errors has a unique code. It is convenient to use it to find an error.

The errors can have different reasons.

In case of “Internal server error” or any other unexpected error occurrence, it is recommended to check service logs to find out more information about the error.

General errors#

Code 0 returned#

Error Message:

Success

Error source:

General errors

Error Description:

This code is returned when there are no errors and the request is successfully processed.

Note that the result may still contain images filtered according to the parameters defined in the request.

Code 1 returned#

Error Message:

Internal server error. Unknown error

Error source:

General errors

Error Description:

An unexpected internal error occurred. The error is not properly processed in the code.

If any additional trace is provided and the error continues to appear, send the trace to VisionLabs technical support.

Code 3 returned#

Error Message:

Invalid url {value}

Error source:

General errors

Error Description:

Invalid URL was specified in the request.

Check the URL in the request. It may contain spaces or erroneous symbols.

Check API specification for the examples of the URL.

Code 4 returned#

Error Message:

Client payload error {value}

Error source:

General errors

Error Description:

Client payload error.

Possible causes: the response object was closed before the response received all data. A transfer encoding error occurred.

Code 5 returned#

Error Message:

Server fingerprint mismatch {value}

Error source:

General errors

Error Description:

Server fingerprint error.

An attempt to connect to an invalid server was performed or an invalid key was used.

Code 6 returned#

Error Message:

Socket read timeout. Request timeout on {value} method {value}

Error source:

General errors

Error Description:

Socket reading error. Request completion time limit exceeded.

The problem may occur due to the following reasons:

  • Problems in the network. Check network.

  • Internal server errors. Check service logs.

Code 7 returned#

Error Message:

Socket connect timeout Request timeout on {value} method {value}

Error source:

General errors

Error Description:

Socket connection error. Request completion time limit exceeded.

The request may take long due to the following reasons:

  • Problems in the network. Check network.

  • Internal server errors. Check service logs.

  • High service load.

Code 8 returned#

Error Message:

Connect timeout on {value} method {value}

Error source:

General errors

Error Description:

Connection error. The connection time limit was exceeded.

The problem may occur due to the following reasons:

  • Problems in the network. Check network.

  • Service is unavailable. Check that the service is running and check its logs.

Code 9 returned#

Error Message:

Request timeout on {value} method {value}

Error source:

General errors

Error Description:

Connection error. Request completion time limit exceeded.

The problem may occur due to the following reasons:

  • Problems in the network. Check network.

  • Service is unavailable. Check that the service is running and check its logs.

Code 10 returned#

Error Message:

Server disconnected {value}

Error source:

General errors

Error Description:

The connection with the server is lost.

The problem may occur due to the following reasons:

  • Problems in the network. Check network.

  • Server is unavailable. Check that the server is running.

Code 11 returned#

Error Message:

Server connection error {value}

Error source:

General errors

Error Description:

Server connection error.

The connection with the server is lost.

The problem may occur due to the following reasons:

  • Problems in the network. Check network.

  • Server is unavailable. Check that the server is running.

Code 12 returned#

Error Message:

Client proxy connection error {value}

Error source:

General errors

Error Description:

Client proxy connection error.

The problem may occur due to the following reasons:

  • Problems in the network. Check network.

  • Proxy connection is unavailable.

Code 13 returned#

Error Message:

Client connector SSL error {value}

Error source:

General errors

Error Description:

Client connection via SSL error. Check SSL certificate.

Code 14 returned#

Error Message:

Client connector certificate error {value}

Error source:

General errors

Error Description:

Client SSL error.

Possible causes are: invalid SSL certificate, outdated client SSL version. Check SSL certificate.

Code 15 returned#

Error Message:

Client SSL error {value}

Error source:

General errors

Error Description:

Client SSL error.

Possible causes are: invalid SSL certificate, outdated client SSL version. Check SSL certificate.

Code 16 returned#

Error Message:

Client connector error {value}

Error source:

General errors

Error Description:

Client connection error.

Code 17 returned#

Error Message:

Client OS error {value}

Error source:

General errors

Error Description:

The error in the client operating system occurred.

Check the client OS.

Code 18 returned#

Error Message:

Client connection error {value}

Error source:

General errors

Error Description:

Client connection error.

Code 19 returned#

Error Message:

Client HTTP proxy error {value}

Error source:

General errors

Error Description:

The HTTP proxy server error has occurred on the client-side.

Code 21 returned#

Error Message:

Content-Type error {value}

Error source:

General errors

Error Description:

Request content-type error. Invalid value in "Content-Type" field in the request header parameters. It does not match with the data provided in the request.

Check the "HEADER PARAMETERS" section in the API documentation for your request.

Code 22 returned#

Error Message:

Client response error {value}

Error source:

General errors

Error Description:

The client response error occurred.

Code 23 returned#

Error Message:

HTTP client error {value}

Error source:

General errors

Error Description:

Client HTTP error.

Code 24 returned#

Error Message:

HTTP client error {value}

Error source:

General errors

Error Description:

Client HTTP error. The response was received in incorrect JSON format.

Code 11055 returned#

Error Message:

Forbidden. License problem: ‘{value}’

Error source:

General errors

Error Description:

License error. The license has expired or is unavailable.

CORE errors, returned in API responses#

Code 100 returned#

Error Message:

Bad/incomplete configuration. {value}

Error source:

CORE errors, returned in API responses

Error Description:

Cannot read the configuration file.

The error may occur due to:

  • Invalid configuration file name or format.
  • Invalid parameter name or parameter format.
  • Required parameter is missed in the configurations.

Check the configuration file of the service.

  • If you are using configuration files, check configuration files in the service directory. The /srv/luna_/configs/config.conf path is used inside Docker container.

  • If you are using the Configurator service, check the corresponding settings in it.

Code 101 returned#

Error Message:

Bad/incomplete query {value}

Error source:

CORE errors, returned in API responses

Error Description:

Invalid request parameters are set or mandatory parameters are absent.

One or several query parameters are misspelled or missed. Invalid values may be set to the query parameters.

Code 102 returned#

Error Message:

Bad/incomplete body {value}

Error source:

CORE errors, returned in API responses

Error Description:

Invalid request body.

There is an error in the request body or it does not match the required schema.

See "REQUEST BODY SCHEMA" in the API documentation and compare it with the specified one.

Code 105 returned#

Error Message:

Out of memory {value}

Error source:

CORE errors, returned in API responses

Error Description:

Not enough memory for the request processing.

Check the server memory usage. It may be required to increase the server memory.

Code 106 returned#

Error Message:

Invalid http request {value}

Error source:

CORE errors, returned in API responses

Error Description:

Invalid HTTP request.

Make sure the request URL and method (POST, GET, etc.) are correct.

Code 200 returned#

Error Message:

Generic error {value}

Error source:

CORE errors, returned in API responses

Error Description:

Generic error: invalid parameter, logical errors.

The problem may appear due to various reasons. Check that the request to the system is correct in the API documentation.

Database Errors#

Code 10015 returned#

Error Message:

SQL error. SQL request execution failed

Error source:

Database Errors

Error Description:

SQL request failed. A database error has occurred.

The database is not available for an unknown reason, or the required tables are missing. You should request the status of the database, check the availability of the database over the network, check the existence of the required tables in the database.

Code 10016 returned#

Error Message:

Database error. Could not connect to database

Error source:

Database Errors

Error Description:

The connection to the database failed.

Check that the database is available. There may be errors during database launch or it is not available in the current network (due to server restrictions or network problems). Check the database settings in services parameters. They may be incorrect.

Code 10017 returned#

Error Message:

Database error Database connection timeout error

Error source:

Database Errors

Error Description:

Database connection timeout error.

Check that the database is available. There may be errors during database launch or it is not available in the current network (due to server restrictions or network problems). Check the database settings in services parameters. They may be incorrect.

Code 10018 returned#

Error Message:

Database error {value}

Error source:

Database Errors

Error Description:

An error occurred in the database. Check the provided description of the error.

REST API common errors#

Code 12001 returned#

Error Message:

Bad/incomplete input data. Object in query is not UUID4 format: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx

Error source:

REST API common errors

Error Description:

The provided ID for the object is not in UUID4 format. Check that the provided IDs are correct.

Code 12002 returned#

Error Message:

Bad/incomplete input data. Request does not contain json

Error source:

REST API common errors

Error Description:

The request does not contain JSON.

Check the JSON syntax in the request body:

  • There are extra symbols or spaces.
  • The JSON structure is wrong.
  • Important syntax elements were missed

Code 12003 returned#

Error Message:

Bad/incomplete input data. Field. {value} not found in json

Error source:

REST API common errors

Error Description:

The specified field was not found in the JSON body. Check that all required fields were added to the request.

Code 12005 returned#

Error Message:

Bad/incomplete input data. Request contain empty json

Error source:

REST API common errors

Error Description:

The request contains an empty JSON body. A body is required to execute the request.

Code 12012 returned#

Error Message:

Bad/incomplete input data. Bad query parameters {value}

Error source:

REST API common errors

Error Description:

The specified query parameters are set incorrectly.

Code 12013 returned#

Error Message:

Resource not found. Page not found

Error source:

REST API common errors

Error Description:

The HTTP resource was not found.

The URL specified in the request was not found.

For example, the request contains the path "/6/sample" instead of "/6/samples". Compare the specified path with the path in the documentation.

Code 12014 returned#

Error Message:

Bad/incomplete input data. Required parameters {value} not found

Error source:

REST API common errors

Error Description:

The required query parameters were not found in the request. These parameters are listed in the error.

Code 12016 returned#

Error Message:

Bad/incomplete input data. No one parameters {value} not found

Error source:

REST API common errors

Error Description:

Listed query parameters were not found in the request.

Code 12017 returned#

Error Message:

Bad/incomplete input data. Bad content type

Error source:

REST API common errors

Error Description:

Invalid "Content-Type" header value transmitted in the request.

No header was specified, an invalid header value was specified, or there is a mistake in the header.

Code 12018 returned#

Error Message:

Bad/incomplete input data. Unsupported param ‘{value}’

Error source:

REST API common errors

Error Description:

The query parameter is unsupported.

Code 12021 returned#

Error Message:

Method not allowed. Method not allowed

Error source:

REST API common errors

Error Description:

The HTTP resource does not support this method. Check the HTTP method specified to send the request.

Code 12022 returned#

Error Message:

Bad/incomplete input data. Failed to validate input json. Path: ‘{value}’ message: ‘{value}’

Error source:

REST API common errors

Error Description:

There is an error in JSON syntax at the specified path.

The request body contains invalid fields. Check the request for compliance with the template specified the API documentation for the request.

Code 12023 returned#

Error Message:

Bad/incomplete input data. Content type is unacceptable allowed types: ‘{value}’

Error source:

REST API common errors

Error Description:

The request contains invalid "content-type". Most likely, there is a typo in the request content-type.

See the API documentation for the request. Check the available content types.

Code 12024 returned#

Error Message:

Bad/incomplete input data. Unsupported media type

Error source:

REST API common errors

Error Description:

The data type transmitted in the request is not supported.

See the API documentation for the request. Check the content type available for the request.

Code 12025 returned#

Error Message:

Bad/incomplete input data. Specified content type does not match data type

Error source:

REST API common errors

Error Description:

The content-type specified in the "Content-Type" header does not match the data type.

See the API documentation for the request. Check the available content types.

Code 12027 returned#

Error Message:

Bad/incomplete input data. Failed to validate input json. Message: {value}

Error source:

REST API common errors

Error Description:

The request body parameters are incorrect. Check the JSON body for compliance with the request requirements. Details are listed in the "Message:" field.

Check the "REQUEST BODY SCHEMA" of the request. See the examples provided for the request in the documentation.

Code 12028 returned#

Error Message:

Bad/incomplete input data. Failed to parse Flatbuf

Error source:

REST API common errors

Error Description:

Internal error. Failed to deserialize Flatbuf.

Code 12029 returned#

Error Message:

Functionality is not implemented. Required server functionality is not implemented

Error source:

REST API common errors

Error Description:

The error is returned for the server functionality that is not implemented.

Code 12030 returned#

Error Message:

Bad/incomplete input data. Request does not contain data

Error source:

REST API common errors

Error Description:

The request contains no data. The request body is empty.

Check the "REQUEST BODY SCHEMA" of the request and other request parameters. See the examples provided for the request in the documentation.

Code 12031 returned#

Error Message:

Bad/incomplete input data. {value}

Error source:

REST API common errors

Error Description:

The input data is incomplete or wrong.

The detailed description of the error is given in the field "message".

Code 12032 returned#

Error Message:

Internal server error. Document file not found

Error source:

REST API common errors

Error Description:

The document with the specified name was not found. The error is returned when requesting service documentation.

Check that the request is correct and the document name is set properly.

Code 12033 returned#

Error Message:

Forbidden. Access to this resource on the server is denied

Error source:

REST API common errors

Error Description:

The access to the resource on the server is denied.

Check the resource availability. The access to the service may be restricted in the server settings.

Code 12034 returned#

Error Message:

Bad/incomplete input data. Descriptor has incorrect length {value}

Error source:

REST API common errors

Error Description:

The descriptor has an incorrect length.

Make sure that you are using a descriptor of the appropriate format. Descriptors received from different sources may have different lengths.

Code 12035 returned#

Error Message:

Bad/incomplete input data. Failed to parse xpk file

Error source:

REST API common errors

Error Description:

Failed to parse the descriptor XPK file. Check that the file is correct.

Code 12036 returned#

Error Message:

Bad/incomplete input data. Descriptor version {value} is not registered in the system

Error source:

REST API common errors

Error Description:

The specified descriptor version is not registered in the system.

A wrong/nonexistent descriptor version is set, or an incompatible service version is used that cannot process this descriptor version.

Check that you use a proper descriptor version.

Code 12037 returned#

Error Message:

Bad/incomplete input data. XPK file does not contain descriptor

Error source:

REST API common errors

Error Description:

The input data XPK does not contain a descriptor. Check that the file is correct.

Code 12038 returned#

Error Message:

Bad/incomplete input data. SDK descriptor is not valid

Error source:

REST API common errors

Error Description:

SDK descriptor is not valid. Check the provided descriptor data.

Make sure that you are using a descriptor of the appropriate format. Descriptors received from different sources may have different lengths.

Code 12039 returned#

Error Message:

Bad/incomplete input data. Unknown multipart name ‘{value}’

Error source:

REST API common errors

Error Description:

There is an unknown multipart name in the request. Check that the name in the "message" field is correct.

Code 12040 returned#

Error Message:

Bad/incomplete input data. Duplicate multipart name ‘{value}’

Error source:

REST API common errors

Error Description:

There is a duplicated multipart name in the request. Check the name in the "message" field. Duplacate names are not available.

Code 12041 returned#

Error Message:

Bad/incomplete input data. Multipart with name ‘{value}’ has bad Content-Type

Error source:

REST API common errors

Error Description:

The input data with the specified name has bad Content-Type in the multipart request. Check the specified content type.

Code 12042 returned#

Error Message:

Gone. Access to this resource on the server is no longer available

Error source:

REST API common errors

Error Description:

The access to the resource on the server is not available. Check that the corresponding service is working, has correct version and is available. Check that the resource is correct.

Code 12043 returned#

Error Message:

Unknown error. Service ‘{value}’ unknown error method: ‘{value}’ url: ‘{value}’

Error source:

REST API common errors

Error Description:

Unknown service error has occurred. Check the method and URL provided in the error message.

Code 12044 returned#

Error Message:

Bad/incomplete input data. Failed to decompress input body using gzip encoder

Error source:

REST API common errors

Error Description:

Failed to decompress input body using GZIP encoder.

Code 12045 returned#

Error Message:

Bad/incomplete input data. Failed to decompress input body using deflate encoder

Error source:

REST API common errors

Error Description:

Failed to decompress input body using deflate encoder.

LUNA Licenses service errors#

Code 33001 returned#

Error Message:

License problem Failed to check HASP License feature {value}

Error source:

LUNA Licenses service errors

Error Description:

A license problem occurred. The request for the feature availability failed. Check your license.

Possible reasons: the license was not applied, you use a wrong license, connection to the license server could not be established.

Code 33002 returned#

Error Message:

License problem Failed to get value of HASP License feature {value}

Error source:

LUNA Licenses service errors

Error Description:

A license problem occurred. The request for the feature value failed. Check your license. Possible reasons: the license was not applied, you use a wrong license, connection to the license server could not be established.

Code 33003 returned#

Error Message:

License problem No value found for required HASP License feature {value}

Error source:

LUNA Licenses service errors

Error Description:

A license problem occurred. The license does not include required feature.

Possible reasons:

  • The required feature was not added to the license.
  • A wrong license is used. A wrong license file was applied.
  • A new license was not applied.
  • Connection to the license server could not be established.

Code 33004 returned#

Error Message:

License problem Failed to consume {value}

Error source:

LUNA Licenses service errors

Error Description:

The specified licensed LP feature cannot be used because the limit on the number of transactions was exceeded. Check your license.

Code 33005 returned#

Error Message:

License problem Failed to consume : license expired

Error source:

LUNA Licenses service errors

Error Description:

The specified licensed LP feature cannot be used because the license has expired.

Check your license.

LUNA Streams service errors#

Code 39001 returned#

Error Message:

Object not found Stream with id {value} not found

Error source:

LUNA Streams service errors

Error Description:

The stream with the specified ID was not found. Make sure that the existing "steam_id" is set. You can get a list of existing "stream_id" by using a GET request to the "/streams" resource.

Code 39002 returned#

Error Message:

Bad input data ‘{value}’ is not valid stream status; permitted: {value}.

Error source:

LUNA Streams service errors

Error Description:

When creating the stream, an incorrect status was entered in the "status" field. You can set only two statuses - "pause" and "pending". The rest of the statuses can be obtained only at a certain point in time (see the section "Statuses transition table"). The error description shows the expected status.

Code 39003 returned#

Error Message:

Unable to stop processing Processing of stream with id ‘{value}’ is already in progress and cannot be stopped.

Error source:

LUNA Streams service errors

Error Description:

It is not possible to set the "pause" status for the specified "stream_id", since processing has already started (relevant only for video files).

Code 39004 returned#

Error Message:

Bad input data ‘{value}’ is not valid stream log target; permitted: {}.

Error source:

LUNA Streams service errors

Error Description:

A non-existent value of the "targets" parameter is specified in the "/streams/logs" request to receive logs.

Code 39005 returned#

Error Message:

Unable to cancel processing Processing of stream with id ‘{value}’ is finished and cannot be cancelled

Error source:

LUNA Streams service errors

Error Description:

It is not possible to set the "cancel" status for the specified "stream_id", because processing has already been finished.