http.violation 1

This message indicates that the request method sent by the client is invalid.

http.violation 1

This message indicates that the URL sent by the client is invalid.

http.violation 1

This message indicates that the protocol version sent by the client is invalid.

http.request 6

This message reports the processed request details.

http.response 6

This message indicates that the server sent an invalid response status line.

http.violation 1

This message indicates that the protocol version sent by the server is invalid.

http.violation 1

This message indicates that the response code sent by the server is invalid.

http.response 7

This message reports the processed response details.

http.request 3

This message indicates that the protocol version sent by the client is unsupported.

http.response 3

This message indicates that the protocol version sent by the server is unsupported.

http.error 2

This message indicates that Vela caught an invalid error code internally. Please report this event to the BalaSys Development Team (at devel@balasys.hu).

http.debug 6

This message reports that Vela is sending the given error page to the clients browser. It is likely that some protocol/configuration/proxy error occurred.

http.error 1

This message reports that Vela was about to write to an invalid stream. Please report this event to the BalaSys Development Team (at devel@balasys.hu).

http.error 1

This message reports that Vela was unable to write to the given stream. It is likely that the peer closed the connection unexpectedly.

http.error 3

This message indicates that the client tried to use the given unsupported HTTP authentication. Currently only Basic HTTP authentication is supported by Vela.

http.violation 1

This message indicates that the client sent a malformed username:password field, during the authentication phase.

http.violation 2

This message indicates that the username:password field received during authentication was malformed.

http.violation 2

This message indicates that the client sent an invalid HTTP request to the proxy.

http.violation 1

This message indicates that the client sent a CONNECT method request, but it is only supported for HTTP/1.0 or later.

http.policy 2

This message indicates that the client sent the given type request, which is not permitted by the policy. Check the permit_proxy_requests and the permit_server_requests attributes.

http.violation 4

This message indicates that no Host header was sent by the client. As the content of the host header is used to reconstruct the requested URL, the request_url attribute will refer to a host named 'unknown'.

http.policy 2

This message indicates that an HTTP/0.9 request was sent by the client, and Host header is required by the policy, but HTTP/0.9 does not support headers. Check the require_host_header attribute.

http.policy 2

This message indicates that no Host header was sent by the client, but it was required by the policy. Check the require_host_header attribute.

http.error 1

This message indicates that there was an error parsing an already canonicalized URL. Please report this event to the BalaSys Development Team (at devel@balasys.hu)

http.policy 2

This message indicates that a client tried to use FTP over HTTP which is not allowed by default. Either set a parent proxy or enable the permit_ftp_over_http attribute.

http.error 3

This message indicates that the requested URL refers to an unsupported protocol scheme. Vela currently knows about http and cache_object protocols, and can support the ftp protocol if a parent_proxy supporting ftp over http tunneling is present.

http.policy 2

This message indicates that the HTTP request was rejected because the hostname part in the URL was too long. You can increase the permitted limit by changing the max_hostname_length attribute.

http.accounting 4

This is an accounting message that reports the requested method and URL.

http.policy 1

This message indicates that the request hash contains an invalid item for the given request method. Check your Vela configuration.

http.policy 1

This message indicates that the request hash contains an invalid POLICY tuple for the given request method. It should contain a valid call-back function in the tuple.

http.policy 1

This message indicates that the request hash contains an invalid REJECT tuple for the given request method. It should contain an error message, which is sent back to the client.

http.policy 1

This message indicates that the request hash contains an invalid action for the given request method. Check your Vela configuration.

http.policy 6

This log message indicates that the policy requested a custom response to be sent to the client.

http.policy 2

This log message indicates that the specified HTTP request was not permitted by your policy.

http.violation 2

This message indicates that the proxy did not allow addressing the specified port as the target_port_range attribute does not allow it.

http.error 1

This message indicates that initializing the server stream failed. Please report this event to the BalaSys Development Team (at devel@balasys.hu).

http.error 2

This message indicates that Vela was unable to enable HTTP/0.9 compatibility mode, due to the full buffer. If you experience this problem many times, please contact your Vela support.

http.policy 2

This message indicates that the server sent back HTTP/0.9 response, which is prohibited by the policy. It is likely a buggy or old server. Check the permit_http09_responses attribute.

http.violation 1

This message indicates the the HTTP status line returned by the server was invalid.

http.violation 1

This message indicates that the server sent the response with an invalid HTTP version. It is likely that the server is buggy.

http.violation 1

This message indicates that the server sent an unsupported protocol version. It is likely that the server is buggy.

http.policy 1

This message indicates that the response hash contains an invalid item for the given response. Check your Vela configuration.

http.policy 1

This message indicates that the response hash contains an invalid POLICY tuple for the given response. It should contain a valid call-back function in the tuple.

http.policy 1

This message indicates that the response hash contains an invalid REJECT tuple for the given response. It should contain an error message, which is sent back to the client.

http.policy 1

This message indicates that the response hash contains an invalid action for the given response. Check your Vela configuration.

http.policy 2

This message indicates that the status code returned by the server is not a permitted response code for this request.

http.violation 1

This message indicates that the received CONNECT request did not include a port number to connect to.

http.error 1

This message indicates that the our parent proxy refused our CONNECT request. It is likely that the parent proxy does not permit CONNECT method.

http.debug 6

This message reports that CONNECT method is in use, and CONNECT method was accepted by out parent proxy.

http.error 1

This message indicates that an internal error occurred, the connectMethod function did not return an integer. Please report this event to the BalaSys Development Team (at devel@balasys.hu).

http.debug 6

This message reports that Vela is fetching the request and the headers from the client.

http.debug 6

This message reports that Vela is processing the fetched request and the headers.

http.policy 3

This message reports that the maximum number of requests in a keep-alive loop is reached, and Vela is closing after this request. Check the max_keepalive_request attribute.

http.debug 6

This message reports that Vela is filtering the processed request and the headers.

http.debug 6

This message indicates that Vela is rechecking the HTTP request after possible changes performed by the policy layer.

http.debug 6

This message reports that Vela is sending the filtered request and headers, and copies the requests data to the server.

http.debug 6

This message reports that Vela is fetching the response and headers from the server.

http.debug 6

This message reports that Vela is processing the fetched response and the headers.

http.debug 6

This message reports that Vela is filtering the processed response and the headers.

http.debug 6

This message reports that Vela is sending the filtered response and headers, and copies the response data to the client.

core.error 1

This message indicates an internal error in HTTP proxy. Please report this event to the BalaSys Development Team (at devel@balasys.hu).

http.debug 6

This message reports that Vela is exiting the keep-alive loop and closing the connection.

http.violation 2

This message indicates that the response given by the FTP server was too short, not even the mandatory status code was included.

http.violation 2

This message indicates that the FTP server gave an invalid response, the status code returned by the server was not numeric.

http.violation 2

This message indicates that the FTP server gave an invalid response as the status code changed from the one which was present on the first line.

http.error 4

This message indicates that the FTP server returned an unknown status code in response to our login request.

http.error 4

This message indicates that the FTP refused our authentication attempt.

http.error 3

This message indicates that the FTP server greeted Vela with a non-220 response code.

http.error 4

This message indicates that the directory specified in the URL was not accepted by the FTP server.

http.error 4

This message indicates that an I/O error occurred while sending our RETR or LIST request.

http.error 4

This message indicates that an I/O error occurred while trying to establish the data connection with the FTP server.

http.error 4

This message indicates that the FTP server did not react with a 150 response after the data connection was established.

http.error 4

This message indicates that the FTP server did not return with an appropriate status code at the end of the data transfer.

http.policy 1

This message indicates that the HDR_CHANGE_NAME parameter is invalid, for the given header. Check your request_header_policy and response_header_policy hashes.

http.policy 1

This message indicates that the HDR_CHANGE_VALUE parameter is invalid, for the given header. Check your request_header_policy and response_header_policy hashes.

http.policy 1

This message indicates that the HDR_CHANGE_BOTH parameter is invalid, for the given header. Check your request_header_policy and response_header_policy hashes.

http.policy 1

This message indicates that the action is invalid, for the given header. Check your request_header_policy and response_header_policy hashes.

http.error 3

This message indicates that Vela was unable to fetch headers from the server. Check the permit_null_response attribute.

http.violation 2

This message indicates that Vela fetched an invalid header from the server. It is likely caused by a buggy server.

http.violation 2

This message indicates that the server sent an invalid HTTP header.

http.policy 2

This message indicates that the server tried to send more header lines, than the allowed maximum. Check the max_header_lines attribute.

http.violation 1

This message indicates that the chunk length line is too long. It is likely caused by a buggy client or server.

http.violation 1

This message indicates that the chunk length is invalid. It is likely caused by a buggy client or server.

http.policy 2

This message indicates that the length of the chunk is larger than allowed or is a negative number. Check the 'max_chunk_length' attribute.

http.violation 1

This message indicates that Vela unexpectedly got EOF during chunk encoded data transfer. It is likely a caused by a buggy client or server.

http.violation 1

This message indicates that the chunk footer contains data. It is likely caused by a buggy client or server.

http.debug 6

This message reports that the stacked proxy sent a content-length hint on how much data will be sent and the http proxy is using it to set the Content-Length header.

http.policy 3

This message indicates that the request_stack or response_stack hash contains an invalid stacking tuple. It should contain a (stack_type, proxy_class) tuple. Check your Vela configuration.

http.policy 3

This message indicates that the request_stack or response_stack hash contains an invalid stacking type. Check your Vela configuration.

http.violation 1

This message indicates that the Content-Length headers value is not a valid number. It is likely caused by a buggy client or server.

http.error 2

This message indicates that the processed request was invalid, and the data transfer failed.

http.error 2

This message reports that the data transfer failed.

http.info 2

This message indicates that the stacked proxy returned the specified verdict about the content. Check the stacked proxy log for further information.

http.info 5

This message reports that the stacked proxy sent an error hint on how the parent proxy should present the reject verdict towards the client.

http.info 4

This message reports that the stacked proxy sent an error info string on how the parent proxy should present the reject verdict reason towards the client.

http.info 5

This message reports that the stacked proxy has not sent an indication on how the parent proxy should present the reject verdict reason towards the client.

http.debug 6

This message indicates that the stacked proxy accepted the content.

telnet.violation 1

This message indicates that the Telnet protocol contained a sequence of protocol elements that would have needed an unreasonably large buffer to process. These structures are not commonly found in normal Telnet streams but could be used to mount a denial of service attack on a Telnet client or server by a malicious host.

plug.policy 1

This message is logged when the policy layer returned a non-integer value in its packetStats() function. packetStats() is expected to return VV_REJECT or VV_ACCEPT.

plug.policy 1

This message indicates that the verdict returned by the packetStats() function requests to terminate the session.

ldap.policy 6

Too many SearchResultEntry message arrived for the corresponding request, and the required action is LDAP_RSP_DROP

ldap.policy 3

Too many SearchResultEntry message arrived for the corresponding request, and the required action is LDAP_RSP_ABORT

ldap.error 3

response_overrun_action may contain other values than LDAP_RSP_DROP and LDAP_RSP_ABORT, in this case the assumed value is LDAP_RSP_DROP

mime.policy 1

This message appears when policy level is too deep. Maybe looping.

mime.policy 1

This message appears when vela cannot parse the policy line.

mime.policy 1

This message appears when vela cannot parse the policy line.

mime.policy 1

This message appears when vela cannot call the given policy function.

mime.policy 5

This message appears when vela cannot found what to do with a command.

mime.policy 5

This message appears when vela cannot found what to do with a command answer.

mime.policy 1

This message appears when vela cannot parse the policy line.

mime.policy 1

This message appears when vela cannot parse policy line.

mime.policy 1

This message caused by an exception in python.

mime.policy 1

This message appears when vela cannot parse policy return value.

mime.policy 5

This message appears when vela cannot found what to do with a command.

mime.policy 1

This message appears when called policy function return with wrong value.

imap.error 1

This message appears, when Vela cannot find a literal in message rebuilding.

imap.error 1

This message indicates an internal error where there are too many literals.

imap.error 2

This message indicates an error occurred while writing the policy response lines.

imap.error 3

This message indicates an error occurred while writing the final policy response after processing the IMAP command.

imap.violation 2

This message indicates a violation of the IMAP protocol where a command could not be parsed from the client's request line.

imap.error 2

This message indicates an error while writing the error response to the client.

imap.debug 6

This message indicates the successful reconstruction of the client's request.

imap.violation 2

This message indicates a violation of the IMAP protocol where an illegal tag is encountered in the client's command.

imap.violation 2

This message indicates that a duplicate tag was encountered in the client's request. It provides details about the duplicate tag and the corresponding previous request.

imap.policy 2

This message indicates that the requested command is not allowed in the current state of the IMAP proxy.

imap.violation 2

This message indicates a syntax error while parsing the client's command.

imap.policy 3

This message indicates that the requested command is denied by the policy.

imap.policy 3

This message indicates that the IMAP proxy is dropping the request without processing it further.

imap.policy 4

This message indicates that the IMAP proxy is responding to the client based on policy rules.

imap.policy 3

This message indicates that the IMAP proxy is aborting the connection due to the client's request.

imap.policy 3

This message indicates that there are too many pending requests and the IMAP proxy cannot handle more.

imap.error 2

This message indicates an error while writing the client's request to the server.

imap.error 2

This message appear when reading continuation answer from message but Vela cannot found a request that need continuation message. this probable means unknown capabilities or synchronization problem between server and proxy.

imap.error 1

This message indicates an error while writing to the server during continuation response handling.

imap.violation 5

This message indicates that the server returned an untagged line during the authentication exchange, which is unexpected. The line is being dropped as a security measure.

imap.policy 3

This message indicates that the connection is being aborted due to a response received from the server.

imap.policy 3

This message indicates that the response from the server is being dropped.

imap.violation 2

This message indicates that the response received from the server is invalid.

imap.error 1

This message indicates an error while writing the response to the client.

imap.violation 5

This message indicates that a response arrived for an unknown request.

imap.policy 2

This message indicates that the connection is being aborted due to a response received from the server.

imap.policy 5

This message indicates that the response from the server is being dropped as per the policy.

imap.response 6

This log message indicates that a complete response has arrived from the IMAP server.

imap.debug 6

This log message indicates the reconstructed response line.

imap.debug 6

This log message indicates that a literal is being read from the IMAP stream.

imap.policy 3

This is appears when literals count reach it's maximum.

imap.violation 3

This message appears when not allowed character appear in read line.

imap.violation 3

This message means that literal length contains non number characters

imap.violation 3

This message appears literal length attribute is not complete. The close parenthesis is not found

imap.error 2

This message indicates that the stacked proxy rejected the content and Vela rejects the response.

imap.policy 1

This message indicates that the policy type is invalid for the given request and Vela aborts the connection. Check the 'request' attribute.

imap.policy 1

This message indicates that the stack policy for the given response is invalid and Vela stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_MIME or POP3_STK_DATA is invalid.

imap.policy 1

This message indicates that the stack policy for the given response is invalid and Vela stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.

imap.policy 1

This message indicates that the callback for the given request policy is invalid and Vela stacks nothing. Check the 'request' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.

imap.policy 1

This message indicates that the returned value of the callback for the given response policy is invalid and Vela stacks nothing. Check the callback function.

smtp.policy 1

This message indicates that the policy type is invalid for the given request and Vela aborts the connection. Check the 'request' attribute.

smtp.policy 1

This message indicates that the parameter of the request policy of the given request is invalid and Vela aborts the connection. Check the 'request' attribute.

smtp.policy 1

This message indicates that the returned value of the callback for the given request policy is invalid and Vela aborts the connection. Check the callback function.

smtp.policy 1

This message indicates that the policy type is invalid for the given response and Vela aborts the connection. Check the 'response' attribute.

smtp.policy 1

This message indicates that the parameter of the response policy of the given request is invalid and Vela aborts the connection. Check the 'response' attribute.

smtp.policy 1

This message indicates that the returned value of the callback for the given response policy is invalid and Vela aborts the connection. Check the callback function.

smtp.violation 2

This message indicates that the request command verb is invalid and Vela rejects the request.

smtp.request 7

This message reports that the request was parsed successfully.

smtp.debug 6

This message reports that the request is going to be fetched.

smtp.violation 2

This message indicates that the request line is too long and Vela rejects the request. Check the 'max_request_length' attribute.

smtp.debug 6

This message reports that the request is going to be processed.

smtp.violation 4

This message indicates that the given command is not permitted in this state of the communication and Vela rejects the request.

smtp.violation 2

This message indicates that the given request is unknown and Vela rejects it. Check the 'permit_unknown_command' and the 'request' attributes.

smtp.debug 6

This message reports that the request is going to be copied to the server.

smtp.error 3

This message indicates that an error occurred during sending the request to the server.

smtp.debug 6

This message reports that the authentication request is going to be fetched.

smtp.violation 2

This message indicates that the authentication request line is too long and Vela rejects the request. Check the 'max_auth_request_length' attribute.

smtp.debug 6

This message reports that the authentication request is going to be copied to the server.

smtp.error 3

This message indicates that an error occurred during sending the authentication request to the server.

smtp.violation 2

This message indicates that the response contains non-numeric characters and Vela rejects the response.

smtp.violation 2

This message indicates that the continuation character of the response contains an invalid character and Vela rejects the response. The response must contain ' ' or '-' after the response code.

smtp.debug 6

This message reports that the response is going to be fetched.

smtp.violation 2

This message indicates that the response line is too long and Vela rejects the response. Check the 'max_response_length' attribute.

smtp.violation 2

This message indicates that the reply code has changed in the continuation lines and Vela rejects the response.

smtp.response 7

This message reports that the response is parsed successfully.

smtp.debug 6

This message indicates that the response is going to be processed.

smtp.debug 6

This message reports that the response is going to be copied to the client.

smtp.error 3

This message indicates that an error occurred during sending the response to the client.

smtp.policy 3

This message indicates that the response code 250 for the NOOP request is required and Vela ignores the invalid policy while generating NOOPs to the server.

smtp.policy 3

This message indicates that the response code 354 for the DATA request is required and Vela ignores the invalid policy during data transfer to the server.

smtp.policy 3

This message indicates that the content was declared invalid by the stacked proxy and Vela rejects it.

smtp.policy 3

This message indicates that an error occurred during stacked proxy handle the contents and Vela send back a temporary error message.

smtp.error 3

This message indicates that an empty message is received from the stacked proxy and Vela rejects it.

smtp.error 3

This message indicates that Vela was unable to send RSET command to the server.

smtp.debug 6

This message reports that Vela is exiting from the SMTP proxy loop and closing connections on both side.

smtp.violation 2

This message indicates that parsing the local part of the address failed.

smtp.violation 2

This message indicates that the local part of the mail is invalid because it does not end with a '@' sign.

smtp.violation 2

This message indicates that the domain name of the mail is invalid.

smtp.violation 2

This message indicates that the address path is invalid because it does not start with a '<' sign.

smtp.violation 2

This message indicates that the source-root information of the address patch is invalid.

smtp.violation 2

This message indicates that the address information is invalid.

smtp.violation 2

This message indicates that the address path is invalid because it does not start with a '>' sign but ends with it.

smtp.violation 2

This message indicates that the address path is invalid because it does not end with a '>' sign.

smtp.violation 2

This message indicates that the SIZE extension of the MAIL command is invalid because it must contain non-numeric characters. Vela rejects the request.

smtp.violation 2

This message indicates that the BODY extension of the MAIL command is invalid because it must contain either '7BIT' or '8BITMIME'. Vela rejects the request.

smtp.violation 2

This message indicates that the AUTH extension of the MAIL command is invalid because it must be xtext. Vela rejects the request.

smtp.violation 2

This message indicates that the given extension is invalid with the MAIL command and Vela rejects the request.

ftp.session 5

This message reports that the data connection is accepted from the client.

ftp.session 5

This message reports that the data connection is accepted from the server.

ftp.session 5

This message reports that the data connection is established to the client.

ftp.error 4

This message indicates that the data connection is established to the client, but the no connection is expected or the connection is canceled meanwhile.

ftp.session 5

This message reports that the data connection is established to the server.

ftp.error 4

This message indicates that the data connection is established to the server, but the no connection is expected or the connection is canceled meanwhile.

ftp.error 3

This message indicates that the previous data connection was not completely teared down and a new one is about to accept. This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.error 3

This message indicates that the previous data connection was not completely teared down while a new connection is being established. This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.error 3

This message indicates that the previous data connection was not completely teared down and a new one is being established. This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.debug 6

This message indicates that the data connection is going to be destroyed.

ftp.error 3

This message indicates an internal error that a previous data connection was not completed successfully. This condition should not occur, though the event is harmless, an explicit data reset clears this state. Please contact the Balasys QA team (devel@balasys.hu).

ftp.error 2

This message indicates an internal error that the proxy is unable to start a stacked data proxy because either the data connection to the FTP client or the FTP server is not yet established. Please contact the Balasys QA team (devel@balasys.hu).

ftp.error 2

This message indicates an internal error that the current command descriptor changed while the data connection was being set up, thus we are unable to know which direction is permitted during data transfer. Please contact the Balasys QA team (devel@balasys.hu).

ftp.session 4

This message reports that data connection is established between the client and the server, and proxy is being stacked for the data transfer.

ftp.policy 3

This message indicates that the IP address of the data connection to be established differs from the IP of the control connection. This might be caused by a real bounce attack on FTP, or a erroneously configured NAT translation on the client or server side.

ftp.error 1

This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.error 1

This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.policy 2

This message indicates that the configured max_line_length is above upper limit and Vela sets it to the upper limit.

ftp.policy 2

This message indicates that the configured max_username_length is above max_line_length which does not make sense and Vela sets it to the max_line_length.

ftp.policy 2

This message indicates that the configured max_password_length is above max_line_length which does not make sense and Vela sets it to the max_line_length.

ftp.policy 2

This message indicates that the configured max_hostname_length is above max_line_length which does not make sense and Vela sets it to the max_line_length.

ftp.policy 2

This message indicates that the character set specified in the valid_chars_username attribute has a syntax error.

ftp.error 1

This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.error 4

This message reports that Vela was unable to write out a full line and some data remained in the buffer.

ftp.violation 1

This message indicates that the server's answer does not begin with a valid 3 character long number.

ftp.response 6

This message reports that a valid answer is read from the server.

ftp.error 1

This message indicates that Vela was unable to fetch the answer from the server. It is likely caused by some timeout.

ftp.violation 1

This message indicates that too short answer is read from the server. A valid answer must be at least 4 character long.

ftp.violation 1

This message indicates that the server's answer has invalid continuation mark.

ftp.policy 3

This message indicates that the given response is rejected and changed by the policy.

ftp.error 2

This message indicates that Vela was unable to read from the client side.

ftp.request 6

This message reports that a valid request is fetched from the client.

ftp.violation 1

This message indicates that an empty command is received, and policy does not permit it.

ftp.violation 1

This message indicates that an unknown command is received and policy does not permit it.

ftp.error 1

This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.error 3

This message indicates that the given request was not permitted in non-transparent mode before the sever connection was established. It is likely caused by an AUTH command.

ftp.policy 3

This message indicates that the given request was rejected by the policy.

ftp.policy 4

This message reports that the given request is answered by Vela without sending the request to the server.

ftp.policy 2

This message indicates that the given request is rejected and the connection is aborted by Vela.

ftp.policy 1

This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.policy 3

* This message reports that the server send an answer * which have too many lines. Increase the self.max_continuous_line variable * if this is not a security incident.

ftp.debug 8

This message reports that Vela is reading from it's peers on the given side.

ftp.policy 5

This message indicates that the policy does not contain any setting for the given request and Vela rejects the request. Check the 'request' attribute.

ftp.policy 1

This message indicates that the policy type is invalid for the given request and Vela rejects the request. Check the 'request' attribute.

ftp.policy 1

This message indicates that the policy for the given request is invalid and Vela rejects the request. Check the 'request' attribute. It is likely that the parameter for the FTP_REQ_POLICY is invalid.

ftp.policy 1

This message indicates that the callback for the given request policy is invalid and Vela rejects the request. Check the 'request' attribute. It is likely that the parameter for the FTP_REQ_POLICY is invalid.

ftp.policy 1

This message indicates that the returned value of the callback for the given request policy is invalid and Vela rejects the request. Check the callback function.

ftp.policy 5

This message indicates that the policy does not contain any setting for the given response and Vela rejects the response. Check the 'response' attribute.

ftp.policy 1

This message indicates that the policy type is invalid for the given response and Vela rejects the request. Check the 'request' attribute.

ftp.policy 1

This message indicates that the policy for the given response is invalid and Vela rejects the response. Check the 'response' attribute. It is likely that the parameter for the FTP_RSP_POLICY is invalid.

ftp.policy 1

This message indicates that the callback for the given response policy is invalid and Vela rejects the response. Check the 'response' attribute. It is likely that the parameter for the FTP_RSP_POLICY is invalid.

ftp.policy 1

This message indicates that the returned value of the callback for the given response policy is invalid and Vela rejects the response. Check the callback function.

ftp.policy 5

This message indicates that the policy does not contain any setting for the given feature and Vela drops the feature. Check the 'features' attribute.

ftp.policy 1

This message indicates that the policy type is invalid for the given feature and thus Vela drops the feature.

ftp.policy 3

This message indicates that the request_stack or response_stack hash contains an invalid stacking tuple. It should contain a (stack_type, proxy_class) tuple. Check your Vela configuration.

ftp.policy 3

This message indicates that the request_stack or response_stack hash contains an invalid stacking type. Check your Vela configuration.

ftp.error 2

This message indicates that the processed request was invalid, and the data transfer failed.

ftp.error 2

This message reports that the data transfer failed.

ftp.info 2

This message indicates that the stacked proxy returned the specified verdict about the content. Check the stacked proxy log for further information.

ftp.debug 6

This message indicates that the stacked proxy accepted the content.

ftp.policy 3

This message indicates that the port part of the username in non-transparent mode is not permitted by the policy and Vela rejects the request. Check the 'target_port_range' attribute.

ftp.policy 3

This message indicates that the username sent by the client contains invalid characters and Vela rejects the request. Check the 'valid_chars_username' attribute.

ftp.policy 3

This message indicates that the hostname part of the username in non-transparent mode is too long and Vela rejects the request. Check the 'max_hostname_length' attribute.

ftp.policy 3

This message indicates that the username is too long and Vela rejects the request. Check the 'max_username_length' attribute.

ftp.error 1

This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

ftp.policy 3

This message indicates that the password is too long and Vela rejects the request. Check the 'max_password_length' attribute.

ftp.violation 1

This message indicates that the data transfer command's answer sent by the server is invalid and Vela resets the data transfer.

ftp.violation 3

This message indicates that the parameter of the request is invalid and Vela rejects the request. This request must not have any parameter at all.

ftp.violation 2

This message indicates that the required parameter for the TYPE command is missing and Vela rejects the request.

ftp.error 3

This message indicates that the requested transfer type specification is normally valid but currently unsupported by the proxy and Vela rejects the request.

ftp.violation 2

This message indicates that the requested transfer type specification is invalid and Vela rejects the request.

ftp.violation 2

This message indicates that the required parameter for the MODE command is missing and Vela rejects the request.

ftp.violation 2

This message indicates that the MODE command parameter is invalid and Vela rejects the request.

ftp.violation 2

This message indicates that the required parameter for the STRU command is missing and Vela rejects the request.

ftp.violation 2

This message indicates that the STRU command parameter is invalid and Vela rejects the request.

ftp.error 2

This message indicates that Vela was unable to start listening for the data connection on the server side and Vela rejects the request.

ftp.error 2

This message indicates that Vela was unable to start listening for the data connection on the server side and Vela rejects the request.

ftp.violation 2

This message indicates that the response to the PASV command is invalid and Vela rejects the response.

ftp.error 2

This message indicates that the proxy was unable to connect to the server on the port specified in its PASV response and Vela rejects the response.

ftp.error 2

This message indicates that Vela was unable to start listening for the data connection on the server side and Vela rejects the request.

ftp.error 2

This message indicates that Vela was unable to start listening for the data connection on the server side and Vela rejects the request.

ftp.violation 2

This message indicates that the required parameter for the EPSV command is missing and Vela rejects the response.

ftp.violation 2

This message indicates that the parameter of the EPSV response does not begin with a bracket and Vela rejects the response.

ftp.violation 2

This message indicates that the parameter of the EPSV response does not have a closing bracket and Vela rejects the response.

ftp.violation 2

This message indicates that the EPSV command response is invalid and Vela rejects the response.

ftp.violation 2

This message indicates that the port number of the EPSV command response is invalid and Vela rejects the response.

ftp.violation 2

This message indicates that Proxy cannot detect the server address. This an internal error.

ftp.violation 1

This message indicates that the protocol specified by the EPSV command response is not supported by the proxy and Vela rejects the response.

ftp.error 2

This message indicates that the proxy was unable to connect to the server on the port specified in its EPSV response and Vela rejects the response.

ftp.violation 2

This message indicates that the parameter of the PORT command is invalid and Vela rejects the request.

ftp.policy 1

This message indicates that the 'data_mode' attribute of the policy is invalid and Vela rejects the request. Check the 'data_mode' attribute.

ftp.error 2

This message indicates that the proxy was unable to connect to the client on the port specified in its PORT response and Vela rejects the response.

ftp.violation 2

This message indicates that the response of the PASV command is invalid and Vela rejects the response.

ftp.error 2

This message indicates that the proxy was unable to connect to the client on the port specified in its PORT response and Vela rejects the response.

ftp.violation 2

This message indicates that the response of the PORT command is invalid and Vela rejects the response.

ftp.error 2

This message indicates that Vela was unable to start listening for the data connection on the client side and Vela rejects the request.

ftp.error 2

This message indicates that Vela was unable to start listening for the data connection on the client side and Vela rejects the request.

ftp.violation 2

This message indicates that the response of the PORT command is invalid and Vela rejects the response.

ftp.violation 2

This message indicates that the required parameter for the EPRT command is missing and Vela rejects the request.

ftp.violation 2

This message indicates that the parameter of the EPRT command is invalid and Vela rejects the request.

ftp.violation 2

This message indicates that the port number of the EPRT command is invalid and Vela rejects the request.

ftp.violation 2

This message indicates that the protocol specified by the EPRT command is not supported by the proxy and Vela rejects the response.

ftp.violation 2

This message indicates that the host address of the EPRT command is invalid and Vela rejects the request.

ftp.error 2

This message indicates that the proxy was unable to connect to the client specified in the EPRT response and Vela rejects the response.

ftp.violation 2

This message indicates that the response of the EPRT is invalid and Vela rejects the response.

ftp.error 2

This message indicates that Vela was unable to start listening for the data connection on the client side and Vela rejects the response.

ftp.violation 2

This message indicates that the response of the EPSV command is invalid and Vela rejects the response.

ftp.violation 2

This message indicates that the parameter of the ALLO command is invalid and Vela rejects the request.

pop3.request 4

This message indicates that the request must not have any parameter and Vela is going to drop the parameter.

pop3.request 3

This message indicates that the numerical parameter of the request is missing and Vela aborts the connection.

pop3.request 3

This message indicates that the numerical parameter of the request is not in the given range and Vela aborts the connection.

pop3.request 3

This message indicates that the numerical parameter of the request is a negative number which is invalid and Vela aborts the connection.

pop3.request 3

This message indicates that the numerical parameter of the request is zero which is invalid and Vela aborts the connection.

pop3.request 4

This message indicates that the numerical parameter of the request contains junk characters after the number but Vela ignores and truncates the junk.

pop3.request 3

This message indicates that the first numerical parameter is not in the given range and Vela aborts the connection.

pop3.request 3

This message indicates that the first numerical parameter of the request is a negative number which is invalid and Vela aborts the connection.

pop3.request 3

This message indicates that only one numerical parameter is present but two is required and Vela rejects the request.

pop3.request 3

This message indicates that the second numerical parameter is not in the given range and Vela aborts the connection.

pop3.request 3

This message indicates that the second numerical parameter of the request is a negative number which is invalid and Vela aborts the connection.

pop3.request 4

This message indicates that the numerical parameters of the request contain junk characters after the numbers but Vela ignores and truncates the junk.

pop3.policy 2

This message indicates that the username parameter of the request is too long and Vela rejects the request. Check the 'max_username_length' attribute.

pop3.policy 2

This message indicates that the password parameter of the request is too long and Vela rejects the request. Check the 'max_password_length' attribute.

pop3.request 3

This message indicates that the username parameter is too long or the digest missing after the username and Vela rejects the request.

pop3.request 3

This message indicates that the MD5 digest parameter of the request is invalid and Vela rejects the request.

pop3.response 3

This message indicates that the numerical parameter of the response is missing and Vela aborts the connection.

pop3.response 3

This message indicates that the numerical parameter of the response is not in the given range and Vela aborts the connection.

pop3.response 3

This message indicates that the numerical parameter of the response is a negative number which is invalid and Vela aborts the connection.

pop3.response 4

This message indicates that the numerical parameter of the response contains junk characters after the number but Vela ignores and truncates the junk.

pop3.response 3

This message indicates that the second numerical parameter of the response is not in the given range and Vela aborts the connection.

pop3.response 3

This message indicates that the second numerical parameter of the response is missing and Vela aborts the connection.

pop3.response 3

This message indicates that the second numerical parameter of the response is a negative number which is invalid and Vela aborts the connection.

pop3.request 4

This message indicates that the second numerical parameter of the response contains junk characters after the number but Vela ignores and truncates the junk.

pop3.debug 5

This message indicates that the policy does not contain any setting for the given request and Vela rejects the request. Check the 'request' attribute.

pop3.policy 1

This message indicates that the policy type is invalid for the given request and Vela aborts the connection. Check the 'request' attribute.

pop3.policy 1

This message indicates that the policy for the given request is invalid and Vela aborts the connection. Check the 'request' attribute. It is likely that the parameter for the POP3_REQ_POLICY is invalid.

pop3.policy 1

This message indicates that the callback for the given request policy is invalid and Vela aborts the connection. Check the 'request' attribute. It is likely that the parameter for the POP3_REQ_POLICY is invalid.

pop3.policy 1

This message indicates that the returned value of the callback for the given request policy is invalid and Vela aborts the connection. Check the callback function.

pop3.debug 5

This message indicates that the policy does not contain any setting for the given response and Vela rejects the response. Check the 'request' attribute.

pop3.policy 1

This message indicates that the policy type is invalid for the given response and Vela aborts the connection. Check the 'request' attribute.

pop3.policy 1

This message indicates that the policy for the given request/response is invalid and Vela aborts the connection. Check the 'request' attribute. It is likely that the parameter for the POP3_REQ_POLICY is invalid.

pop3.policy 1

This message indicates that the returned value of the callback for the given response policy is invalid and Vela aborts the connection. Check the callback function.

pop3.policy 1

This message indicates that the stack policy type is invalid for the given response, so nothing will be stacked. Check the 'response_stack' attribute.

pop3.policy 1

This message indicates that the stack policy for the given response is invalid and Vela stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_MIME or POP3_STK_DATA is invalid.

pop3.policy 1

This message indicates that the stack policy for the given response is invalid and Vela stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.

pop3.policy 1

This message indicates that the callback for the given request policy is invalid and Vela stacks nothing. Check the 'request' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.

pop3.policy 1

This message indicates that the returned value of the callback for the given response policy is invalid and Vela stacks nothing. Check the callback function.

pop3.violation 3

This message indicates that the response line is too long and Vela aborts the connection. Check the 'max_reply_length' attribute.

pop3.violation 3

This message indicates that the status of the response is invalid and Vela rejects the response. The response should begin with '+OK' or with '-ERR'.

pop3.response 7

This message reports that the fetched response contains a parameter.

pop3.response 7

This message reports the fetched response.

pop3.error 2

This message indicates that the multi-line data transfer failed and Vela rejects the response.

pop3.violation 3

This message indicates that the request line is too long and Vela rejects the request. Check the 'max_request_length' attribute.

pop3.request 7

This message reports that the fetched request contains a parameter.

pop3.request 7

This message reports the fetched request.

pop3.request 3

This message indicates that the request was unknown and Vela aborts the connection. Check the 'permit_unknown_command' and the 'request' attributes.

pop3.request 3

This message indicates that the request command is not allowed in this state of the protocol and Vela rejects the request.

pop3.error 2

This message indicates that the stacked proxy rejected the content and Vela rejects the response.

mb.log.policy 1

This message indicates that the policy type is invalid for the given request and Vela aborts the connection. Check the 'request' attribute.

mb.log.policy 1

This message indicates that the policy for the given request is invalid and Vela aborts the connection. Check the 'request' attribute. It is likely that the parameter for the MB_REQ_POLICY is invalid.

mb.log.policy 1

This message indicates that the callback for the given request policy is invalid and Vela aborts the connection. Check the 'request' attribute. It is likely that the parameter for the MB_REQ_POLICY is invalid.

mb.log.policy 1

This message indicates that the returned value of the callback for the given request policy is invalid and Vela aborts the connection. Check the callback function.

ssh.policy 3

This message indicates that the client_channel_stack or the server_channel_stack hash contains an invalid stacking type. Check your Vela configuration.

ssh.policy 3

This message indicates that the client_channel_stack or the server_channel_stack hash contains an invalid stacking tuple. It should contain a (stack_type, proxy_class) tuple. Check your Vela configuration.

core.debug 7

This message reports that the data-transfer to or from some endpoint is closed.

core.error 3

This message indicates the data transfer timed out.

core.error 3

This message indicates that the data-transfer is interrupted by a timed progress callback and Vela is closing the date-transfer channels.

core.error 4

This message indicates that server unexpectedly closed its connection.

core.error 0

This message is logged when Vela caught a fatal signal. Possible reason is bad RAM or other hardware.

core.error 0

This message indicates that Vela was unable to initialize the Python engine. It is likely that your installation is broken. Check your packages and there version number.

core.session 3

This message reports that a new proxy instance is started.

core.session 4

This message reports that a new proxy instance is stopped.

smtp.policy 3

This message indicates that the sender address was administratively prohibited and the request is rejected. Check the 'sender_matcher' attribute.

smtp.debug 6

This message reports that the sender address check was successful and the request is accepted.

smtp.policy 3

This message indicates that the email address local-part contains a percent sign and it is not permitted by the policy and the request is rejected. Check the 'permit_percent_hack' attribute.

smtp.policy 3

This message indicates that the email address local-part contains a exclamation mark and it is not permitted by the policy and the request is rejected. Check the 'permit_exclamation_mark' attribute.

smtp.policy 3

This message indicates that relaying the given address is not permitted by the policy and the request is rejected. Check the 'relay_check' attribute.

smtp.debug 6

This message reports that the relay check was successful and the request is accepted.

smtp.policy 3

This message indicates that the given recipient address is administratively prohibited and request is rejected. Check the 'recipient_matcher' attribute.

smtp.debug 6

This message reports that the recipient check was successful and the request is accepted.

smtp.debug 7

This message reports that the zone of the client is being checked.

smtp.debug 7

This message reports that the domain name of the email is being checked.

core.error 0

This message indicates that the initialization function of the given instance was not found in the policy file.

core.debug 6

This message reports that the given instance is stopping.

core.debug 6

This message reports that the given instance is freeing its external resources (for example its kernel-level policy objects).

ftp.policy 3

This message indicates that the remote port is bellow 1024 and due to the violation the connection is closed.

ftp.policy 3

This message indicates that the remote port is bellow 1024 and due to the violation the connection is closed.

ftp.policy 3

This message indicates that the server's remote port is not control_port-1 or 20 and due to the violation the connection is closed.

ftp.policy 3

This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).

core.debug 4

This message reports that the NAT type and the old address before the NAT mapping occurs.

core.debug 4

This message reports that the NAT type and the new address after the NAT mapping occurred.

core.policy 0

This message indicates that the service lookup has failed for this session.

core.policy 2

This message indicates that no applicable service was found for this client zone in the services cache. It is likely that there is no applicable service configured in this ZoneDispatcher at all. Check your ZoneDispatcher service configuration. @see: Dispatcher.ZoneDispatcher

core.policy 2

This message indicates that no applicable service was found for this client zone. Check your ZoneDispatcher service configuration. @see: Dispatcher.ZoneDispatcher

core.policy 2

This message indicates that no applicable service was found for this client zone in the services cache. It is likely that there is no applicable service configured in this CSZoneDispatcher at all. Check your CSZoneDispatcher service configuration. @see: Dispatcher.CSZoneDispatcher

core.policy 2

This message indicates that no applicable service was found for this client zone. Check your CSZoneDispatcher service configuration. @see: Dispatcher.CSZoneDispatcher

core.policy 1

This message indicates that a service trying to enter to the given zone was denied by the policy. Check that the destination zone is included in the target zone list of the service.

core.error 3

This message indicates that the given hostname could not be resolved. It could happen if the hostname is invalid or nonexistent, or it if your resolve setting are not well configured. Check your "/etc/resolv.conf"

core.message 3

This message indicates that the cache size(threshold) is reached, and cache is shifted. @see: Cache.ShiftCache

core.policy 4

This message reports that a matching regexp pattern was found for the given string.

core.policy 3

This message indicates that the file containing the match regexps cannot be opened. It is likely that the file does not exists or it is not permitted to read. @see: Matcher.RegexpFileMatcher

core.policy 3

This message indicates that the file containing the ignore regexps cannot be opened. It is likely that the file does not exists or it is not permitted to read. @see: Matcher.RegexpFileMatcher

core.debug 6

This message reports that the recipient address has been already checked and the cached information is used.

core.debug 6

This message reports that the recipient address has not been already checked and it is going to be checked now directly.

core.error 3

This message indicates that the sender address was rejected during the recipient address verify check and the recipient address is rejected.

core.info 5

This message reports that the recipient address verify was successful and it is accepted.

core.info 4

This message reports that the recipient address verify was unsuccessful and it is rejected.

core.error 3

This message indicates that an SMTP error occurred during the recipient address verify and it is rejected.

http.accounting 4

This is an accounting message that reports request details.

http.request 6

This message indicates that the request was blocked by the URIFilter.

core.auth 5

This message reports that a REQUIRED type Basic ACL rule is evaluated with the given result.

core.auth 4

This message reports that every Basic ACL rule were evaluated with the given final result.

core.session 5

This message reports that this proxy instance was ended.

core.debug 6

This message reports that this proxy instance was destroyed and freed.

core.error 2

This message indicates that an error occurred during child proxy stacking. The stacking failed and the subsession is destroyed.

core.debug 7

This message reports that a new proxy is about to be stacked under the current proxy, as a child proxy.

core.auth 3

This message reports that the user authentication was successful.

core.session 3

This message indicates that the connection to the server failed.

core.session 3

This message indicates that the connection to the server succeeded.

core.session 3

This message indicates that the connection to the server can not be established, because no server address is set.

core.message 4

This message reports that the remote end is down and the down state of the remote end is stored, so connection is wont be tried to it within the timeout latter.

core.message 4

This message reports that the remote end is down, but the down state is not stored of the remote end, so connection will be tried to it next time.

core.message 4

This message reports that the remote end is down and the down state is stored of the remote end, so connection wont be tried within the timeout latter.

core.session 3

This message indicates that side stacking failed, because a socketPair creation is failed. It is likely that there is now resource available. Try increase fd limits.

core.session 4

This message indicates that side stacking was successful.

core.error 3

This message indicates that side stacking failed.

core.error 3

This message indicates an internal error, please contact your Vela support for assistance.

core.error 3

This message indicates an internal error, please contact your Vela support for assistance.

core.error 3

This message indicates an internal error, please contact your Vela support for assistance.

core.info 4

This message reports that the SZIG framework was unable to create its socket and thus velactl won't be able to access and display internal Vela information.

core.error 1

This message indicates that the given python function is not callable. Check your AuthenticationProvider methods. @see: Auth.AuthenticationProvider

core.error 1

This message indicates that Vela was unable to find the required proxy module. Check your installation, or contact your Vela support for assistance.

core.debug 6

This message reports that the given proxy-exported attribute was fetched, and it contained the also given value.

core.debug 6

This message reports that the given proxy-exported attribute was changed to the given value.

core.info 3

Indicates that an invalid session ID is specified by the authorize command

core.debug 7

This message reports that Vela is about to call the proxy's %event() event.

core.debug 7

This message reports that Vela is about to call the proxy's __destroy__() event. This method handles the pre destroy tasks, like the shutdown of the server side connection.

core.error 3

This message indicates an internal error, please contact your Vela support for assistance.

core.error 2

This message indicates that Vela was unable to create a new thread for the new proxy instance. It is likely that Vela reached a thread limit, or not enough resource is available.

core.info 2

A stop request arrived to the proxy. It has to be stopped.

core.debug 7

This message indicates that Vela began establishing connection with the indicated remote host.

core.error 2

This message indicates that the AuthAgent authentication client sent an invalid command. Check your AuthAgent package version, or contact your Vela support for assistance.

core.error 3

This message indicates that communication was interrupted to VAS.

core.debug 8

This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.

core.error 1

This message indicates that loading a proxy module failed.

core.error 0

This message indicates that Vela was unable to open the policy file. Check the permissions of your policy file.

core.error 0

This message indicates that Vela was unable to parse the policy file. Check the logs for further information on where the error occurred in the policy.

core.error 1

This message indicates that stacking a child proxy failed, because creating an AF_UNIX domain socketpair failed on the client side.

core.error 1

This message indicates that stacking a child proxy failed, because creating an AF_UNIX domain socketpair failed on the server side.

core.debug 6

This message reports that Vela is about to stack a proxy class with the given fds as communication channels.

core.error 1

This message indicates that stacking a child proxy failed, because creating an AF_UNIX domain socketpair failed for the control channel.

core.debug 6

This message reports that Vela is about to stack a program with the given fds as communication channels.

core.debug 7

This message reports that the end-of-file status has been updated.

core.error 3

This message indicates that packet stats interval was specified, but no action was configured to handle the event. Check your policy for packetStats event.

core.debug 6

This message reports that the connection was successfully established.

auth.agent.error 3

This message indicates that establishing a connection to the authentication agent failed for the given reason.

core.error 3

This message indicates that the AUTH_AGENT authentication subsystem does not support the address family the client used to access the service to be authenticated. Please contact your Vela support for assistance.

core.error 3

This message indicates that Vela was unable to connect to the client AuthAgent authentication client. It is likely that the client does not run AuthAgent on the default port or something blocks the connection. Check your client configuration.

core.error 3

This message indicates that the SSL handshake with the authentication agent failed because of the given SSL error condition.

core.error 3

This message indicates that AuthAgent authentication failed, because non-IPv4 address was used. Please contact your Vela support for assistance.

core.error 3

This message indicates that AuthAgent authentication failed, because Vela was unable to send data to AuthAgent.

core.error 3

This message indicates that AuthAgent authentication failed, because Vela was unable to read the client authentication answer.

core.error 3

This message indicates an internal error, please contact your Vela support for assistance.

core.error 0

This message indicates that Vela was unable to load the policy. It is likely that the policy has any kind of syntactical problem. Check the traceback in the log to find out where the problem occurs.

core.error 0

This message indicates that Vela was unable to initialize the policy.

core.error 0

This message indicates that the loading of the initial policy failed, because of some policy problem. Check the log to find out where the problem occurs.

core.info 0

This message reports that Vela caught a HUP signal and tries to reload its policy.

core.error 0

This message indicates that Vela was unable to load the new policy, and reverts to the old one. Check the logs to find out where the error occurs in the new policy.

core.error 3

This message indicate that Vela failed opening a new socket. It is likely that Vela reached some resource limit.

core.error 3

This message indicates that UDP connection failed.

core.error 3

This message indicates that Vela was unable to query the local address.

core.error 3

This message indicates that the setsockopt requesting reception of original destination addresses of UDP frames failed.

core.error 3

This message indicates that the setsockopt requesting reception of original destination addresses of UDP frames failed.

core.error 2

This message indicate that the creation of a new socket failed for the given reason. It is likely that the system is running low on memory, or the system is running out of the available fds.

core.policy 1

This message indicates that the decision layer denied the given connection.

core.debug 7

This message indicates that a Dispatcher on the given local address is started.

core.debug 4

This message reports that a new dispatcher thread is starting. This is used if threaded dispatching is enabled. @see: Dispatcher

core.debug 4

This message reports the dispatcher average accept queue length status.

core.debug 4

This message reports that the dispatcher thread is exiting. It it likely that Vela unbinds from that address.

core.error 2

This message indicates that Vela was unable to create a dispatcher thread for accepting new connection, and it is reverting back to the original non-threaded mode. It is likely that Vela reached its thread or resource limit. Check your logs for further information.

core.debug 6

This message reports that a new connections is coming.

core.error 3

This message indicates that a new connection was accepted, but no Dispatcher/Proxy was interested in it.

core.error 1

This message indicates that Dispatcher was configured to be accept transparent connections, but it was connected directly. Configure it either non-transparent or deny direct access to it and set up the appropriate TPROXY rule. @see: Dispatcher

core.error 1

This message indicates that a Dispatcher/Proxy was unable bind to a specified address, because another instance is already listening there and specified that only one connection could be accepted.

core.error 1

This message indicates that a Dispatcher/Proxy tries to unbind from the specified address, but have not registered itself to that address.

core.error 1

This message indicates that a Dispatcher/Proxy tries to unbind from the specified address, but Vela does not bind to that address.

configdb.error 1

This message indicates that loading a module failed.

configdb.error 2

This message indicates that parsing plugin directory failed.

core.error 0

This message is logged when VMS caught a fatal signal. Possible reason is bad RAM or other hardware.

core.debug 4

This message is logged when VMS caught a fatal signal. Possible reason is bad RAM or other hardware.

core.debug 7

This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.

core.error 1

This message indicates that loading a module failed.

core.error 1

This message indicates that configdb module not loaded.

core.error 1

This message indicates that keymanagement module not loaded.

core.error 1

This message indicates that transfer module not loaded.

core.error 1

This message indicates that backup module not loaded.

core.error 1

This message indicates that loading a proxy module failed.

core.error 0

This message is logged when agent caught a fatal signal. Possible reason is bad RAM or other hardware.

core.error 0

This message is logged when VAS caught a fatal signal. Possible reason is bad RAM or other hardware.

core.debug 6

This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.

core.error 3

This message indicates that loading a module failed.

core.info 3

This message indicates that loading a module failed.

core.error 1

This message indicates that the module directory does not exist.

core.error 0

This message is logged when agent caught a fatal signal. Possible reason is bad RAM or other hardware.

core.error 0

This message is logged when Vela caught a fatal signal. Possible reason is bad RAM or other hardware.

core.debug 6

This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.

core.error 3

This message indicates that loading a module failed.

core.info 3

This message indicates that loading a module failed.

core.error 1

This message indicates that the module directory does not exist.