Table of Contents
- ADFI-120 — Application of honeypot blacklist failed
- ADFI-121 — Failure of pfctl operation report
- ADFI-131 — Reading packet filter ips-blacklist table failed
- ADFI-710 — Adaptive Kernun IPS module database refresh report
- ADFI-720 — Adaptive Firewall IPS database refresh report
- ADFI-724 — Client was excluded from the IPS database due to whitelist
- ADFI-729 — Adaptive Firewall IDS database refresh report
- ADFI-730 — Planned refresh of packet filter ips-blacklist table
- ADFI-731 — Current packet filter ips-blacklist table size report
- AFHP-250 — Honeypot module cannost accept new connection
- AFHP-251 — Honeypot module accepted unsupported client
- AFHP-750 — New client was trapped to honeypot
- AFHP-888 — Honeypot module statistics message
- AFLD-709 — Final application termination message
- AFWD-120 — Unrecognized event on watched file
- AFWD-150 — Watched file is not regularly accessible
- AFWD-160 — Watched file is not regularly accessible
- AFWD-670 — Client occurence in watchdog file checked against thresholds
- ALRT-109 — General select() error
- ALRT-159 — Call of snmptrap program has failed
- ALRT-259 — SNMP trap could not be sent
- ALRT-290 — Alert daemon socket not accessible
- ALRT-501 — Alert daemon communication channels cannot be opened
- ALRT-700 — Notification about the mode of operation of the alert daemon
- ALRT-701 — An alert daemon has been initialized and is ready to work
- ALRT-707 — Alert daemon has finished
- ALRT-708 — Alert daemon has unbound the sockets used for listening for clients
- ALRT-709 — Final daemon termination message
- ALRT-710 — SNMP alert receipt report
- ALRT-750 — SNMP trap has been sent
- ALRT-759 — SNMP trap could not be sent
- ARGS-000 — Application initialisation failed when preparing getopt() system call
- ARGS-001 — Application has improperly started
- ARGS-002 — Application command line arguments array is NULL
- ARGS-010 — Application requested to register an illegal option char
- ARGS-011 — Function initgetopt() failed due to duplicate command-line option
- ARGS-012 — Function initgetopt() failed due to a large option set
- ARGS-013 — Function initgetopt() failed due to a large option set
- ARGS-500 — Command line argument array starts by a NULL pointer (bad program name)
- ARGS-520 — Command-line option used more than once
- ARGS-521 — Application called with an unknown command-line option
- ARGS-522 — Application called with option without proper argument
- ARGS-523 — Option -f specifies too long filename
- ARGS-524 — Options on command line are followed by an extra argument
- ARGS-529 — Terminal message in case of wrong command line parameters
- ARGS-710 — KERNUN_ROOT environment variable has incorrect content
- ASN1-300 — Parser ran out of read buffer
- ASN1-700 — Parser read integer out of allowed range
- ASN1-701 — Parser read integer coding length greater than 4 bytes
- ASN1-702 — Parser read length encoding starting with two ones
- ASN1-720 — Parser read IA5 string character with unknown code
- ATRM-010 — Searching of ACL failed
- ATRM-109 — General select() error
- ATRM-610 — Request is not covered by configuration
- ATRM-700 — Notification about the mode of operation of ATR monitor
- ATRM-701 — ATR monitor has been initialized and is ready to accept packets
- ATRM-707 — ATR monitor has finished
- ATRM-708 — ATR monitor has unbound the sockets used for listening for clients
- ATRM-709 — Final daemon termination message
- ATRM-710 — Daemon runtime monitoring support cannot be initialized
- ATRM-740 — Address state change report
- ATRM-808 — Session has started, client connection has arrived
- ATRM-809 — DNS session finished
- ATRM-810 — ACL decision has been made, operation either accepted or rejected
- ATRM-820 — ACL decision has been made, operation either accepted or rejected
- ATRM-860 — Request processing finished
- AUTH-110 — Authentication handle cannot be allocated
- AUTH-111 — Authentication password file cannot be opened
- AUTH-112 — Authentication tool cannot be opened
- AUTH-131 — Authentication password file read failed
- AUTH-135 — Call to authentication library failed
- AUTH-631 — User not found in authentication password file
- AUTH-632 — User password does not match to the one in password file
- AUTH-635 — User password/response rejected by authetication tool
- AUTH-731 — Proxy-user name too long
- AUTH-740 — I/O error in communication with external authentication tool
- AUTH-741 — Protocol error in communication with external authentication tool
- AUTH-742 — Protocol error in communication with external authentication tool
- AUTH-743 — Protocol error in communication with external authentication tool
- AUTR-500 — Configuration does not contain RADIUS library settings
- AUTR-501 — RADIUS server host is not correctly specified in configuration file
- AUTR-600 — A call to RADIUS client library returned an error
- AUTR-601 — RADIUS client library initialization failed
- AUTR-602 — A response of unknown type was received from a RADIUS server
- AUTR-603 — A user was rejected by a RADIUS server
- AUTR-604 — A user was accepted by a RADIUS server
- AUTR-605 — A RADIUS server has sent a challenge to a user
- AUTR-606 — A user has respoded to an authentication challenge
- CASE-500 — Obsolete feature used in configuration
- CASE-510 — Interface definition does not contain IP address specification
- CASE-511 — Interface definition does not contain IP address specification
- CASE-513 — Only Ethernet interfaces can be aggregated
- CASE-514 — Duplicite aggregation of one interface
- CASE-515 — VLAN ID definition invalid
- CASE-516 — Parent interface of VLAN interface is of inappropriate type
- CASE-517 — Duplicate VLAN ID definition
- CASE-518 — Cannot make alias without base address
- CASE-804 — The kernel may be blocked by a packet cyclically fastrouted on lo0
- CFGL-010 — Incorrect call of regexpizelist()
- CFGL-031 — Incorrect key is to be searched in list
- CFGL-340 — List extraction function called with insufficient array
- CFGL-500 — Attempt to add item '*' into non-extended list
- CFGL-501 — Too deep sublist nesting
- CFGL-520 — Adding to '*'-list requested
- CFGL-521 — Adding of exclude-member to simple list requested
- CFGL-522 — Overlapping range is to be added to list
- CFGL-523 — Lower and upper bounds are not compatible
- CFGL-524 — Adding of string, regexp or sock range requested
- CFGL-549 — Name-set represents no section
- CFGP-100 — Revoking configuration file from RCS failed
- CFGP-500 — Configuration file is empty
- CFGP-501 — First character of configuration is illegal
- CFGP-531 — Illegal character found
- CFGP-532 — Configuration contains character string
- CFGP-533 — Integer found in configuration is too large
- CFGP-534 — Illegal character found in IP address
- CFGP-535 — Illegal syntax of IP address
- CFGP-544 — Alphanumeric character expected in configuration
- CFGP-545 — Incorrect character escape sequence used in string
- CFGP-546 — String expression not closed
- CFGP-547 — String or regexp exceeded the maximum length
- CFGP-548 — String or regexp not closed
- CFGP-549 — IP address probably not closed
- CFGP-591 — IPv4 address byte value too big
- CFGP-592 — IPv4 address byte empty
- CFGP-593 — Incorrect number of IPv4 address bytes
- CFGP-594 — IPv4 address syntax error
- CFGP-595 — IPv4 mask or IPv6 prefix specification invalid
- CFGP-596 — IPv4 mask or IPv6 prefix specification invalid
- CFGP-599 — IPv6 address cannot be parsed
- CFGR-000 — Section/item parser routine failed
- CFGR-003 — Application version tag misformed
- CFGR-109 — Parser initialisation failed
- CFGR-110 — System error during configuration reading
- CFGR-160 — Item addition to list failed
- CFGR-161 — Value to list conversion failed
- CFGR-162 — Sublist creation failed
- CFGR-500 — Configuration integrity constraints error
- CFGR-501 — Parser started without configuration file
- CFGR-502 — No VERSION statement in configuration
- CFGR-503 — VERSION statement has incorrect argument
- CFGR-504 — VERSION statement has incorrect argument
- CFGR-505 — VERSION statement repeated
- CFGR-511 — Configuration item must be closed by semicolon
- CFGR-512 — Section must begin with left brace
- CFGR-513 — List member must be followed by comma or right brace
- CFGR-514 — Configuration ended incorrectly
- CFGR-515 — Closing brace not found
- CFGR-517 — Item/subsection name expected in configuration
- CFGR-518 — Item/subsection name expected in configuration
- CFGR-519 — Incorrect configuration directive found
- CFGR-520 — Obligatory keyword not found
- CFGR-521 — Integer value expected in configuration
- CFGR-523 — String value expected in configuration
- CFGR-524 — Enumeration value expected in configuration
- CFGR-525 — Hostname/IP address expected in configuration
- CFGR-526 — Hostname/regexp/IP network expected in configuration
- CFGR-527 — Regular expression expected in configuration
- CFGR-528 — Hostname/IP address not followed by a colon
- CFGR-529 — IP address value and type incompatibility
- CFGR-530 — Section reference invalid
- CFGR-531 — Section reference invalid
- CFGR-540 — Element is not optional
- CFGR-541 — Element value type is not fractional
- CFGR-542 — Integer value too large
- CFGR-543 — Port/service name invalid
- CFGR-544 — Empty hostname is not allowed
- CFGR-545 — Direct integer value not allowed
- CFGR-546 — Some forms of addresses are not allowed in this place
- CFGR-547 — Enumeration keyword invalid
- CFGR-548 — Time value is not in hhmm format
- CFGR-550 — Section defined more than once
- CFGR-551 — Name of repeatable section missing
- CFGR-552 — Name of repeatable section too long
- CFGR-559 — Nonrepeatable item defined more than once
- CFGR-560 — List not closed by regular member
- CFGR-561 — Excluding members not allowed in simple lists
- CFGR-562 — Member ranges not allowed in simple lists
- CFGR-563 — Operator '*' not allowed in simple lists
- CFGR-564 — List member reading failed
- CFGR-566 — Member ranges not allowed
- CFGR-569 — List of values is not allowed
- CFGR-590 — Negative final configuration message
- CFGR-700 — Configuration file has been opened
- CFGR-710 — Configuration hash reader report
- CFGR-790 — Configuration successfully completed
- CHSC-710 — Character set converter initialisation message
- CHSC-719 — Character set converter initialisation failure
- CHSC-720 — Incomplete or invalid multibyte character sequence
- CKGB-100 — Cannot copy system configuration file prototype to system image
- CKGB-121 — Kernun component configuration generation failed
- CKGB-122 — Nameserver structure creation failed
- CKGB-191 — Cannot create directory
- CKGB-193 — Directory creation failed
- CKGB-321 — Postfix MASTER.CF template line too long
- CKGB-390 — Filename too long
- CKGB-500 — Kernun configuration file contains no SYSTEM
- CKGB-541 — Only one backbone area must be defined in OSPF configuration
- CKGB-550 — More than one IFACE item found when IFACE ANY used
- CKGB-551 — More than one INTERFACE section found when IFACE ANY used
- CKGB-553 — Only FAILOVER protocol is possible for LAGG with ALTQ
- CKGB-554 — Each interface can be used in just one INTERFACE section
- CKGB-560 — ALTQ queue set definition incorrect
- CKGB-561 — ALTQ queue set definition incorrect
- CKGB-562 — ALTQ queue set definition incorrect
- CKGB-563 — ALTQ queue set definition incorrect
- CKGB-564 — ALTQ queue set definition incorrect
- CKGB-565 — ALTQ queue set definition incorrect
- CKGB-566 — ALTQ queue set definition incorrect
- CKGB-567 — ALTQ queue set definition incorrect
- CKGB-568 — ALTQ queue parent definition incorrect
- CKGB-569 — ALTQ queues with equal priority found
- CKGB-570 — DHCP client interface definition collision
- CKGB-571 — Non-transparent proxy cannot listen on DHCP interface
- CKGB-572 — Dynamic DNS forwarder cannot be used without DHCP interface
- CKGB-573 — Proxy probably uses reserved port and will not operate
- CKGB-574 — More Kaspersky antivirus HTTP daemon configured
- CKGB-578 — Primary nameserver must be in zone table
- CKGB-580 — System resolver nameserver specification invalid
- CKGB-584 — Nameserver zone defined by incorrect address
- CKGB-586 — Two interfaces with equal device names found
- CKGB-587 — Socket collision report message
- CKGB-588 — Exactly two systems must be present in the configuration
- CKGB-589 — Cannot resolve listen-on address of pikemon
- CKGB-590 — Exactly two systems must be present in the configuration
- CKGB-710 — Kernun generation started
- CKGB-711 — Kernun verification started
- CKGB-718 — Kernun verification/generation has failed
- CKGB-719 — Kernun verification/generation has succeeded
- CKGB-790 — Particular system configuration file saved
- CKGB-799 — Particular system configuration file failure
- CMLI-100 — EditLine library initialisaton failed
- CMLI-101 — EditLine library initialisaton failed
- CMLI-102 — EditLine library initialisaton failed
- CMLI-103 — EditLine library initialisaton failed
- CMLI-120 — File completion failed
- CMLI-125 — Path to Kernun manual pages invalid
- CMLI-190 — KAT cannot display output to terminal
- CMLI-700 — User interface startup message
- CMLI-709 — User interface closeup message
- CMLI-710 — CML C3H failed
- CMLI-711 — CML C3H failed
- CMLI-712 — CML C3H failed
- CMLI-713 — CML C3H failed
- CMLI-714 — Cannot use C3H for long lines
- CMLI-720 — C3H cannot find filename continuation
- CMLI-725 — Manual page section invalid
- CMLI-775 — Automatic reply in batch mode
- CMLI-780 — Invalid parameters of DBG command
- CMLK-101 — Unaccessible diretory
- CMLK-130 — KAT sends signal to proxy/ssh server
- CMLK-140 — KAT cannot determine running processes
- CMLK-149 — KAT component control command failed for some component
- CMLK-155 — General I/O error message
- CMLK-156 — Log file line misformed
- CMLK-342 — Component misconfigured
- CMLK-500 — Current directory information
- CMLK-509 — Current directory change error report
- CMLK-540 — Misformed line found in 'component.lst' file
- CMLK-541 — Unknown component type found in 'component.lst' file
- CMLK-542 — KAT cannot read proxy configuration
- CMLK-543 — Compoenent monitoring is not available
- CMLK-609 — Issued command denied in read-only mode
- CMLK-700 — KAT exiting
- CMLK-702 — KAT/CML file name invalid
- CMLK-705 — Incorrect call of KAT command
- CMLK-706 — Incorrect call of KAT command
- CMLK-707 — Incorrect call of KAT command
- CMLK-708 — KAT command option not known
- CMLK-709 — KAT command name not known
- CMLK-710 — Configuration hash report
- CMLK-712 — KAT cannot find continuation
- CMLK-713 — Too many arguments to KAT command
- CMLK-714 — Incorrect selection for KAT operation
- CMLK-715 — KAT command parameter invalid
- CMLK-716 — KAT command parameters invalid
- CMLK-720 — KAT cannot find CML SYSTEM file tree
- CMLK-721 — KAT APPLY command requires system name
- CMLK-725 — Configuration RCS version shortcut invalid
- CMLK-731 — KAT KILL command invoked with incorrect signal name/number
- CMLK-732 — KAT KILL command invoked without application name
- CMLK-733 — KAT KILL command invoked with incorrect child specification
- CMLK-739 — KAT command was interrupted
- CMLK-740 — KAT detected running application, cannot start new one
- CMLK-741 — KAT command parameter error
- CMLK-742 — Not daemonized proxy cannot be started by KAT
- CMLK-743 — Invalid component control command issued
- CMLK-747 — Preliminary command summary message
- CMLK-748 — Command can be applied to Kernun proxies only
- CMLK-749 — Component control command failed to finish
- CMLK-751 — Incorrect call of KAT command
- CMLK-756 — Log rotation command invalid
- CMLK-820 — KAT APPLY command is executed
- CMLK-821 — Exporting system configuration to tarball
- CMLK-825 — Revoking old configuration requested
- CMLK-830 — KAT is sending signal to one or more application processes
- CMLK-841 — General Kernun component start/stop execution message
- CMLK-849 — Kernun component control command successfully issued
- CMLK-856 — Log rotation command execution message
- CMLK-857 — Old log file compression started
- CMLM-115 — Configuration overwriting warning
- CMLM-540 — CML configuration node verification failed
- CMLM-620 — Auditor mode startup
- CMLM-621 — Issued command denied in read-only mode
- CMLM-701 — Configuration consistency warning
- CMLM-702 — Configuration consistency warning
- CMLM-703 — Configuration consistency warning
- CMLM-712 — CML Load operation interrupted by user
- CMLM-713 — CML /SAVE operation not completed
- CMLM-714 — CML command-line options incompatible
- CMLM-720 — Unknown CML command name
- CMLM-721 — CML command misuse
- CMLM-722 — Invalid arguments of CML command
- CMLM-731 — Bad parameter, information not available
- CMLM-732 — Bad parameter, information not available
- CMLM-740 — Bad parameter, target node invalid
- CMLM-741 — RCS operations not allowed without source file specified
- CMLM-750 — Multinode operation allowed only for structured comments
- CMLM-751 — Clipboard change message
- CMLM-790 — RCS command terminal message
- CMLM-799 — RCS command terminal message
- CMLR-113 — Include file path is invalid
- CMLR-510 — Configuration version inconsistency
- CMLR-511 — Configuration file incomplete
- CMLR-512 — Configuration file probably corrupted
- CMLR-513 — Configuration root path setting failed
- CMLR-515 — Include directive failed for some reason
- CMLR-518 — Configuration file probably corrupted
- CMLR-519 — Configuration file not loaded after previous errors
- CMLR-530 — Incorrect CML path specification
- CMLR-540 — Incorrect high-level configuration command usage
- CMLR-542 — CML include file content incorrect
- CMLR-543 — Compound comment syntax error
- CMLR-550 — General CML syntax error message
- CMLR-551 — CML parser detected syntax error
- CMLR-552 — Section format error
- CMLR-560 — Item completeness error
- CMLR-564 — Excluding member misuse
- CMLR-565 — Configuration directive not closed properly
- CMLR-566 — List definition misformed
- CMLR-567 — Item definition misformed
- CMLR-569 — Item completeness error
- CMLR-570 — Variable definition misformed
- CMLR-571 — Variable definition misformed
- CMLR-572 — Variable definition misformed
- CMLR-573 — Variable definition misformed
- CMLR-574 — CML SWITCH command syntax error
- CMLR-575 — CML SWITCH/CASE command syntax error
- CMLR-580 — CML parser detected syntax error
- CMLR-581 — CML parser detected syntax error
- CMLR-582 — CML parser detected syntax error
- CMLR-583 — CML parser detected syntax error
- CMLR-584 — CML parser detected syntax error
- CMLR-585 — CML parser detected syntax error
- CMLR-586 — CML parser detected syntax error
- CMLR-587 — CML SWITCH/CASE command syntax error
- CMLR-590 — Configuration directive misformed
- CMLR-591 — Configuration directive misformed
- CMLR-592 — Configuration directive misformed
- CMLR-593 — Configuration directive specified twice
- CMLR-710 — Final loading result message
- CMLR-712 — Configuration loading was aborted
- CMLR-713 — INCLUDE statements with relative paths found
- CMLR-720 — Operation not allowed in this point of configuration
- CMLR-721 — Improper use of /EDIT command
- CMLR-732 — CML command parameter invalid
- CMLR-770 — Incorrect variable definition
- CMLS-110 — Configuration file cannot be opened
- CMLS-114 — Configuration was not succesfully saved
- CMLS-311 — Inline-file line format invalid
- CMLS-321 — Variable or sublist tree too deep
- CMLS-501 — Incorrect variable usage
- CMLS-505 — Incorrect for loop usage
- CMLS-506 — Incorrect variable application
- CMLS-507 — CML SWITCH command incompleteness found
- CMLS-510 — Inline-file line format invalid
- CMLS-511 — Inline-file line format invalid
- CMLS-540 — Meaningless ACL found
- CMLS-541 — ACL level 1 inconsistency
- CMLS-551 — Incorrect for loop usage
- CMLS-561 — Two SHARED files/directories have the same name
- CMLS-569 — Shared file or directory check failed
- CMLS-719 — Bad filter parameter of /SHOW command
- CMLT-302 — Name chosen is not allowed
- CMLT-501 — Name chosen is not allowed
- CMLT-502 — Name chosen is not allowed
- CMLT-521 — Incorrect variable usage
- CMLT-530 — Reference leading toward end of configuration
- CMLT-533 — Variable/path incosistency warning
- CMLT-534 — Variable or reference invalid
- CMLT-539 — Incorrect value used in CML
- CMLT-540 — Incorrect CML path construction
- CMLT-541 — Incorrect CML path construction
- CMLT-542 — Incorrect CML path construction
- CMLT-543 — Incorrect CML path construction
- CMLT-544 — Incorrect CML path construction
- CMLT-545 — Incorrect CML path construction
- CMLT-548 — Incorrect CML path construction
- CMLT-549 — Path continuation invalid
- CMLT-550 — Reference chain loops back
- CMLT-551 — CML reference invalid
- CMLT-556 — CML reference invalid
- CMLT-559 — Undefined value referenced
- CMLT-560 — Integer value incompatibility
- CMLT-561 — Mnemonic name misuse
- CMLT-562 — IP address used is invalid
- CMLT-563 — Overlapping range is to be added to list
- CMLT-564 — Item element value incorrect
- CMLT-565 — SOCK type incompatibility warning
- CMLT-566 — Inline-file specification incorrect
- CMLT-567 — Denied format of value used in CML
- CMLT-568 — List value inconsistency
- CMLT-569 — Type and value inconsistency
- CMLT-570 — Configuration redundancy warning
- CMLT-572 — Name chosen is not allowed
- CMLT-573 — ACL name '*' inconsistency
- CMLT-574 — Dynamic names for some section types unimplemented
- CMLT-575 — CML SWITCH command syntax error
- CMLT-577 — Illegal sections in for-loop definition
- CMLT-578 — Context inconsistency warning
- CMLT-579 — Section variable definition incorrect
- CMLT-583 — String concatenation is allowed in variable definition only
- CMLT-584 — Parameter declaration misplaced
- CMLT-589 — Top level section misuse
- CMLT-591 — Parametrized variable misuse
- CMLT-592 — Parametrized variable misuse
- CMLT-593 — List tail meaningless
- CMLT-594 — List not closed by regular member
- CMLT-599 — Name specification syntax error
- CMLT-720 — Operation not allowed in this point of configuration
- CMLT-722 — Clipboard empty
- CMLT-723 — Cannot undelete node
- CMLT-724 — Undelete not possible
- CMLT-770 — CML operation not allowed due to context check
- CMLT-771 — Incorrect CML edit operation
- CMLT-772 — CML command misuse
- CMLT-773 — Some member of multiitem clipboard is not valid for pasting
- CMLT-774 — Clipboard containing more items cannot be renamed
- CMLT-800 — CML configuration identification report
- CMLT-801 — CML configuration CDF version report
- CMLT-802 — CML configuration root path report
- CMLT-803 — CML configuration origin report
- CWBP-707 — Bypass has not been activated or has expired and must be reactivated
- CWBP-708 — The bypass activation page has not been returned to the proxy in time
- CWBP-709 — Bypass cannot be activated due to an internal error
- CWBP-710 — Bypass Cookie header prepared
- CWBP-711 — Maximum number of bypass sessions has been reached
- CWBP-712 — Bypass has been activated for a set of categories
- CWBP-717 — Bypass is disabled due to an internal error in the bypass table
- CWBP-718 — A URL is temporarily accessible due to bypass
- CWDB-716 — A set of categories has been looked up in the Clear Web DataBase
- DHCP-523 — DHCP subnet and address definition inconsistent
- DHCP-540 — DHCP failover configuration needs RANGE specified
- DHDR-710 — Document header syntax error
- DHDR-711 — Document header syntax error
- DHDR-712 — Document header syntax error
- DHDR-713 — Document header syntax error
- DHDR-721 — Document header syntax error
- DNSC-001 — Zone name not found in cache
- DNSC-002 — Domain name not found in cache
- DNSC-192 — Cannot get list of IP addresses
- DNSC-580 — No valid root server record for zone
- DNSC-590 — Non-periodical cleanup did not clear cache sufficiently
- DNSC-600 — Received answer contains our own address to be queried
- DNSC-700 — Cache storing function finds resource record of incorrect type
- DNSC-701 — Resolving process cannot continue due to incorrect answer
- DNSC-702 — Resource record set contains no valid authority records
- DNSC-705 — Glue records missing
- DNSC-750 — DNS server EDNS parameters announcement
- DNSC-897 — Cache cleanup efectivity report
- DNSC-898 — Cache cleanup final report
- DNSC-899 — Cache capacity report
- DNSC-980 — No valid server record for domain
- DNSE-001 — Request state is invalid
- DNSE-003 — Event on socket non belonging to any request
- DNSE-012 — Used socket registered by another request
- DNSE-013 — Request tried to open second server connection
- DNSE-097 — Invalid event in particular request state
- DNSE-105 — ALTQ queue assigment has failed
- DNSE-109 — Syscall select() in main proxy loop failed
- DNSE-120 — Binding to a random port failed
- DNSE-130 — Getting a socket or preparing it to work failed
- DNSE-210 — Reading request from UDP socket failed
- DNSE-211 — Accepting connection on TCP socket failed
- DNSE-212 — Reading request from TCP connection failed
- DNSE-218 — Timeout expired when reading DNS query or response
- DNSE-219 — Client closed TCP connection
- DNSE-221 — Connection to server failed
- DNSE-228 — Reading reply from DNS server failed
- DNSE-230 — Sending request to server failed
- DNSE-239 — Server has closed connection during sending query to it
- DNSE-240 — Reading reply from server failed
- DNSE-249 — Server closed TCP connection
- DNSE-260 — Reply was not sent to client
- DNSE-269 — Client has closed connection during sending reply to it
- DNSE-300 — Request table is exhausted
- DNSE-301 — Sockets table is exhausted
- DNSE-308 — DNS request table monitoring message
- DNSE-309 — Requests table dump final info
- DNSE-310 — Received query length exceeds allowed size
- DNSE-340 — Reading reply from server failed
- DNSE-342 — UDP reply from server exceeds 512 bytes
- DNSE-360 — Proxy cannot send response via TCP
- DNSE-361 — Reply is too long, it could cause problem to resolver
- DNSE-390 — Cannot connect server due to long name
- DNSE-590 — Proxy tried all possible forwarders getting no answer
- DNSE-612 — Named DNS operation not implemented
- DNSE-613 — Only single-query requests implemented
- DNSE-614 — Named resource record class not implemented
- DNSE-615 — DNS extensions denied in configuration
- DNSE-670 — Request/response contains unimplemented version of EDNS
- DNSE-710 — Received query/response is shorter than minimal size
- DNSE-711 — Request is formally incorrect
- DNSE-712 — Named DNS operation not known
- DNSE-713 — Request must contain exactly one QUERY
- DNSE-714 — Query resource record contains unknown class
- DNSE-715 — IXFR query with invalid NS part
- DNSE-716 — Bad transport protocol for AXFR request
- DNSE-740 — Proxy received reply with unexpected response code
- DNSE-741 — Query section of the answer does not match one of request
- DNSE-742 — Nameserver response contains invalid flags
- DNSE-743 — Zone transfer response does not start with SOA
- DNSE-744 — Incremental zone transfer response does not end with proper SOA
- DNSE-745 — Misformed response from server
- DNSE-749 — Server connection is not idle
- DNSE-750 — Too deep recursion of internal requests
- DNSE-760 — DNS request cancelled due response limit expiration
- DNSE-790 — Proxy tried all possible servers getting no answer
- DNSE-791 — Retry of request is not allowed
- DNSE-792 — Information about domain contains no glue record
- DNSE-793 — Querying to name loops back to itself
- DNSE-794 — Reasonable amount of attempts exhausted
- DNSE-795 — Informational output of requests dependency
- DNSE-798 — Internal request final report
- DNSE-799 — Request timed out
- DNSI-500 — Section LISTEN-ON contains incorrect address
- DNSP-010 — Searching of ACL failed
- DNSP-500 — Zone transfer cannot be resolved
- DNSP-510 — Cannot force source address in dns-proxy
- DNSP-610 — Request is not covered by configuration
- DNSP-641 — Reply resource record policy decision
- DNSP-649 — Reply resource record not found in configuration
- DNSP-700 — Notification about the mode of operation of the proxy
- DNSP-701 — The proxy has been initialized and is ready to accept packets
- DNSP-708 — The proxy has unbound the sockets used for listening for clients
- DNSP-709 — Final proxy termination message
- DNSP-710 — Proxy runtime monitoring support cannot be initialized
- DNSP-723 — The proxy has finished
- DNSP-808 — Session has started, client connection has arrived
- DNSP-809 — DNS session finished
- DNSP-810 — ACL decision has been made, operation either accepted or rejected
- DNSP-820 — ACL decision has been made, operation either accepted or rejected
- DNSP-860 — Request processing finished
- DNSP-888 — Unified DNS proxy statistics message
- DNSR-001 — Name or label being stored is too long
- DNSR-011 — Resource record of unknown type being stored
- DNSR-301 — Read domain name exceeds 254 characters
- DNSR-310 — DNS message RR count limit reached
- DNSR-630 — Answer resource record has class oher than IN
- DNSR-631 — Answer resource record has unimplemented or incorrect type
- DNSR-653 — Query resource record type unimplemented
- DNSR-654 — Reply resource record type unimplemented
- DNSR-702 — Label contains incorrect character
- DNSR-703 — Token does not start with 00 or 11 bits couple
- DNSR-704 — Token length exceeds end of block
- DNSR-705 — Token references offset greater than offset of itself
- DNSR-710 — Resource record length differs from length field value
- DNSR-711 — Resource record exceeds block boundary
- DNSR-712 — Misformed CAA resource record
- DNSR-716 — Misformed DNS packet correction
- DNSR-717 — Received block length disagree with total length of resource records
- DNSR-718 — Received block length disagree with total length of resource records
- DNSR-719 — Resource record formally incorrect
- DNSR-730 — Nameserver response inconsistency message
- DNSR-731 — General appearance incorrectness message
- DNSR-732 — DNS reply contains incorrect CNAME
- DNSR-734 — Irrelevant additional record found
- DNSR-735 — Nameserver response contains invalis CNAME chain
- DNSR-753 — Query resource record type unknown
- DNSR-754 — Reply resource record type unknown
- DNSR-760 — EDNS0 OPT RR must close ADDITIONAL section
- DNSR-761 — EDNS0 OPT RR must have empty name
- DNSX-501 — QUERY or REPLY item will never act
- DNSX-502 — No QUERY item contains operation requiring REPLY/FAKE definition
- DNSX-503 — No REPLY item found in forwarding or resolving ACL
- DNSX-510 — Faked name is longer then 254 characters
- DNSX-511 — Faked name label is longer then 64 characters
- DNSX-512 — Faked name contains invalid character
- DNSX-513 — Faked address is not of proper type
- DNSX-520 — Regexps used for query name matching must end with dot
- FTPH-050 — FTP server directory format unknown
- FTPH-710 — Internal HTTP to FTP protocol error
- FTPH-711 — Internal HTTP to FTP protocol error
- FTPH-712 — Internal HTTP to FTP protocol error
- FTPH-713 — Internal HTTP to FTP protocol error
- FTPH-714 — Internal HTTP to FTP protocol error
- FTPH-715 — Internal HTTP to FTP protocol error
- FTPH-716 — Internal HTTP to FTP protocol error
- FTPH-739 — Resending FTP server reply to HTTP proxy
- FTPH-750 — FTP directory listing not understood
- FTPP-090 — TCP server returned with error
- FTPP-099 — Final startup failure message
- FTPP-573 — Proxy probably uses reserved port and will not operate
- FTPP-808 — Session has started, client connection has arrived
- FTPP-809 — Session finished
- FTPP-888 — Unified TCP proxy statistics message
- FTPS-009 — Answer prepared for client has no response code
- FTPS-100 — FTP proxy control channel initialisation failed
- FTPS-105 — ALTQ queue assigment has failed
- FTPS-110 — Searching of ACL failed
- FTPS-119 — Authentication system is unsable
- FTPS-131 — Connection to server failed
- FTPS-230 — Target server name cannot be resolved to IP address
- FTPS-232 — Target server connection failed
- FTPS-234 — Targer server response invalid
- FTPS-238 — I/O operation on socket failed
- FTPS-239 — Control socket closed by peer
- FTPS-341 — Client reply buffer is over
- FTPS-342 — Data command parameter exceeded internal buffer size
- FTPS-530 — Next-hop server/proxy name cannot be resolved to IP address
- FTPS-532 — Next-hop server/proxy connection failed
- FTPS-534 — Next-hop server/proxy response invalid
- FTPS-628 — User illegally requested connection to non-ftp port
- FTPS-640 — FTP command has been rejected
- FTPS-642 — Simple username expected
- FTPS-643 — Username should contain target server
- FTPS-644 — Password must combine proxy user's and remote user's ones
- FTPS-679 — PORT family command has illegal parameter
- FTPS-690 — Data transfer size limit exceeded
- FTPS-691 — Data transfer size limit exceeded
- FTPS-701 — Timeout reached
- FTPS-710 — Too many commands used prior to connecting to server
- FTPS-732 — Command not allowed if target server known
- FTPS-738 — Remote server has answered with error message
- FTPS-739 — Remote server has logically closed session
- FTPS-744 — RNTO received without RNFR
- FTPS-745 — Proxy received an unknown command
- FTPS-746 — FTP command syntax error
- FTPS-747 — FTP initialisation command USER/PASS duplicated
- FTPS-748 — User setting required
- FTPS-749 — Port required by user is invalid
- FTPS-771 — Received EPSV command with bad argument
- FTPS-773 — Data transfer parameter commands invalid if EPSV ALL is set
- FTPS-774 — PORT family command contains bad argument
- FTPS-791 — Reissuing the REST command failed
- FTPS-810 — ACL decision has been made, operation either accepted or rejected
- FTPS-819 — Proxy user authentication finished
- FTPS-820 — ACL decision has been made, operation either accepted or rejected
- FTPS-840 — FTP command received
- FTPS-870 — File Transfer Protocol command handling
- FTPT-001 — Wrong address of server requested
- FTPT-101 — FTP proxy data channel initialisation failed
- FTPT-105 — ALTQ queue assigment has failed
- FTPT-110 — Searching of ACL failed
- FTPT-119 — Cannot recognize document type
- FTPT-181 — Data connection accept failed
- FTPT-280 — Data connection to peer cannot be established
- FTPT-281 — Cannot create listening socket for data transfer
- FTPT-288 — Data connection not established
- FTPT-289 — Another data connection arrived
- FTPT-600 — Data arrived from wrong peer
- FTPT-688 — PASV family command response contains bad address
- FTPT-689 — Data connection arrived from bad peer
- FTPT-690 — Data transfer size limit exceeded
- FTPT-702 — Listening timeout expired
- FTPT-746 — FTP command syntax error
- FTPT-772 — Received repeated data transfer parameter command
- FTPT-788 — PASV family command response invalid
- FTPT-830 — ACL decision has been made, operation either accepted or rejected
- FTPT-872 — Client used data command without transfer parameter setting
- FTPT-880 — Data transfer initialized
- FTPT-881 — Data connection server established
- FTPT-890 — Data transfer stopped
- H225-300 — Parser ran out of read buffer
- H225-700 — Unrecoverable H.323 parser error
- H225-710 — Received packet with unimplemented H.323 feature
- H225-720 — Received packet with more RAS/CSA addresses
- H245-700 — Unrecoverable H.323 parser error
- H245-710 — Received packet with unimplemented H.323 feature
- H245-711 — Received packet with unimplemented H.323 feature
- HTCT-100 — An operation with the cookie table failed
- HTCT-102 — An operation with the cookie table failed
- HTCT-104 — An operation with the cookie table failed
- HTCT-105 — An operation with the cookie table failed
- HTCT-107 — An operation with the cookie table failed
- HTCT-108 — An operation with the cookie table failed
- HTCT-800 — A cookie has been received from other client than expected
- HTCW-100 — Closing a Clear Web DataBase file failed
- HTCW-101 — Opening a Clear Web DataBase file failed
- HTCW-102 — Reading all records from a Clear Web DataBase file failed
- HTCW-103 — The Clear Web DataBase cannot test whether its database was changed
- HTCW-104 — Search operation in the Clear Web DataBase file failed
- HTCW-105 — Inserting a record into the Clear Web DataBase file failed
- HTCW-106 — Deleting a record from the Clear Web DataBase file failed
- HTCW-700 — The Clear Web DataBase cannot open its updated database file
- HTTA-100 — AProxy session table initialization failed
- HTTA-101 — AProxy session table initialization failed
- HTTA-102 — A new proxy process cannot use the session table
- HTTA-157 — AProxy session table lock cannot be unlocked
- HTTA-500 — AProxy session table must have non-zero size
- HTTA-502 — Required item OOB_AUTH-SRV missing in configuration
- HTTA-600 — An error occurred when calling authentication functions
- HTTA-601 — RADIUS state does not fit into the session table entry
- HTTA-710 — Information about OOB user authentication
- HTTA-720 — Information about AProxy user authentication
- HTTA-801 — Client returned invalid authentication data to AProxy
- HTTA-802 — AProxy session table lock cannot be locked
- HTTA-803 — Maximum number of sessions reached, no new session cannot be created
- HTTA-804 — User name does not fit into the session table entry
- HTTA-805 — Client returned invalid contents of the authentication form to AProxy
- HTTA-806 — AProxy cannot prepare the authentication form
- HTTA-807 — List of groups does not fit into the session table entry
- HTTA-808 — OOB external authentication produces too long lines
- HTTA-809 — OOBA update list line not understood
- HTTA-810 — Unterminated line at the end of an OOBA update list is ignored
- HTTA-811 — An OOB-authenticated user cannot be found in LDAP
- HTTA-812 — A user tried logout without previous login
- HTTA-813 — Authentication form incorrectly filled/sent
- HTTA-858 — AProxy cannot decode the request
- HTTF-800 — The proxy cannot convert FTP directory listing into an HTML page
- HTTF-801 — The proxy cannot convert FTP directory listing into an HTML page
- HTTF-802 — The proxy cannot convert FTP directory listing into an HTML page
- HTTH-025 — Invalid method number in parsed request line
- HTTH-101 — The proxy cannot replace credentials
- HTTH-102 — The proxy cannot replace credentials
- HTTH-105 — ALTQ queue assigment has failed
- HTTH-300 — The response body is shorter than expected according to Content-Length
- HTTH-600 — Kerberos authentication has failed
- HTTH-702 — A new request has been started
- HTTH-703 — Information about user authentication on the proxy
- HTTH-704 — A URL is temporarily accessible due to bypass
- HTTH-705 — Bypass has been activated for a single domain
- HTTH-706 — Bypass life time has expired and must be reactivated
- HTTH-707 — Bypass has not been activated or has expired and must be reactivated
- HTTH-708 — The bypass activation page has not been returned to the proxy in time
- HTTH-709 — Bypass cannot be activated due to an internal error
- HTTH-711 — Maximum number of bypass sessions has been reached
- HTTH-712 — Bypass has been activated for a set of categories
- HTTH-713 — A request has terminated
- HTTH-714 — A request has terminated
- HTTH-715 — Detail request information
- HTTH-716 — A set of categories has been looked up in the Clear Web DataBase
- HTTH-717 — Bypass is disabled due to an internal error in the bypass table
- HTTH-718 — A URL is temporarily accessible due to bypass
- HTTH-741 — Proxy repairs invalid Host request header
- HTTH-750 — Data from server were rejected by antivirus checking
- HTTH-788 — Cannot set the value of the IP packet TOS field
- HTTH-789 — Kerberos authentication cannot obtain group information from LDAP
- HTTH-790 — An unsupported authentication header has been received
- HTTH-791 — Negotiate authentication data format is invalid
- HTTH-792 — The proxy cannot initialize client CONNECT data filtering
- HTTH-793 — The proxy cannot initialize server CONNECT data filtering
- HTTH-794 — The proxy cannot perform NTLM authentication
- HTTH-795 — NTLM authentication data format is invalid
- HTTH-796 — The proxy cannot execute an external program
- HTTH-797 — Bad format of a cookie deletion request
- HTTH-798 — Matching of request body data not possible
- HTTH-799 — Matching of response data not possible
- HTTH-800 — Cannot decode the server response due to an unsupported encoding
- HTTH-801 — Http-proxy cannot communicate with ftp-proxy
- HTTH-802 — Connection of http-proxy with ftp-proxy, is not configured
- HTTH-803 — The client has not sent compulsory HTTP/1.1 Host header
- HTTH-804 — Challenge/response proxy authentication is not supported
- HTTH-805 — The request URI has been invalidated by a rewrite operation
- HTTH-806 — The request specifies an unsupported scheme
- HTTH-807 — Setup for request body decoding failed
- HTTH-808 — Setup for request body encoding failed
- HTTH-809 — The proxy cannot initialize the image filtration module
- HTTH-810 — The proxy received the status line from the server twice
- HTTH-811 — Reports REQUEST-ACL used for this request
- HTTH-812 — HTTP header name contains an illegal character
- HTTH-813 — HTTP header does not contain the colon separating name and value
- HTTH-814 — Repeated HTTP header which may occur only once
- HTTH-815 — Value of a HTTP header is invalid and cannot be parsed
- HTTH-816 — Internal form of a HTTP header is invalid
- HTTH-817 — Repeated HTTP header which may occur only once
- HTTH-818 — HTTP request line must contain a HTTP method
- HTTH-819 — HTTP request line must contain a HTTP request URI
- HTTH-820 — HTTP version in request or response is invalid
- HTTH-821 — Something invalid at the end of the HTTP request line
- HTTH-822 — A bad %xx sequence in URI has been encountered
- HTTH-823 — Internal form of URI is invalid
- HTTH-824 — Internal form of HTTP version is invalid
- HTTH-825 — Internal form of HTTP request line is invalid
- HTTH-826 — Status line must contain version identifier
- HTTH-827 — Status line must contain a valid status code
- HTTH-828 — Internal form of HTTP status line is invalid
- HTTH-829 — Internal form of a HTTP header is invalid
- HTTH-830 — Unknown type of authentication
- HTTH-831 — URI cannot be parsed
- HTTH-832 — Only GET method is allowed in HTTP v. 0.9 requests
- HTTH-833 — Received HTTP message has an unsupported version of HTTP
- HTTH-834 — Content-Length header contains an invalid value
- HTTH-835 — Request or status line is forbidden by REQUEST-ACL
- HTTH-836 — Request or response header is forbidden by REQUEST-ACL
- HTTH-837 — Request failed due to inoperative web filter
- HTTH-838 — Invalid HTTP status code in response from server
- HTTH-839 — Request continues despite web filter failure
- HTTH-840 — Proxy cannot configure NAT address mapping on connection to server
- HTTH-841 — Proxy cannot initialize data related to server connection
- HTTH-842 — Proxy cannot create modules for communication with the server
- HTTH-843 — Proxy cannot create module for sending CONNECT response headers
- HTTH-844 — The proxy cannot process response headers
- HTTH-845 — An unexpected error occurred when searching REQUEST-ACLs
- HTTH-846 — The request is denied because it does not match any REQUEST-ACL
- HTTH-847 — Matching REQUEST-ACL contains item DENY
- HTTH-848 — Request URI has a form unsupported by http-proxy
- HTTH-849 — A file to be sent as a response does not exist or is not readable
- HTTH-850 — Antivirus has reported a virus
- HTTH-851 — The proxy is unable to verify user authentication
- HTTH-852 — The proxy cannot establish an SSL/TLS secure channel to the server
- HTTH-853 — The request specifies an unsupported scheme
- HTTH-854 — AProxy is enabled in the configuration, but cannot be initialized
- HTTH-855 — FTP requests allow only downloading (GET) and uploading (PUT) data
- HTTH-856 — HTTP Host header contains an invalid port number
- HTTH-857 — Proxy cannot interpret Transfer-Encoding header
- HTTH-858 — Transfer-Encoding header defines an incorrect encoding
- HTTH-859 — Transfer-Encoding header defines an incorrect encoding
- HTTH-860 — Communication with a FTP server failed
- HTTH-861 — A file to be sent as a response does not exist or is not readable
- HTTH-862 — The proxy cannot decode chunked trasfer encoding of response
- HTTH-863 — The proxy cannot use an external program to reply to a request
- HTTH-864 — Cannot decode the server response due to an unsupported encoding
- HTTH-865 — Proxy informs the client about an unsupported content encoding
- HTTH-866 — The proxy cannot encode the response into the chunked encoding
- HTTH-867 — The proxy cannot decode a gzipped response
- HTTH-868 — The proxy cannot perform requested HTML filtration
- HTTH-869 — The proxy cannot return a directory listing obtained from ftp-proxy
- HTTH-870 — The proxy cannot send the response to the antivirus
- HTTH-871 — The client has closed the connection when it should not
- HTTH-872 — The request line is wrong
- HTTH-873 — A request cannot escape from a subdirectory
- HTTH-874 — The request headers are wrong
- HTTH-875 — Proxy cannot configure NAT address mapping on connection to ftp-proxy
- HTTH-876 — Forwarding the request to ftp-proxy failed
- HTTH-877 — Request line processing failed
- HTTH-878 — The request line does not fit into the appropriate buffer
- HTTH-879 — Request header processing failed
- HTTH-880 — A request line does not fit into the appropriate buffer
- HTTH-881 — The server has closed the connection when it should not
- HTTH-882 — The status line is wrong
- HTTH-883 — A cookie modification failed
- HTTH-884 — The response headers are wrong
- HTTH-885 — Status line processing failed
- HTTH-886 — The status line does not fit into the appropriate buffer
- HTTH-887 — Response header processing failed
- HTTH-888 — A response line does not fit into the appropriate buffer
- HTTH-889 — The request would require the proxy to connect back to itself
- HTTH-890 — HTTP header value contains an illegal character
- HTTH-891 — Repeated HTTP header which may occur only once
- HTTH-892 — An unexpected error occurred when searching DOC-ACLs
- HTTH-893 — Reports DOC-ACL used for this request
- HTTH-894 — The request is denied because it does not match any DOC-ACL
- HTTH-895 — Matching DOC-ACL contains item DENY
- HTTH-896 — Proxy cannot use the module for guessing MIME types
- HTTH-897 — The server has specified response body length incorrectly
- HTTH-898 — The client has specified request body length incorrectly
- HTTH-899 — The proxy is unable to verify user authentication
- HTTH-901 — The proxy cannot extract lifetime information from a cookie
- HTTH-923 — Proxy requests user authentication
- HTTH-924 — Proxy authentication request sent to client
- HTTH-925 — Proxy authentication request sent to client
- HTTH-926 — Cannot create SSL/TLS with buffer
- HTTH-927 — SSL/TLS accept did not fail with expected error
- HTTH-928 — Client did not send anything
- HTTH-929 — Skipping SNI inspection in unknown protocol
- HTTH-930 — Skipping SNI inspection in SSLv3
- HTTH-931 — Skipping SNI inspection because message size from SSL/TLS header does not match data size
- HTTH-932 — Skipping SNI inspection in unknown protocol
- HTTH-934 — Skipping SNI inspection in Skype protocol
- HTTH-935 — Accept-Encoding header parsing failed
- HTTH-936 — Skipping SNI inspection in empty message
- HTTH-937 — SNI inspection resulted in an error
- HTTP-104 — The main loop for serving clients (tcpserver) failed
- HTTP-105 — ALTQ queue assigment has failed
- HTTP-123 — Blacklist database cannot be used
- HTTP-124 — The proxy cannot use SSL/TLS
- HTTP-125 — The table for storing modified cookie cannot be initialized
- HTTP-126 — The proxy cannot delete stored cookie values
- HTTP-127 — The proxy cannot get a Kerberos ticket for LDAP
- HTTP-501 — AProxy configuration error
- HTTP-502 — AProxy configuration error
- HTTP-710 — A new proxy session has been started
- HTTP-711 — A proxy session has terminated
- HTTP-712 — Session ACLs have been processed
- HTTP-740 — Connecting to server in SSL/TLS inspection
- HTTP-741 — No SNI specified
- HTTP-801 — Error during initial processing of a new session
- HTTP-802 — The next request on a persistent connection cannot be processed
- HTTP-803 — Error during initialization of a new request
- HTTP-804 — The client has closed the connection to the proxy
- HTTP-810 — The proxy is unable to respond with a local file
- HTTP-811 — The proxy is unable to respond with a local file
- HTTP-812 — The proxy is unable to respond with a local file
- HTTP-813 — Data size limit has been exceeded
- HTTP-814 — Data size limit has been exceeded
- HTTP-815 — Data size limit has been exceeded
- HTTP-816 — Data size limit has been exceeded
- HTTP-817 — An unexpected error occurred when searching SESSION-ACLs
- HTTP-818 — The session is denied because it does not match any SESSION-ACL
- HTTP-819 — Matching SESSION-ACL contains item DENY
- HTTP-820 — The proxy captured a CONNECT request and will handle it itself
- HTTP-821 — The proxy creates a TCP tunnel to the server
- HTTP-822 — A shared library cannot be used
- HTTP-823 — A shared library does not contain a required function
- HTTP-824 — A shared library cannot be initialized
- HTTP-825 — The proxy is unable to respond with locally generated data
- HTTP-826 — SNI was inspected, now HTTPS will be inspected
- HTTP-852 — The proxy cannot establish an SSL/TLS secure channel from the client
- HTTP-888 — Unified HTTP proxy statistics message
- HTTX-540 — Incomplete FAKE-CERT configuration
- HTTX-810 — Cannot use FAKE-CERT on server SSL
- HTTX-811 — Server SSL must be defined when FAKE-CERT used
- HTTX-812 — Cannot define server SSL when FAKE-CERT not used
- HTTX-813 — SNI-INSP must be defined in SSL-PARAMS referenced by SNI-SSL
- HTTX-814 — SNI-INSP cannot be defined in SSL-PARAMS referenced by CLIENT-SSL
- HTTX-815 — SNI-INSP cannot be defined in SSL-PARAMS referenced by SERVER-SSL
- HTTX-816 — CAPTURED-CONNECT request will fail when SNI-RESULT is UNKNOWN-PROTOCOL
- HTTX-817 — CAPTURED-CONNECT request will fail when SNI-RESULT is SKYPE
- ICAB-700 — Received ICAP message has unsupported version of ICAP
- ICAB-701 — ICAP version in request is invalid
- ICAB-710 — ICAP request line misformed
- ICAB-711 — Request line ends incorrectly
- ICAB-720 — ICAP Encapsulation header is syntactically incorrect
- ICAB-725 — ICAP Host header contains invalid port number
- ICAB-730 — Unknown type of authentication
- ICAP-888 — Unified ICAP server statistics message
- ICAR-120 — An unexpected error occurred when searching REQUEST-ACLs
- ICAR-140 — Setup for request body decoding failed
- ICAR-150 — Proxy cannot use the module for guessing MIME types
- ICAR-160 — ICAP server cannot send data to the antivirus
- ICAR-170 — ICAP server cannot establish chunked encoding of data
- ICAR-200 — ICAP client has closed connection in improper situation
- ICAR-580 — The status line does not fit into the appropriate buffer
- ICAR-581 — A response line does not fit into the appropriate buffer
- ICAR-620 — Matching SERVICE-ACL contains item DENY
- ICAR-621 — The request is denied because it does not match any SERVICE-ACL
- ICAR-625 — Matching REQUEST-ACL contains item DENY
- ICAR-626 — The request is denied because it does not match any REQUEST-ACL
- ICAR-630 — Matching DOC-ACL contains item DENY
- ICAR-631 — The request is denied because it does not match any DOC-ACL
- ICAR-711 — ICAP request line sent by client is wrong
- ICAR-712 — ICAP request headers are wrong
- ICAR-713 — Error occured when reading HTTP headers encapsulated in ICAP request
- ICAR-715 — Received ICAP request with unsupported feature
- ICAR-716 — Client has not sent compulsory Host header
- ICAR-727 — Challenge/response server authentication is not supported
- ICAR-728 — Proxy requests user authentication
- ICAR-729 — ICAP server is unable to verify user authentication
- ICAR-740 — Errorneous or duplicite Encapsulated header
- ICAR-760 — HTTP request within ICAP request does not contain Host header
- ICAR-761 — Antivirus check final result report
- ICAR-810 — A new request has been started
- ICAR-818 — Summary of HTTP session being inspected by ICAP server
- ICAR-819 — A request has terminated
- ICAR-820 — Reports SERVICE-ACL used for this request
- ICAR-825 — Reports REQUEST-ACL used for this request
- ICAR-829 — Information about user authentication on server
- ICAR-830 — Reports DOC-ACL used for this request
- ICAS-090 — TCP server returned with error
- ICAS-099 — Final startup failure message
- ICAS-111 — Blacklist database cannot be used
- ICAS-130 — Error during initial processing of a new session
- ICAS-131 — The next request on a persistent connection cannot be processed
- ICAS-132 — ICAP server cannot establish an SSL/TLS secure channel from the client
- ICAS-133 — ALTQ queue assigment has failed
- ICAS-139 — Error during initialization of a new request
- ICAS-150 — The server is unable to respond with a local file
- ICAS-191 — ICAP server cannot use SSL/TLS
- ICAS-210 — Client has improperly closed connection
- ICAS-220 — Client exceeded maximum time between requests
- ICAS-230 — Client exceeded maximum time for request completing
- ICAS-330 — Data size limit has been exceeded
- ICAS-621 — Session denied due to no matching SESSION-ACL
- ICAS-622 — Matching SESSION-ACL contains item DENY
- ICAS-801 — Session has started, client connection has arrived
- ICAS-809 — Session finished
- ICAS-821 — SESSION-ACL search report
- IFSC-100 — Cannot create socket for interface status checking
- IFSC-101 — Cannot connect to socket for interface status checking
- IFSC-120 — Cannot read from socket for interface status checking
- IFSC-320 — Line read from socket for interface status checking is not understood
- IFSC-710 — Interface status change message
- IFSC-720 — Socket for interface status checking has been closed
- IMAP-100 — The main loop for serving clients (tcpserver) failed
- IMAP-101 — ALTQ queue assigment has failed
- IMAP-200 — Cannot change source address of a connection to a server
- IMAP-201 — The proxy cannot initialize a connection to a server
- IMAP-202 — The proxy cannot initialize a connection to a server
- IMAP-700 — Session ACL has been processed
- IMAP-701 — Command ACL has been processed
- IMAP-702 — A client has been disconnected from the proxy
- IMAP-704 — A new client has connected to the proxy
- IMAP-706 — Information about direction of a mail transfer
- IMAP-710 — A command has been denied by ACL
- IMAP-711 — A capability has been denied by ACL
- IMAP-712 — An unimplemented capability received from the server
- IMAP-713 — An unimplemented command received from the client
- IMAP-760 — Mail ACL has been processed
- IMAP-800 — Proxy initialization failed
- IMAP-801 — An error occurred during searching SESSION-ACLs
- IMAP-802 — The client has been denied by SESSION-ACL
- IMAP-803 — The proxy is unable to verify user authentication
- IMAP-804 — The proxy does not know a server address to connect
- IMAP-805 — Initial processing of a new client connection has failed
- IMAP-806 — Proxy cannot start SSL/TLS on the client connection
- IMAP-807 — Proxy cannot start IMAP4 protocol
- IMAP-808 — An error occurred during searching COMMAND-ACLs
- IMAP-809 — The client has been denied by COMMAND-ACL
- IMAP-810 — Limit for session duration has been reached
- IMAP-811 — The client is sending too much data
- IMAP-812 — The server is sending too much data
- IMAP-813 — Proxy cannot start SSL/TLS on the server connection
- IMAP-814 — The session is being idle for too long
- IMAP-817 — A temporary file cannot be read
- IMAP-818 — A mail from the server cannot be processed
- IMAP-819 — The proxy is unable to get size of a temporary file
- IMAP-820 — The client has unexpectedly disconnected from the proxy
- IMAP-821 — The server has unexpectedly disconnected from the proxy
- IMAP-822 — A FETCH response does not correspond to the FETCH command
- IMAP-823 — Proxy cannot decode length of a literal
- IMAP-824 — A client command line is too long
- IMAP-825 — A server response line is too long
- IMAP-843 — IMAP4 BINARY protocol extension (RFC3516) is not implemented
- IMAP-844 — The proxy does not understand a request for mail data
- IMAP-845 — The proxy detented data which should not occur in a FETCH response
- IMAP-846 — The server response is not a valid mail
- IMAP-847 — Bad format of an IMAP4 command line
- IMAP-848 — A command tag does not fit to a buffer in the proxy
- IMAP-850 — The proxy cannot create a temporary file
- IMAP-851 — The proxy is unable pro process a mail
- IMAP-852 — A mail from client to server is denied by configuration
- IMAP-853 — A mail from client to server is denied by configuration
- IMAP-854 — Bad format of an IMAP4 response line
- IMAP-855 — A response tag does not match the last last command
- IMAP-856 — A response tag does not match the last last command
- IMAP-857 — The proxy is unable to get size of a temporary file
- IMAP-858 — A command tag does not fit to a buffer in the proxy
- IMAP-860 — The proxy cannot create a temporary file
- IMAP-861 — The proxy cannot start processing of a mail
- IMAP-862 — A mail from server to client is denied by configuration
- IMAP-863 — A mail from server to client is denied by configuration
- IMAP-865 — The proxy cannot finish processing of a mail
- IMAP-867 — The client asked for a nonexistent part of a mail
- IMAP-868 — The proxy cannot sent a mail in the form of literal string
- IMAP-870 — There is not cached mail in the proxy
- IMAP-871 — The proxy received unexpected data from the server
- IMAP-888 — Unified IMAP4 proxy statistics message
- IPCL-100 — The proxy cannot create a lock for synchronizing its processes
- IPCL-101 — The proxy cannot write its PID to the lock file
- IPCL-102 — The proxy cannot close a lock file
- IPCL-103 — The proxy cannot delete a lock file
- IPCL-104 — A proxy process cannot open a lock file
- IPCL-106 — A proxy process cannot lock a lock file
- IPCL-107 — A proxy process cannot unlock a lock file
- IPSE-800 — Bad interface referenced in an IPSEC configuration section
- IPSE-801 — No interface referenced in an IPSEC configuration section
- IPSE-802 — Configuration directory of the ISAKMP daemon cannot be generated
- IPSE-803 — The specified DH group value is not allowed
- IPSR-136 — Suricata did not start within the expected time
- IPSR-139 — Suricata failed to within the expected time
- IPSY-100 — Failed to generate the IPS configuration file
- KERN-001 — Function called with NULL parameter
- KERN-002 — Expression has incorrect (NULL) value
- KERN-003 — An unexpected true value of a Boolean expression detected
- KERN-011 — Library function returned unknown return value
- KERN-012 — Application has detected an incorrect value
- KERN-013 — Application has detected an incorrect value
- KERN-020 — Application reached unreachable code
- KERN-100 — System call failed with reported errno
- KERN-510 — Regexp in FROM and TO items are meaningless
- KERN-515 — Address has other address family than expected
- KEYV-701 — Keyword-value parser error
- KEYV-702 — Keyword-value parser error
- KEYV-703 — Keyword-value parser error
- KEYV-704 — Keyword-value parser error
- KEYV-710 — Keyword-value parser error
- KEYV-711 — Keyword-value parser error
- KEYV-751 — Keyword-value parser error
- KEYV-770 — MIME header continuation incomplete
- LDAP-301 — Buffer for ldap filter is too short for storing string "(|(attribute_name=value)(attribute_name=value))"
- LDAP-302 — Buffer for ldap filter is too short for storing string "(attribute_name=value)"
- LDAP-501 — Bad attribute name
- LDAP-502 — Invalid configuration of the server's URI
- LDAP-601 — Bad username
- LDAP-603 — User not found in the LDAP database
- LDAP-607 — Bind to account successful
- LDAP-610 — Bind LDAP server to the user's DN unsuccessful due to invalid credentials
- LDAP-613 — Error when binding to the LDAP server using user's DN
- LDAP-701 — LDAP initialization failed
- LDAP-702 — More than 1 value returned as the group name
- LDAP-703 — Setting LDAP_OPT_X_TLS_KEYFILE failed
- LDAP-704 — More than one object for user found in named LDAP directory
- LDAP-706 — More than one value returned as the users default GID number
- LDAP-707 — ldap_start_tls_s returned error
- LDAP-709 — Error while searching for the user's UID number
- LDAP-710 — Error getting users's DN
- LDAP-711 — Error retrieving group number from the group's node
- LDAP-712 — Error retrieving user's default GID number
- LDAP-713 — Error while searching for the user's GID list
- LDAP-714 — Setting LDAP_OPT_X_TLS_REQUIRE_CERT option failed
- LDAP-715 — Setting LDAP_OPT_TIMEOUT option failed
- LDAP-716 — Setting LDAP_OPT_TIMELIMIT failed
- LDAP-717 — Setting LDAP_OPT_NETWORK_TIMEOUT option failed
- LDAP-718 — Error binding to the LDAP server
- LDAP-721 — Setting LDAP_OPT_PROTOCOL_VERSION option failed
- LDAP-722 — Setting LDAP_OPT_X_TLS_CERTFILE failed
- LDAP-723 — Setting LDAP_OPT_X_TLS_CACERTFILE option failed
- LDAP-724 — Setting LDAP_OPT_X_TLS_CACERTDIR option failed
- LDAP-726 — Error retrieving group number from the group's node
- LDAP-727 — Getting LDAP_OPT_X_TLS_CTX option failed
- LDAP-728 — Setting LDAP_OPT_X_TLS_CTX option failed
- LDAP-729 — List of groups for a user cannot be obtained from Active Directory
- LDAP-730 — List of groups for a user cannot be obtained from Active Directory
- LDAP-731 — List of groups for a user cannot be obtained from Active Directory
- LDAP-732 — List of groups for a user cannot be obtained from Active Directory
- LDAP-733 — Setting LDAP_OPT_REFERRALS failed
- LDAP-734 — Failed to reinitialize the LDAP structure
- LDAP-901 — Unsuscpected behaiour; ldap_result returned unsuspected value
- LIBA-700 — Reports the first user group matched by an ACL
- LIBA-701 — No user groups matched an ACL
- LIBA-810 — Statistical message for R.U.R. analysis
- LIBI-009 — Closing of file descriptor failed
- LIBI-101 — Socket number not applicable to select()
- LIBI-102 — Traffic shaping support not present in kernel and system libraries
- LIBI-103 — Cannot configure traffic shaping for a network socket
- LIBI-141 — Function dupip() failed to allocate memory
- LIBI-220 — Setting of socket option failed
- LIBI-221 — File descriptor flag operation failed
- LIBI-230 — Attempt to connect timed out
- LIBI-752 — Internal routines cannot resolve domain name
- LIBP-031 — System call of sigaction() failed
- LIBP-120 — System call to daemon() failed
- LIBP-130 — Parent process cannot resend signal to children
- LIBP-730 — Kernun signal handler caught signal
- LIBP-931 — Kernun signal handler has been registered
- LIBT-001 — Syscall gettimeofday() failed
- LIBT-120 — System clock disruption
- LIBT-150 — Sleeping for a time interval terminated with error
- LIBT-959 — A system call was interrupted by a signal
- LIBU-020 — Wrong formatting directive
- LIBU-021 — Printing bad address argument
- LIBU-022 — Printing bad regexp argument
- LIBU-023 — Printing bad IP argument
- LIBU-140 — Error during re-creating file
- LIBU-141 — Cannot properly set attributes of file created
- LIBU-142 — Required file/directory does not exist
- LIBU-143 — Filename already used
- LIBU-144 — Filename already used
- LIBU-145 — Input file opening failed
- LIBU-146 — File cannot be renamed
- LIBU-150 — System call failed
- LIBU-155 — System control variable access failed
- LIBU-156 — System control variable has invalid type
- LIBU-320 — Printing too long string
- LIBU-330 — Filename too long
- LIBU-461 — Per-Address Statistic Table search failure
- LIBU-510 — Regular expression library fails to compile given regexp
- LIBU-530 — Filename contains invalid characters
- LIBU-533 — Filename longer than OS limitations
- LIBU-534 — Library function cannot assemble file name
- LICC-100 — The Kernun license file cannot be found or read
- LICC-101 — The license fail verification failed
- LICC-102 — Cannot check hardware serial number
- LICC-103 — Cannot check hrdware serial number
- LICC-500 — A component is not available and cannot be configured
- LICC-501 — A component is not available and cannot be configured
- LICC-502 — Each SYSTEM section should contain PRODUCT specification
- LICC-700 — Information about a license
- LICC-701 — Reports date when new functionality will not be licensed
- LICC-800 — The license file has bad content
- LICC-801 — The license file does not permit the named component to run
- LICC-802 — The license is no longer valid
- LICC-803 — Cannot check hardware serial number
- LICC-804 — License was issued for another computer
- LICC-805 — License was issued for another software version
- LIST-001 — There are bad links in a linked list data structure
- LSQL-101 — Opening the SQLite file with honeypot blacklist database failed
- LSQL-103 — Removing of old format Honeypot DB file failed
- LSQL-109 — SQLite database cannot be closed
- LSQL-110 — SQL command compilation failed
- LSQL-111 — SQL command execution failed
- LSQL-119 — SQL command execution failed
- LSQL-701 — Cannot set version to honeypot blacklist database
- LSQL-702 — Adaptive Firewall blacklist database has incorrect version
- LSQL-703 — Removing of old format Honeypot DB file succeeded
- LSTN-150 — Listen-on data structure array cannot be allocated
- LSTN-250 — Proxy listening socket creation failed
- LSTN-251 — Socket option failed to be set on the socket
- LSTN-550 — Application cannot resolve address it should be listening on
- LSTN-551 — The given IP address is not configured on any interface
- LSTN-552 — No server address to listen on
- LSTN-553 — Application cannot find address it should be listening on
- LSTN-554 — Failed to prepare listening address
- LSTN-555 — Failed to prepare listening address
- LSTN-559 — No socket for requested traffic defined in listen-on section
- LSTN-950 — Listening socket has been prepared
- LSTN-953 — Listen-on address protocol family was deduced
- LSTN-954 — Listen-on address protocol family was deduced
- MAVC-120 — Antivirus module cannot initialize file for communication with engine
- MAVC-121 — Antivirus module cannot initialize file for communication with engine
- MAVC-123 — Antivirus module cannot read data
- MAVC-130 — Communication with antivirus failed
- MAVC-180 — Antivirus module cannot read data
- MAVC-181 — Communication with antivirus failed
- MAVC-510 — Antivirus list is empty
- MAVC-600 — Antivirus check has found some viruses
- MAVC-700 — Final antivirus check result report
- MAVC-730 — Zero-length file check bypassed
- MAVC-731 — Data are not checked by antivirus due to too big size
- MAVP-209 — Antivirus communication problem
- MAVP-310 — Request for an antivirus does not fit into a buffer
- MAVP-550 — Configured URI for ICAP server antivirus check is invalid
- MAVP-600 — Antivirus engine has found some virus
- MAVP-652 — ICAP antivirus server returns non-virus violation
- MAVP-701 — Unknown status message returned by antivirus engine
- MAVP-707 — Error status message returned by antivirus engine
- MAVP-708 — Proxy does not understand responses from antivirus engine
- MAVP-709 — EOF received when waiting for data from antivirus
- MAVP-731 — ClamAV antivirus response invalid
- MAVP-740 — Antivirus engine does not check document
- MAVP-751 — ICAP server responded by unclear response
- MAVP-758 — ICAP server responded by unclear response
- MAVP-759 — ICAP server responded by unclear response
- MCHU-702 — Found error in chunked body from the client or server
- MCHU-703 — Found error in chunked body from the client or server
- MCHU-704 — Found error in chunked body from the client or server
- MCHU-705 — Found error in chunked body from the client or server
- MCHU-709 — Preview block too large
- MEMM-000 — Memory manager detected a cycle in its internal data structures
- MEMM-001 — Re-initialization of memory management is not allowed
- MEMM-002 — Reparenting of root resource pool is not allowed
- MEMM-003 — Invalid value in memory allocation limits
- MEMM-004 — The structure of resource pools must always be a tree
- MEMM-005 — Repeated deletion of a cleanup function attempted
- MEMM-010 — Root resource pool can never be destroyed
- MEMM-011 — Specification of a string to be copied is invalid
- MEMM-100 — An allocation error occurred
- MEMM-101 — Cannot allocate memory, process will terminate
- MEMM-102 — Cannot allocate memory
- MEMM-103 — Cannot allocate memory, process will terminate
- MEMM-104 — Cannot allocate memory
- MEMM-105 — Maximum size of a pool reached, cannot allocate more memory
- MEMM-106 — Cannot allocate too large memory block
- MEMM-107 — Maximum number of allocated blocks in a pool reached
- MEMM-108 — Maximum number of sub-pools of a resource pool reached
- MEMM-109 — Cannot allocate memory for a pool structure
- MEMM-110 — Cannot register a function to be called at process exit
- MEMM-111 — Cannot register a function to be called at process exit
- MEMM-112 — Cannot register a cleanup function in a pool, process will terminate
- MEMM-113 — Cannot register a cleanup function in a pool
- MEMM-114 — Maximum number of registered cleanup handlers reached
- MEMM-115 — Cannot allocate memory for a pool structure, process will terminate
- MEMM-116 — Cannot create a new resource pool, process will terminate
- MEMM-117 — Cannot create a new resource pool
- MEMM-120 — Cannot allocate memory on the stack
- MEMM-121 — Cannot allocate memory on the stack, process will terminate
- MEMM-122 — Cannot register a pair of related cleanup functions in pools
- MEMM-125 — A resource pool cannot get assigned name
- MENC-751 — Invalid MIME header encoding encountered
- MENC-752 — Invalid MIME header encoding encountered
- MENC-753 — Invalid MIME header encoding encountered
- MENC-791 — Incorrect BASE64 encoding encoutered
- MGZI-100 — Gzip (de)compression cannot be initialized
- MGZI-101 — Gzip (de)compression failed
- MGZI-102 — An error occurred in the zlib data compression library
- MGZI-103 — An unexpected end of file occurred while reading compressed data
- MIME-101 — Proxy cannot use the library for guessing MIME types
- MIME-103 — Proxy cannot use the library for guessing MIME types
- MIME-104 — It is not known if compiled database is up to date
- MIME-105 — The magic database cannot be compiled
- MIME-106 — The magic database cannot be compiled
- MIME-150 — The proxy is unable to open the file with definitions of MIME types
- MIME-151 — Data structure for suffix->MIME type mapping cannot be initialized
- MIME-152 — The proxy is unable to read the file with definitions of MIME types
- MIME-153 — The proxy is unable to close the file with definitions of MIME types
- MIME-154 — An error occurred when storing a value to DB database
- MIME-160 — Error when looking MIME type in database
- MIME-501 — Configuration specifies more than 3 doctype identification methods
- MIME-502 — Magic database cannot be compiled
- MIME-550 — There is very long line in the file defining MIME types
- MIME-551 — A file extension occurs twice in the file defining MIME types
- MIME-700 — The magic database will be recompiled by the proxy
- MIME-701 — The magic database will not be recompiled by the proxy
- MIMX-503 — Configuration specifies incorrect doctype identification method
- MMAT-100 — The proxy cannot save values from a HTML form
- MMAT-101 — The proxy cannot close a database with HTML form values
- MMAT-102 — The proxy cannot open a database used for replacing HTML form values
- MMAT-103 — The proxy cannot open a database of values searched for in HTML forms
- MMAT-800 — The proxy denied further communication because of forbidden data
- MMAT-801 — The proxy cannot store values from a HTML form for later searching
- MMAT-802 — The proxy cannot look up received HTML form data in a database
- MMAT-803 — Forbidden data found in a HTML form
- MMAT-804 — The proxy cannot look up received HTML form data in a database
- MMAT-805 — The proxy cannot look up received HTML form data in a database
- MMAT-806 — The proxy denied further communication because of missing required data
- MMCC-105 — ALTQ queue assigment has failed
- MMCC-131 — Connection to server failed
- MMCC-181 — H.245 control connection accept failed
- MMCC-231 — Target server cannot be connected within timeout period
- MMCC-232 — Target server connection failed
- MMCC-281 — Cannot create listening socket for H.245 session
- MMCC-530 — Next-hop server/proxy name cannot be resolved to IP address
- MMCC-533 — Address being to be forced as source toward the server cannot be resolved
- MMCC-650 — Data connection offer with wrong address
- MMCC-700 — H.225/H.245 packet format error
- MMCC-710 — H.323 destination missing
- MMCC-711 — H.323 destination unknown
- MMCC-720 — Q.931 packet format error
- MMCC-721 — Unimplemented feature in H.323 protocol
- MMCC-730 — Q.931 address unexpected
- MMCC-731 — Unknown Q.931 message
- MMCC-741 — Unimplemented feature in H.323 protocol
- MMCC-742 — Unimplemented feature in H.323 protocol
- MMCC-750 — Data connection offer with changed address
- MMCC-781 — Peer cancelled H.245 connection before accepting
- MMCC-808 — Session initialized, proxy is ready to mediate communication
- MMCC-881 — H.245 session announced and ready
- MMCD-105 — ALTQ queue assigment has failed
- MMCD-110 — H.323 chnannel cannot be created
- MMCD-219 — Peer cancelled channel connection before accepting
- MMCD-600 — Maximal number of H.323 data channel reached
- MMCD-610 — Data connection arrived from bad peer
- MMCD-720 — H.323 data channel I/O failed
- MMCD-721 — H.323 data channel I/O failed
- MMCD-810 — H.323 data channel announced and ready
- MMCG-121 — Udp-proxy was not able to find an ACL appropriate to session
- MMCG-590 — ANY-address used as listen-on for gk-proxy
- MMCG-709 — Final proxy termination message
- MMCG-810 — A datagram from a client has arrived, a session has started
- MMCG-811 — Session initialized, proxy is ready to mediate communication
- MMCG-812 — Session finished
- MMCG-821 — ACL decision has been made, operation either accepted or rejected
- MMCG-888 — Unified GK proxy statistics message
- MMCP-090 — TCP server returned with error
- MMCP-099 — Final startup failure message
- MMCP-100 — Proxy main loop select call failed
- MMCP-104 — Original connection destination getting failed
- MMCP-105 — ALTQ queue assigment has failed
- MMCP-110 — Searching of ACL failed
- MMCP-200 — Proxy main loop timeout reached
- MMCP-239 — TPKT socket closed by peer
- MMCP-500 — ACL misconfigured
- MMCP-700 — Misformed TPKT packet received
- MMCP-711 — Cannot determine target due to missing admission
- MMCP-801 — Client connection arrives to proxy
- MMCP-808 — Session has started, client connection has arrived
- MMCP-809 — Session finished
- MMCP-810 — ACL decision has been made, operation either accepted or rejected
- MMCP-888 — Unified H.232 proxy statistics message
- MMCR-700 — Nonrecoverable parser error reading RAS packet
- MMCR-701 — Unknown RAS packet received
- MMCR-710 — RRQ RAS packet does not contain crucial attributes
- MMCR-720 — URQ RAS packet does not contain crucial attributes
- MMCR-730 — Unknown client registers known H.323/URL identification
- MMCR-800 — RAS packet parsing summary
- MMCY-100 — YP map file cannot be opened
- MMCY-110 — YP map file has incorrect content
- MMCY-111 — RAS YP map file corrupted
- MMCY-113 — RAS YP map file corrupted
- MMCY-120 — YP map file cannot be extended
- MMCY-121 — YP map file seek failed
- MMCY-130 — Memory (re)mapping of YP file failed
- MMCY-510 — RAS YP map file outdated
- MNIO-001 — Invalid network communication mode
- MNIO-003 — Unexpected data found in data buffers during certain operations
- MNIO-021 — Invalid network communication mode
- MNIO-100 — Proxy cannot check for unexpected connection close
- MNIO-101 — Proxy cannot check for unexpected connection close
- MNIO-102 — Proxy cannot check for unexpected connection close
- MNIO-103 — Proxy cannot check for unexpected connection close
- MNIO-150 — Cannot connect to server due to resolution error
- MNIO-151 — Cannot connect to server due to bad socket name
- MNIO-160 — Connection to a remote server timed out
- MNIO-170 — Connection to a remote server failed
- MNIO-171 — Address of a local network socket cannot be obtained
- MNIO-172 — Address of a remote network socket cannot be obtained
- MNIO-200 — Data from client contains bare line-feed character
- MNIO-201 — Information about source address of the connection to the server
- MNIO-202 — Proxy cannot configure source address according to the configuration
- MNIO-301 — The proxy has received a line which does not fit into its buffers
- MNIO-302 — The proxy has received a line which does not fit into its buffers
- MNIO-303 — Timeout while waiting for connection close
- MNIO-500 — The address specified in the SOURCE-ADDRESS cannot be used
- MNIO-600 — Peer has sent a certificate which does not satisfy proxy's requirements
- MNIO-710 — Network connection has been successfully established
- MNIO-800 — Some error occurred during receiving data from a network socket
- MNIO-802 — Some error occurred during sending data to a network socket
- MNIO-803 — Connection to a remote server failed
- MNIO-840 — Attempt to shut down one or both directions of a connection failed
- MNIO-850 — There is no more addresses the proxy could try to connect to
- MNIO-851 — A network socket cannot be created
- MNIO-852 — An error occurred in handling the SSL/TLS protocol
- MNIO-853 — A system call failed during a SSL/TLS operation
- MNIO-870 — The proxy cannot shutdown a SSL/TLS connection properly
- MNIO-871 — A TCP connection has been closed without a proper SSL/TLS shutdown
- MNIO-872 — No memory rbio to swap with socket rbio
- MODM-003 — System call setitimer() unexpectedly failed
- MODM-004 — System call getitimer() unexpectedly failed
- MODM-005 — An unregistered file descriptor has been selected for I/O
- MODM-007 — A deadlock detected in the proxy
- MODM-008 — Creating a temporary resource pool outside a module's run() function
- MODM-009 — Cannot write data to nonexistent output buffer
- MODM-010 — Debugging output of the module manager in case of an internal error
- MODM-011 — Non-existent group number assigned to a new module
- MODM-012 — Non-existent group number assigned to a new module
- MODM-040 — Inconsistent file descriptor and netio structure
- MODM-100 — A program cannot be executed
- MODM-101 — A process for a program execution cannot be created
- MODM-102 — A proxy cannot communicate with an executed program
- MODM-156 — Proxy cannot determine transparency of a client connection
- MODM-801 — A serious error occurred, the client will be disconnected
- MODM-802 — A serious error occurred, the client will be disconnected
- MODM-803 — An error occurred, an error message will be sent to the client
- MODM-804 — A timeout expired which killed the current client's request
- MODM-805 — A process exceeded a maximum allowed runtime
- MODM-806 — A process exceeded a maximum allowed runtime
- MODM-821 — Initialization of a new request failed
- MODM-832 — Initialization of a new proxy module failed
- MODM-835 — A per-client module cannot be attached to a request
- MODM-838 — A per-client module cannot be detached from a request
- MONI-100 — Proxy cannot initialize communication with monitoring utility
- MONI-101 — Proxy cannot initialize communication with monitoring utility
- MONI-102 — Proxy cannot initialize communication with monitoring utility
- MONI-103 — Proxy cannot terminate monitoring properly
- MONI-500 — Proxy cannot initialize communication with monitoring utility
- MPWF-001 — Unknown content of ICAP response Encapsulated header
- MPWF-200 — Proxy cannot communicate with the web filter
- MPWF-201 — Proxy cannot communicate with the web filter
- MPWF-202 — A web filtration request does not fit to a buffer
- MPWF-203 — The proxy is unable to return the web filter response
- MPWF-700 — The web filter has rejected the request
- MPWF-800 — The web filter terminated its response unexpectedly
- MPWF-801 — A web filter response does not fit to a buffer
- MPWF-802 — A web filter response cannot be processed
- MPWF-810 — Request failed due to inoperative web filter
- MPWF-811 — Request continues despite web filter failure
- MRDF-000 — Trying to subtitute a nonexisting string in a file
- MRDF-003 — Unexpected data found in data buffers during certain operations
- MRDF-100 — A file cannot be opened for reading
- MRDF-101 — A file size cannot be obtained
- MRDF-102 — A file cannot be mapped to memory
- MRDF-103 — A file cannot be read to memory
- MRDF-300 — Line longer than internal buffer size
- MRDF-800 — Trying to subtitute a nonexisting string in a file
- MRDF-801 — Files in a directory cannot be read for later use
- MRDF-802 — A file cannot be read for later use
- MSPA-105 — ALTQ queue assigment has failed
- MSPA-310 — Antispam report truncated
- MSPA-709 — Antispam failed, spam score invalid
- MSPA-710 — Spam checker has returned unknown response
- MSPA-800 — Information about mail size and antispam score
- MSPA-810 — Report of partial spam scores by categories
- MWRF-100 — The proxy cannot open a local file
- NATT-002 — It is not possible to issue bind() syscall to desired address
- NETL-002 — Function netopen() attempts to change netio socket type
- NETL-003 — Internal buffer pointers are inconsistent
- NETL-010 — Improper call to netctl() function
- NETL-011 — Scratch of too many bytes requested
- NETL-012 — Function ungetc() called to empty buffer
- NETL-032 — Improper call of netgetcmd() function
- NETL-033 — Network Virtual Terminal processing error
- NETL-060 — Inconsistent options given to write operation
- NETL-087 — Attempt to reconnect UDP socket
- NETL-088 — Attempt to send data to not connected UDP socket
- NETL-089 — Send to invalid address requested
- NETL-101 — Shutdown operation with socket failed
- NETL-202 — Setting socket flags by fcntl() or setsockopt() failed
- NETL-203 — Preparing socket for TCP reset by setsockopt() failed
- NETL-204 — Cannot obtain the value of the IP packet TOS field
- NETL-205 — Cannot set the value of the IP packet TOS field
- NETL-210 — General message of NAT operation failure
- NETL-211 — Binding of socket to printed address failed
- NETL-212 — Syscall getsockname() failed
- NETL-220 — The proxy sends TCP reset instead of normal TCP connection close
- NETL-231 — Socket read failed
- NETL-262 — Writing data to socket failed
- NETL-267 — Non-blocking write ended by some data unsent
- NETL-283 — UDP data not sent
- NETL-291 — Timeout reached during netio operation
- NETL-331 — Too large UDP datagram received
- NETL-390 — Netio function failed due to buffer shortage
- NETL-391 — Netio function failed due to buffer shortage
- NETS-001 — Select handler size is negative
- NETS-010 — Adding too high socket number
- NETS-011 — Unregistered socket used to select
- NETS-012 — Unopened socket used to select
- NETS-039 — Network I/O select routine failed
- NETS-101 — Too many file descriptors are requested
- NETS-228 — Timeout reached during select() syscall
- NETS-700 — Select handler manipulation function already called
- NTIF-001 — Network interface has no link address
- NTIF-004 — Network interface name not found
- NTIF-007 — Socket address information for netmask is not valid
- NTIF-101 — Kernel routing information is not available
- NTIF-102 — No memory available for kernel routing information
- NTIF-103 — No memory available for network interface information
- NTIF-901 — Function has started its operation
- NTIF-902 — Function has finished its operation
- NTLM-200 — The proxy cannot communicate with the NTLM helper program
- NTLM-201 — The proxy cannot communicate with the NTLM helper program
- NTLM-500 — NTLM-related communication with an AD controller should be limited
- NTLM-501 — NTLM-related communication should be limited by INTERFACE or NETWORK
- NTLM-800 — Client provided unexpected authentication information
- NTLM-801 — The proxy cannot communicate with the NTLM helper program
- NTLM-802 — An error has occured in the NTLM authentication module
- NTLM-803 — The NTLM helper program have not replied in time
- NTLM-804 — The NTLM helper program have returned an unexpected response
- NTLM-805 — The NTLM helper program have returned an unexpected response
- NTLM-806 — The NTLM helper program have returned an unexpected response
- NTLM-807 — NTLM authentication failed
- NTLM-808 — NTLM authentication cannot obtain group information from LDAP
- NTLM-809 — The NTLM helper program have returned a too long response
- NTPC-099 — Final startup failure message
- NTPC-711 — Host name in NTP configuration failed to resolve
- NTPC-718 — No NTP server IP address available
- NTPC-719 — Final NTP regeneration success message
- OOBA-001 — No OOBA handle exists for a given set of configuration parameters
- OOBA-100 — The OOB authentication server cannot communicate with proxies
- OOBA-101 — The OOB authentication server cannot communicate with proxies
- OOBA-102 — The OOB authentication server cannot communicate with proxies
- OOBA-103 — The OOB authentication server cannot communicate with proxies
- OOBA-104 — The OOB authentication server cannot communicate with proxies
- OOBA-105 — Proxy cannot terminate using a session table file properly
- OOBA-106 — Proxy cannot terminate using a session table file properly
- OOBA-107 — The proxy cannot communicate with the authentication server
- OOBA-108 — Contents of the OOB authentication session table is not valid
- OOBA-109 — The OOB authentication server cannot release its session table
- OOBA-590 — OOB authentication server name misconfigured
- OOBA-800 — Limit for number of OOB authenticated users has been reached
- OOBA-801 — A user name does not fit into the OOBA session table entry
- OOBA-802 — List of groups does not fit into the OOBA session table entry
- OOBA-803 — List of groups does not fit into the OOBA session table entry
- OSSL-000 — The proxy tried to initialize OpenSSL twice
- OSSL-100 — An SSL context cannot be created
- OSSL-101 — Cipher list for an SSL context cannot be set
- OSSL-102 — The proxy cannot initialize OpenSSL error logging
- OSSL-103 — Contents of the SSL error queue
- OSSL-104 — The proxy cannot load a certificate for SSL/TLS
- OSSL-105 — The proxy cannot load its private key
- OSSL-106 — The proxy cannot load a certificate revocation list
- OSSL-107 — The proxy cannot load a certificate revocation list
- OSSL-108 — The proxy cannot load a certificate revocation list
- OSSL-109 — Parameters for ephemeral DH key exchange cannot be created
- OSSL-110 — Parameters for ephemeral DH key exchange cannot be created
- OSSL-111 — A structure representing a new SSL/TLS connection cannot be created
- OSSL-112 — The OpenSSL library cannot attach to a TCP connection
- OSSL-113 — A SSL/TLS operation failed due to an OS-level I/O error
- OSSL-114 — An SSL/TLS operation due to an error at the OpenSSL library level
- OSSL-115 — The underlaying TCP connection has been unexpectedly closed
- OSSL-116 — A system call has failed during an SSL/TLS operation
- OSSL-117 — The proxy cannot load certificates of trusted certification authorities
- OSSL-118 — The proxy will not use a certificate revocation list
- OSSL-119 — Assigning security attributes to new SSL connection failed
- OSSL-120 — An SSL/TLS operation reported syscall failure but errno is empty
- OSSL-121 — The session id context cannot be set for an SSL context
- OSSL-122 — Security attributes for SSL connection cannot be reset
- OSSL-123 — Parent CA certificate adding failed
- OSSL-124 — The OpenSSL library cannot create a memory buffer containing ClientHello request
- OSSL-125 — The OpenSSL library cannot create a memory buffer containing ClientHello request
- OSSL-130 — The SSL session cache cannot be initialized
- OSSL-131 — The SSL session cache cannot be initialized
- OSSL-134 — The SSL session cache cannot be initialized
- OSSL-156 — The process cannot access the SSL/TLS session cache
- OSSL-157 — The SSL/TLS session cache cannot be unlocked
- OSSL-158 — An SSL/TLS session obtained from the session cache is unusable
- OSSL-159 — An SSL/TLS session obtained from the session cache is unusable
- OSSL-160 — The process cannot access the SSL/TLS session cache
- OSSL-161 — The process cannot access a cached SSL/TLS session
- OSSL-162 — The process cannot access the SSL/TLS session cache
- OSSL-163 — The SSL/TLS session cache is missing parameters
- OSSL-170 — Faked server private key load failed
- OSSL-171 — Faking CA private key load failed
- OSSL-172 — Faking CA certificate load failed
- OSSL-173 — Faked certificate cannot be stored
- OSSL-178 — Cached certificate for HTTPS inspection is unreadable
- OSSL-179 — Faked certificate cannot be stored
- OSSL-180 — Configuration file for FAKE-CERT section not found
- OSSL-181 — Faked certificates configuration not accessible
- OSSL-182 — Faked certificates cache hash tag file is not accessible
- OSSL-183 — Faked certificates cache cannot be cleaned
- OSSL-190 — PEM file with certificates cannot be open
- OSSL-191 — PEM file with certificates cannot be read
- OSSL-192 — The fingerprint computatin has failed for the certificate
- OSSL-193 — The fingerprint computation has failed for the certificate
- OSSL-510 — Server SSL parameters do not requires certificate verification
- OSSL-511 — Configuration allows deprecated SSL protocols
- OSSL-512 — Distrusted certificates list has been loaded
- OSSL-513 — The peer certificate is listed in the distrusted list
- OSSL-514 — The certificate chain of the peer is listed in the distrusted list
- OSSL-515 — The distrusted certificate list failed to be loaded from the PEM file
- OSSL-516 — DISTRUSTED-CERTS should be specified when AUTH-CERT is KERNUN-DIST
- OSSL-600 — The peer has not presented a certificate during SSL/TLS handshake
- OSSL-601 — Peer's certificate could not be verified
- OSSL-602 — Information about a valid peer certificate
- OSSL-607 — Openssl syscall for creating the EC_KEY object using a named curve failed
- OSSL-737 — SSL_accept was expected to fail but did not
- OSSL-738 — SSL_accept failed with different error than expected
- OSSL-739 — SSL_accept failed with different error than expected
- OSSL-740 — SSL_accept failed with more errors than expected
- OSSL-775 — Some X.509 extension from server certificate is unknown
- OSSL-776 — Some X.509 extension from server certificate is unknown
- OSSL-780 — Health report of FAKE-CERT cache directory
- OVPN-001 — Openvpn failed to start the client connect script
- OVPN-098 — Final startup failure message
- OVPN-099 — Final startup failure message
- OVPN-101 — Failed to exec the openvpn daemon
- OVPN-102 — Error during accepting a connection on a socket
- OVPN-103 — Failed to open the socket for reading
- OVPN-104 — Failed to read line from the management socket
- OVPN-105 — Connection from client has been closed before accepted
- OVPN-107 — Openvpn configuration provider failed to create the server socket
- OVPN-108 — Failed to bind the unix-domain socket
- OVPN-109 — Failed to listen on the server socket
- OVPN-111 — Failed to create the client socket
- OVPN-112 — Cannot establish a connection to the openvpn management socket
- OVPN-113 — The parent process tried to signal its children and received an error
- OVPN-114 — An error occured during waiting for a child process
- OVPN-115 — Failed to unlink the socket file
- OVPN-116 — Openvpn failed to execute the client-connect script
- OVPN-118 — Openvpn daemon failed to create the socket-root directory
- OVPN-119 — Openvpn daemon was unable to unlink invalid sessions-db file
- OVPN-301 — Openvpn configuration provider failed to read the row
- OVPN-302 — Openvpn policy enforcement failed to read the row
- OVPN-405 — Client is connected without permission, it will be disconnected now
- OVPN-406 — Openvpn policy enforcement client disconnection report
- OVPN-408 — Failed to load the client connect script
- OVPN-410 — Client is disabled now
- OVPN-412 — Openvpn daemon was unable to create the sessions-db file
- OVPN-413 — Unexpected error occured while opening the sessions-db file
- OVPN-501 — Failed to reread the configuration
- OVPN-502 — Openvpn section must reference an interface of the correct type
- OVPN-503 — Ifconfig-pool address must respect the interface range
- OVPN-504 — Ifconfig-push address must respect the interface range
- OVPN-505 — Address pushing in OPENVPN must respect the INTERFACE type
- OVPN-506 — OPEVNPN pushing address collision
- OVPN-507 — Interface not specified for openvpn
- OVPN-508 — Invalid interface type referenced in the openvpn section
- OVPN-510 — Ifconfig-pool collides with the ifconfig-push address
- OVPN-511 — OPENVPN pushing address must not collid with the INTERFACE address
- OVPN-512 — Ifconfig-ipv6-pool address must respect the interface IPv6 network range
- OVPN-513 — Ifconfig-ipv6-push address must respect the interface IPv6 range
- OVPN-514 — Items PROTO, LOCAL and REMOTE must respect each other's address family
- OVPN-515 — Ifconfig-ipv6-pool collides with the ifconfig-ipv6-push address
- OVPN-516 — Openvpn daemon failed to execute the configured client-connect script
- OVPN-701 — Unknown command to the openvpn config provider
- OVPN-702 — Failed to serve the client
- OVPN-703 — Failed to connect to the openvpn manage socket
- OVPN-705 — Failed to disconnect the client
- OVPN-706 — Failed to list the connected clients
- OVPN-707 — Openvpn management command failed
- OVPN-709 — Reading the contents of file was unsuccessful
- OVPN-712 — Failed to obtain the status from the openvpn
- OVPN-713 — Openvpn daemon failed to connect to the configured client-connect socket
- OVPN-715 — Openvpn sessions database was created succesfully
- OVPN-801 — Openvpn config provider failed to serve the client
- OVPN-802 — Openvpn parent process failed to create a child process
- OVPN-806 — Too many openvpn terminated child processes
- OVPN-807 — Openvpn parent process detected the reload request
- OVPN-824 — Openvpn daemon was unable to initialize the SQLite library
- OVPN-825 — A database error occured while accessing sessions-db
- OVPN-826 — Openvpn daemon failed to insert new record into the sessions-db
- OVPN-827 — Openvpn daemon failed to update a record in the sessions-db
- OVPN-828 — Openvpn daemon tried to update a record in the sessions-db but the query had no effect
- OVPN-829 — Unexpected SQL error occured while searching in sessions-db
- OVPN-830 — Openvpn daemon failed to reset prepared SQL statements
- OVPN-831 — Openvpn daemon failed to finalize prepared SQL statements
- OVPN-832 — Openvpn daemon failed to close SQlite database connection
- OVPN-833 — Openvpn daemon was unable to update sessions-db due to failed management socket connection
- OVPN-834 — Openvpn daemon ignored invalid record in current connections table
- OVPN-835 — Openvpn daemon encountered an old version of the sessions-db database
- OVPN-836 — Openvpn daemon ignored invalid record in current connections table
- OVPN-838 — Openvpn daemon encountered an unexpected error
- OVPN-839 — Openvpn monitoring daemon detected an ongoing VPN connection of unknown origin
- PFCD-109 — Syscall select() in main loop failed
- PFCD-110 — Call of pfctl command failed
- PFCD-120 — Reloading of some PF tables failed
- PFCD-700 — Notification about the mode of operation of the pf-control
- PFCD-701 — PF control daemon has been initialized and is ready to work
- PFCD-708 — PF control daemon has finished
- PFCD-709 — Final daemon termination message
- PFCD-710 — Cannot determine current PF status
- PFCD-720 — PF control daemon failed to load new PF tables
- PFCD-728 — PF table change report
- PFCD-729 — Packet filter table reload error
- PFCD-820 — PF tables refresh report
- PFLG-120 — Input printcap device initialisation failed
- PFLG-121 — Input printcap device initialisation failed
- PFLG-123 — Input printcap device initialisation failed
- PFLG-129 — Input printcap device initialisation failed
- PFLG-320 — PF logger data misunderstanding
- PFLG-715 — PF control daemon timeout misconfiguration
- PFLG-719 — Packet filter information line misunderstood
- PFLG-751 — Incorrect data captured from the PF
- PFLG-765 — PF controling daemon failed to read pfsync message
- PFLG-768 — Inconsistent time data from PF
- PFLG-769 — Inconsistent time data from PF
- PFLG-810 — PF rule map record report
- PFLG-850 — PF rule event log message
- PFLG-860 — PF state end log message
- PFLG-870 — Statistic message of non-blocking stateless PF rules
- PFLG-888 — Unified packet filter statistics message
- PFTB-351 — PF table rebuild failed
- PIKE-100 — PIKE monitoring component cannot recognize cluster status
- PIKE-109 — Syscall select() in main pikemon loop failed
- PIKE-110 — Pikemon state change command failed
- PIKE-118 — Cannot prioritize pikemon daemon
- PIKE-120 — Pikemon status file corrupted or inaccessible
- PIKE-121 — Pikemon restart failed
- PIKE-501 — Single heart-beat listening socket must be specified
- PIKE-510 — All virtual clusters must have unique ID
- PIKE-511 — Interface devices used for PIKE are incorrect
- PIKE-512 — Interface devices used for PIKE are incorrect
- PIKE-513 — Interface devices used for PIKE are incorrect
- PIKE-518 — PIKE timeouts inconsistency
- PIKE-519 — PIKE virtual cluster configuration is not complete
- PIKE-580 — PIKEMON command syntax error
- PIKE-581 — Invalid VCID in PIKEMON command
- PIKE-652 — HMAC verifiaction failed
- PIKE-700 — Notification about the mode of operation of pikemon
- PIKE-707 — The pikemon has finished
- PIKE-709 — Final daemon termination message
- PIKE-710 — Daemon runtime monitoring support cannot be initialized
- PIKE-720 — Pikemon status file parsing result
- PIKE-730 — PIKE monitor received packet of unsupported protocol version
- PIKE-731 — PIKE peer uses incompatible set of virtual clusters
- PIKE-740 — PIKE protocol state change message
- PIKE-741 — Network recovery triggered by partner status change has started
- PIKE-750 — PIKE monitor received packet of other than current protocol version
- PIKE-751 — PIKE peer uses incompatible set of virtual clusters
- PIKE-763 — SWAP message of PIKE protocol received
- PIKE-780 — PIKEMON command execution message
- PIKE-781 — SWAP command result informational message
- PIKE-820 — Brief cluster health status information
- PIKE-821 — Firewall drops master role for virtual cluster
- PIKE-822 — Firewall takes master role for virtual cluster
- PING-255 — ICMP ECHO sent incompletely
- PING-710 — PIKE ping group state change message
- PING-711 — Monitoring of a group of target host by ping has ended
- PING-755 — ICMP ECHO sending failed
- POP3-100 — The main loop for serving clients (tcpserver) failed
- POP3-101 — ALTQ queue assigment has failed
- POP3-200 — Cannot change source address of a connection to a server
- POP3-201 — The proxy cannot initialize a connection to a server
- POP3-202 — The proxy cannot initialize a connection to a server
- POP3-700 — Session ACL has been processed
- POP3-701 — Command ACL has been processed
- POP3-702 — A client has been disconnected from the proxy
- POP3-704 — A new client has connected to the proxy
- POP3-710 — A command has been denied by ACL
- POP3-711 — A capability has been denied by ACL
- POP3-712 — An unimplemented capability received from the server
- POP3-800 — Proxy initialization failed
- POP3-801 — An error occurred during searching SESSION-ACLs
- POP3-802 — The client has been denied by SESSION-ACL
- POP3-803 — The proxy is unable to verify user authentication
- POP3-804 — The proxy does not know a server address to connect
- POP3-805 — Initial processing of a new client connection has failed
- POP3-806 — Proxy cannot start SSL/TLS on the client connection
- POP3-807 — Proxy cannot start POP3 protocol
- POP3-808 — An error occurred during searching COMMAND-ACLs
- POP3-809 — The client has been denied by COMMAND-ACL
- POP3-810 — Limit for session duration has been reached
- POP3-811 — The client is sending too much data
- POP3-812 — The server is sending too much data
- POP3-813 — Proxy cannot start SSL/TLS on the server connection
- POP3-814 — The session is being idle for too long
- POP3-815 — Proxy cannot create module for sending a processed mail to the client
- POP3-820 — The client has unexpectedly disconnected from the proxy
- POP3-821 — The server has unexpectedly disconnected from the proxy
- POP3-823 — A client command line is too long
- POP3-824 — A capability line is longer than the configured limit
- POP3-825 — A server response line is too long
- POP3-826 — An authentication challenge line is too long
- POP3-827 — An authentication answer line is too long
- POP3-829 — A command line is longer than the configured limit
- POP3-830 — A line with capability is too long
- POP3-831 — The command from the client is bad
- POP3-832 — A response line is longer than the configured limit
- POP3-833 — The response from the server is bad
- POP3-835 — A mail line is longer than the configured limit
- POP3-836 — The command from the client is bad
- POP3-837 — A mail being retrieved from the server is too big
- POP3-838 — A mail line is longer than the configured limit
- POP3-840 — A mail message contains too long line
- POP3-841 — The proxy does not understand a server response
- POP3-850 — Proxy cannot store a mail for processing
- POP3-851 — A mail cannot be processed
- POP3-852 — A mail has been rejected by DOC-ACL
- POP3-853 — A mail has been rejected by MAIL-ACL
- POP3-860 — Information about selected MAIL-ACL
- POP3-861 — Proxy cannot create module for processing a mail
- POP3-888 — Unified POP3 proxy statistics message
- PRXY-132 — Switching list of groups from root to another user failed
- PRXY-133 — Switching real and effective GID from root to another user failed
- PRXY-134 — Switching real and effective UID from root to another user failed
- PRXY-135 — Setting login class for the proxy user failed
- PRXY-139 — Proxy cannot change its root directory
- PRXY-500 — Application configuration missing
- PRXY-501 — Application configuration is not unique
- PRXY-521 — No USE-RESOLVER used
- PRXY-523 — Resolver configuration reduced
- PRXY-530 — Invalid run-time user specified
- PRXY-531 — Application cannot change its root directory if not started by root
- PRXY-533 — Application cannot be switched to unknown user
- PRXY-541 — Working directory specification invalid
- PRXY-549 — Application cannot create working directory
- PRXY-734 — The proxy was switched from root to some other user
- PRXY-739 — Proxy changed its root directory
- RCSL-100 — Insufficient permissions to configuration file
- RCSL-110 — Unrecognised rcsdiff output
- RCSL-120 — Creation of revision control file for configuration file failed
- RCSL-139 — Current user name unknown
- RCSL-700 — Some of configuration files does not exist
- RCSL-710 — Text and RCS versions of configuration mismatch
- RCSL-718 — Configuration file locking failed
- RCSL-719 — Configuration file inconsistency warning
- RCSL-720 — Configuration file with chosen name exists
- RCSL-730 — Configuration file successfully locked
- RCSL-738 — Configuration file lock status incorrect
- RCSL-739 — Configuration file lock status incorrect
- RDST-201 — Client has closed connection too early
- RDST-901 — Function realdest() has started its operation
- RDST-902 — Function realdest() has finished its operation
- RGAI-330 — DNS response contains too many RRs
- RGAI-331 — DNS response contains too many texts in RR
- RGAI-730 — DNS answer contains irrelevant data
- RGAI-731 — DNS response contains too long text
- RGAI-735 — DNS response contains incorrect CNAME chain
- RGAI-739 — No records in ANSWER section of DNS response were accepted
- RGHD-330 — DNS response contains too many RRs
- RGHD-730 — DNS answer contains irrelevant data
- RGHD-735 — DNS response contains incorrect CNAME chain
- RGHD-739 — No records in ANSWER section of DNS response were accepted
- RSLC-761 — Nameserver response contains invalid name
- RSLV-180 — Resolver mapping file unaccessible
- RSLV-213 — DNS resolution failed
- RSLV-589 — Resolver pool directory misconfigured
- RSLV-713 — ACR successfully resolved domain name in configuration
- RSLV-741 — Query section of the answer does not match one of request
- RSLV-770 — Hostnames used in configuration was resolved
- RSLV-795 — Proxy reloaded results of ACR name resolution
- SDPB-710 — SDP line misformed
- SDPB-720 — SDP line misformed
- SDPB-721 — SDP version unrecognized
- SDPB-740 — SDP line misformed
- SDPC-120 — Data port assignment failure
- SDPC-219 — Data channel unexpectedly closed
- SDPC-230 — Invalid data channel
- SDPC-310 — Data channel table exhausted
- SDPC-350 — Oversized media data block
- SDPC-800 — SIP data channel closed
- SIPB-710 — SIP method recognition message
- SIPB-719 — SIP line misformed
- SIPB-750 — SIP line misformed
- SIPB-751 — SIP line misformed
- SIPB-760 — SIP line misformed
- SIPB-781 — SIP line misformed
- SIPB-789 — SIP line misformed
- SIPC-130 — Control socket creation failed
- SIPC-180 — Routing table search failed
- SIPC-231 — Control socket acceptation failed
- SIPC-232 — Control connection attempt unsuccessful
- SIPC-240 — Control connection I/O error
- SIPC-242 — Control connection I/O error
- SIPC-249 — Client control connection closed
- SIPC-250 — Control connection I/O error
- SIPC-259 — Control connection unexpectedly closed
- SIPC-310 — Control channel table exhausted
- SIPC-330 — Control channel table exhausted
- SIPC-340 — Control message line too long
- SIPC-341 — Control message unrecognized
- SIPC-588 — Listening socket missing for outgoing direction
- SIPC-830 — Control channel establishing message
- SIPM-310 — SIP message table exhausted
- SIPM-380 — Control message too long
- SIPM-751 — SIP over TCP message header invalid
- SIPM-752 — SIP over UDP message header invalid
- SIPM-753 — Unsupported document body in SIP message
- SIPM-759 — SIP message misformed
- SIPP-119 — Syscall select() in main proxy loop failed
- SIPP-351 — Insufficient socket table size
- SIPP-700 — Notification about the mode of operation of the proxy
- SIPP-701 — The proxy has been initialized and is ready to accept packets
- SIPP-708 — The proxy has unbound the sockets used for listening for clients
- SIPP-709 — Final proxy termination message
- SIPP-710 — Proxy runtime monitoring support cannot be initialized
- SIPP-723 — The proxy has finished
- SIPP-888 — Unified SIP proxy statistics message
- SIPR-310 — Requests table is exhausted
- SIPR-719 — Incomplete request removed
- SIPR-729 — Request was not finished in time
- SIPR-739 — Proxy rejects request
- SIPR-740 — Client registration not accepted
- SIPR-741 — Client registration not accepted
- SIPR-742 — Client registration not accepted
- SIPR-745 — Call transfer requested by user
- SIPR-751 — Misplaced ACK/CANCEL request
- SIPR-759 — Misplaced ACK/CANCEL request
- SIPR-760 — Response message not accepted
- SIPR-761 — Request matching response not found
- SIPR-762 — Misordered response to request received
- SIPR-769 — Cannot match response to request
- SIPR-800 — Response to request arrived and forwarded
- SIPS-130 — Routing table search failed
- SIPS-310 — Session table exhausted
- SIPS-311 — Session table exhausted
- SIPS-530 — Listening socket missing for server session transaction
- SIPS-531 — SIP misconfigured due to bad resolution
- SIPS-710 — Received request that cannot establish session
- SIPS-730 — Next-hop for request cannot be determined
- SIPS-760 — Configured IDLE-TIMEOUT expired
- SIPS-800 — Session has started, unmatched request arrived
- SIPS-801 — Session initialized, proxy is ready to mediate communication
- SIPS-809 — Session finished
- SIPS-821 — SESSION-ACL search report
- SIPS-822 — REQUEST-ACL search report
- SIPY-110 — SIP YP map file unaccessible
- SIPY-111 — SIP YP map file corrupted
- SIPY-119 — SIP YP map is corrupted
- SIPY-120 — SIP YP map file cannot be extended
- SIPY-121 — SIP YP map file seek failed
- SIPY-130 — Memory (re)mapping of SIP YP file failed
- SIPY-510 — SIP YP map format is older than proxy version
- SIPY-750 — SIP YP map record inconsistency
- SLOG-009 — Application has improperly started
- SLOG-011 — Improper combination of arguments to opentnslog() function
- SLOG-020 — Logging function called with unknown severity code
- SLOG-100 — Backup log file cannot be opened
- SLOG-104 — Syslog socket opening failure
- SLOG-110 — Forwarding log to file failed
- SLOG-120 — A process cannot terminate its logging to memory correctly
- SLOG-121 — A file with memory log of a process cannot be deleted
- SLOG-122 — The process cannot perform logging into memory
- SLOG-123 — The process cannot perform logging into memory
- SLOG-124 — Memory logging file cannot be renamed
- SLOG-500 — The process cannot perform logging into memory
- SLOG-501 — The process cannot perform logging into memory
- SLOG-700 — Application initial log message
- SLOG-701 — Process initial log message
- SLOG-702 — Change of program identification in log
- SLOG-703 — PID suffix will be used
- SLOG-704 — Communication to syslog daemon successfully reopened
- SLOG-709 — Application introduction message after log reopening
- SLOG-710 — Log destination changed to file
- SLOG-711 — Log destination changed to standard error
- SLOG-712 — Log destination changed to syslog daemon
- SLOG-713 — Re-introduction log message
- SLOG-714 — A memory log file has been successfully initialized for a process
- SLOG-720 — Logging level changed to a new value
- SMTB-350 — Header too long
- SMTB-750 — Header contains invalid character
- SMTB-751 — Header contains invalid quoted character
- SMTB-752 — Header contains unpaired parenthesis
- SMTB-753 — Header contains incorrect quotting
- SMTB-754 — Duplicite CR found in end-of-line sequence
- SMTB-760 — No semicolon found between header arguments
- SMTB-761 — Unquoted character occurred in header
- SMTB-762 — Illegal character used in structured header
- SMTB-780 — MIME header syntax error
- SMTB-781 — Incomplete value in MIME header
- SMTB-789 — Mail or MIME header RFC violation
- SMTC-541 — Header modification too long
- SMTC-542 — Incorrect character found in header modification configuration
- SMTC-560 — Mailbox address incorrect
- SMTC-561 — Mailbox address incorrect
- SMTC-562 — Mailbox address incorrect
- SMTC-563 — Mailbox address incorrect
- SMTC-564 — Mailbox address incorrect
- SMTC-565 — Mailbox address incorrect
- SMTC-569 — SMTP forwarders misconfiguration
- SMTD-100 — Searching of ACL failed
- SMTD-180 — MIME structure subdocument is not readable
- SMTD-310 — Cannot read mail body line
- SMTD-311 — Too long mail header line found
- SMTD-312 — Too long mail header line handling report
- SMTD-313 — Too long mail header line cannot be wrapped
- SMTD-320 — Message MIME structure is too large
- SMTD-340 — Mail will not be sent as-is, it must be re-assembled from parts
- SMTD-360 — Cannot write mail body line
- SMTD-370 — Mail antispam check skipped due to mail size
- SMTD-530 — Incorrect MIME format in configuration
- SMTD-531 — Incorrect header modification defined in configuration
- SMTD-700 — Possible forwarding loop
- SMTD-720 — Incorrect MIME specification
- SMTD-721 — Incorrect multipart MIME boundary definition
- SMTD-722 — Invalid Content-Transfer-Encoding
- SMTD-726 — Mail text does not contain any boundary line
- SMTD-727 — Boundary regeneration failed
- SMTD-728 — Header and body not separated
- SMTD-729 — MIME structure corrupted
- SMTD-739 — Final message reporting mail/MIME header error
- SMTD-742 — Incorrect character found in mail body
- SMTD-790 — Non US-ASCII mail not correctly declared
- SMTD-803 — DOC-ACL search report
- SMTI-502 — SMTP forwarder contains too many servers
- SMTI-520 — Incorrect black-list configuration
- SMTI-552 — Antivirus configuration inconsistency
- SMTI-553 — QUARANTINE configuration must be specified
- SMTI-554 — SMTP proxy QUARANTINE configuration inconsistent
- SMTI-555 — GREY-LISTING configuration must be specified
- SMTI-556 — SPF in DELIVERY-ACL requires using of WHITE-LISTING in SESSION-ACL
- SMTN-760 — Found ESMTP DSN extension parameter with invalid syntax
- SMTN-761 — Found ESMTP DSN extension parameter with invalid syntax
- SMTP-090 — TCP server returned with error
- SMTP-099 — Final startup failure message
- SMTP-104 — The proxy cannot use SSL/TLS
- SMTP-239 — Control socket closed by peer
- SMTP-738 — I/O operation on socket failed
- SMTP-801 — Session has started, client connection has arrived
- SMTP-809 — Session finished
- SMTP-888 — Unified SMTP proxy statistics message
- SMTR-101 — Searching of ACL failed
- SMTR-105 — ALTQ queue assigment has failed
- SMTR-109 — Session initialization failed
- SMTR-169 — Mail storing failed
- SMTR-180 — Quarantine storing failed
- SMTR-181 — Quarantine storing failed
- SMTR-202 — The proxy cannot establish an SSL/TLS secure channel from the client
- SMTR-300 — The proxy has received line longer than protocol defined maximum
- SMTR-310 — Mail size reached configuration limit
- SMTR-330 — Mail too big
- SMTR-500 — Mail cannot be sent due to unknown forwarder
- SMTR-510 — Cannot force source address in SESSION-ACL
- SMTR-540 — Configuration does not cover fatal error
- SMTR-601 — Unknown client - access denied
- SMTR-602 — Unknown client - access denied
- SMTR-603 — Client found in black list
- SMTR-609 — Client sent too many bad commands
- SMTR-640 — Client sent too many RCPT commands
- SMTR-641 — Client sent too many bad RCPT commands
- SMTR-700 — SMTP command processing report
- SMTR-701 — Unknown command sent by client
- SMTR-702 — Incorrect character in SMTP command
- SMTR-703 — Client has not closed session
- SMTR-709 — Session idle timeout reached
- SMTR-710 — SMTP command syntax error
- SMTR-712 — SMTP command parameter syntax error
- SMTR-719 — SMTP command arguments not valid
- SMTR-730 — MAIL BODY parameter value not valid
- SMTR-740 — Recipient change report
- SMTR-741 — Found unknown ESMTP DSN extension parameter value
- SMTR-742 — Found incorrect ESMTP DSN extension parameter value
- SMTR-749 — SMTP command argument parsing error
- SMTR-750 — No valid recipient remained
- SMTR-760 — The proxy has received line with unencoded leading dot
- SMTR-769 — EOF encountered during mail reception
- SMTR-801 — SESSION-ACL search report
- SMTR-802 — DELIVERY-ACL search report
- SMTR-803 — MAIL-ACL search report
- SMTR-810 — Client ESMTP DSN extension parameters report message
- SMTR-811 — Opening mail report message
- SMTR-819 — Final mail report message
- SMTS-105 — ALTQ queue assigment has failed
- SMTS-202 — The proxy cannot establish an SSL/TLS secure channel to the server
- SMTS-208 — Forwarder closed connection not using the x21 message
- SMTS-209 — Forwarder has sent x21 message
- SMTS-300 — Forwarder sent too long line
- SMTS-500 — Trivial configuration loop danger
- SMTS-600 — Forwarding channel does not satisfy proxy SSL requirements
- SMTS-700 — Forwarder sent unexpected response
- SMTS-708 — Mail forwarding failed
- SMTS-709 — Session idle timeout reached
- SMTS-711 — Forwarder sent incorrect response
- SMTS-720 — Forwarder sent unknown response
- SMTS-729 — Negative response got from forwarder
- SMTS-730 — Forwarder uses incorrect ESMTP option
- SMTS-739 — Forwarder rejects connection from proxy
- SMTS-740 — Recipient accepted/refused by forwarder
- SMTS-741 — Incorrect mail for 7bit forwarders
- SMTS-750 — Forwarder rejects mail body
- SMTS-815 — Sending mail report message
- SMTT-099 — Final startup failure message
- SMTT-120 — Triplet database not accessible
- SMTT-130 — Final message from triplet database purging
- SMTT-500 — Triplicator called for configuration w/o grey-listing
- SMTT-730 — Final message from triplet database purging
- SMTT-740 — Triplet database modification failed
- SMTT-741 — Triplet database modification incorrect - bad state
- SMTT-742 — Triplet database modification incorrect - bad date/time
- SMTT-743 — Triplet database modification incorrect - invalid IP address
- SMTT-744 — Triplet database modification incorrect - bad sender/recipient address
- SMTT-748 — Adding of redundant item to triplet database
- SMTT-749 — Triplet database modification incorrect
- SMTT-810 — Triplet information display
- SMTT-820 — Triplet database statistical information
- SMTT-830 — Final report message from triplet database cleanup
- SMTT-831 — Final report message from triplet database backup
- SMTT-832 — Final report message from triplet database restoring
- SMTV-139 — Greylisting switched off due to database error
- SMTV-371 — Checked domain SPF definition incorrect
- SMTV-388 — Domain name stripped suring SPF verification
- SMTV-389 — Checked domain SPF definition incorrect
- SMTV-540 — Grey-listing database filename too long
- SMTV-712 — SPF processing truncated
- SMTV-751 — No SPF definition for domain verified
- SMTV-752 — Checked domain SPF definition incorrect
- SMTV-758 — SPF processing truncated
- SMTV-759 — Final SPF processing message
- SMTV-761 — Checked domain SPF definition incorrect
- SMTV-762 — Checked domain SPF definition incorrect
- SMTV-763 — Checked domain SPF definition incorrect
- SMTV-771 — Checked domain SPF definition incorrect
- SMTV-772 — Checked domain SPF definition incorrect
- SMTV-780 — Checked domain SPF definition incorrect
- SMTX-590 — Boundary length out of bounds
- SQLP-090 — TCP server returned with error
- SQLP-099 — Final startup failure message
- SQLP-100 — Proxy main loop select call failed
- SQLP-104 — Original connection destination getting failed
- SQLP-200 — Proxy main loop timeout reached
- SQLP-239 — TCP socket closed by peer
- SQLP-500 — Database users checking not allowed in unknown protocols
- SQLP-550 — Connect string character set invalid
- SQLP-590 — Cannot use DB-USER for unknown protocol versions
- SQLP-801 — Client connection arrives to proxy
- SQLP-808 — Session has started, client connection has arrived
- SQLP-809 — Session finished
- SQLP-888 — Unified SQL proxy statistics message
- SQLS-105 — ALTQ queue assigment has failed
- SQLS-110 — Searching of ACL failed
- SQLS-119 — The proxy is unable to verify user authentication
- SQLS-131 — Connection to server failed
- SQLS-230 — Target server name cannot be resolved to IP address
- SQLS-231 — Target server cannot be connected within timeout period
- SQLS-232 — Target server connection failed
- SQLS-239 — TCP socket closed by peer
- SQLS-530 — Next-hop server/proxy name cannot be resolved to IP address
- SQLS-531 — Next-hop server/proxy cannot be connected within timeout period
- SQLS-532 — Next-hop server/proxy connection failed
- SQLS-533 — Address being to be forced as source toward the server cannot be resolved
- SQLS-700 — TNS protocol version information
- SQLS-711 — TNS protocol checksum is not zero
- SQLS-719 — SQL*Net service name exceeds configured limit
- SQLS-730 — SQL*Net proxy cannot determine target server
- SQLS-732 — Unexpected packet type received
- SQLS-740 — Packet exceeds Session Data Unit
- SQLS-741 — Packet length less than header size
- SQLS-742 — Data offset points into packet structure
- SQLS-743 — Packet is too short to contain data
- SQLS-747 — Server offers TDU less than SDU
- SQLS-748 — Server offers SDU out of valid range
- SQLS-749 — Transparent Network Substrate layer error
- SQLS-750 — Connect packet contains invalid connect string
- SQLS-751 — Connect packet contains invalid connect string
- SQLS-752 — Connect packet contains invalid connect string
- SQLS-753 — Incorrect character found in attribute name
- SQLS-754 — Real destination server cannot be determined
- SQLS-759 — Connect packet contains invalid connect string
- SQLS-760 — Connect string must contain named attribute
- SQLS-761 — Named attribute of connect string must be string
- SQLS-762 — Named attribute of connect string must be list
- SQLS-763 — Named attribute of connect string value invalid
- SQLS-771 — Too many redirection packets encountered
- SQLS-781 — Continuation packet exceeds total packet size
- SQLS-782 — Total length of fragmented message not reached
- SQLS-783 — MORE flag set in packet completing whole message
- SQLS-784 — Connect/redirect string packet splitted in incorrect offset
- SQLS-810 — ACL decision has been made, session either accepted or rejected
- SQLS-819 — Proxy user authentication finished
- SQLS-820 — ACL decision has been made, operation either accepted or rejected
- SQLS-831 — Connection to server was refused
- SQLS-832 — Connection to server was redirected to another server
- SQLS-840 — Session initialized, proxy is ready to mediate communication
- SQLS-850 — Connect string parser message
- SQLT-620 — SQL*Net RPC session authentication started
- SQLT-621 — Database user successfully authenticated by SQL server
- SQLT-622 — Database user logged off
- SQLT-628 — Database user logon failed
- SQLT-629 — Database user not allowed by configuration
- SQLT-720 — Logon packet has incorrect format
- SQLT-721 — Logon packet contain too long user name
- SQLT-722 — Logon packet contains user name with invalid characters
- SQLT-723 — SQL*Net RPC LOGON partially misunderstood
- SQLT-725 — SQL*Net proxy cannot recognize RPC LOGON encoding
- SQLT-727 — SQL*Net proxy registered database authentication result
- SQLT-728 — Incorrect logging sequence
- SQLT-729 — SQL*Net Remote Procedure Call received w/o authentication
- TCPC-100 — Socket for outgoing connection not created
- TCPC-210 — Function tcpclient() has successfully connected to server
- TCPC-218 — Connection to one of server's IP addresses failed
- TCPC-219 — Function tcpclient() failed to connect to server
- TCPC-229 — Source network address translation failed
- TCPP-104 — The main loop for serving clients (tcpserver) failed
- TCPP-105 — ALTQ queue assigment has failed
- TCPP-124 — The proxy cannot use SSL/TLS
- TCPP-200 — Proxy cannot configure NAT address mapping on connection to server
- TCPP-201 — Proxy cannot initialize data related to server connection
- TCPP-202 — Proxy cannot create modules for communication with the server
- TCPP-300 — Configured maximum of size of data from server to client exceeded
- TCPP-301 — Configured maximum of size of data from client to server exceeded
- TCPP-710 — A new proxy session has been started
- TCPP-711 — A proxy session has terminated
- TCPP-712 — Reports ACL used for this session
- TCPP-801 — Proxy cannot create modules for communication with the client
- TCPP-802 — The proxy cannot establish an SSL/TLS secure channel from the client
- TCPP-803 — The proxy cannot establish an SSL/TLS secure channel to the server
- TCPP-804 — The proxy is unable to verify user authentication
- TCPP-805 — The proxy cannot initialize client data filtering
- TCPP-806 — The proxy cannot initialize server data filtering
- TCPP-807 — Cannot set the value of the IP packet TOS field
- TCPP-850 — Some unexpected error occurred when searching ACLs
- TCPP-851 — No ACL matches the connection from the client
- TCPP-852 — The ACL matching the client connection denies access
- TCPP-853 — The proxy does not know to which server it should connect
- TCPP-888 — Unified TCP proxy statistics message
- TCPS-001 — The parent process encountered a child process in unknown state
- TCPS-002 — The child process encountered an unknown command from the parent
- TCPS-104 — Error during waiting for a connection on multiple sockets
- TCPS-105 — Error during accepting a connection on a socket
- TCPS-109 — Cannot allocate memory for communication between parent and children
- TCPS-110 — Cannot deallocate memory for communication between parent and children
- TCPS-113 — Allocation of file descriptor array by malloc() failed
- TCPS-115 — Kernun TCP server cannot create communication socket for listener
- TCPS-117 — Listener cannot control child processes
- TCPS-118 — Trying to kill a superfluos child which already terminated
- TCPS-119 — Killing a superfluos child failed
- TCPS-120 — Parent failed when trying to create a new child process
- TCPS-123 — The parent process tried to signal its children and received an error
- TCPS-124 — The parent process tried to signal its children and received an error
- TCPS-125 — Getting exit status of a terminated child process returned error
- TCPS-128 — Connection from client has been closed before accepted
- TCPS-220 — Listener communication channel is out of control
- TCPS-450 — Listener communication channel is out of control
- TCPS-500 — There are some invalid values in the configuration
- TCPS-501 — There are some invalid values in the configuration
- TCPS-502 — There are some invalid values in the configuration
- TCPS-503 — There are some invalid values in the configuration
- TCPS-540 — Connection rate limitation established
- TCPS-640 — Global connection rate counter reset
- TCPS-641 — Client violated CONN-RATE limitation
- TCPS-642 — Client violated CONN-RATE-PER-IP limitation
- TCPS-652 — Client violated MAX-CHILDREN-PER-IP limitation
- TCPS-700 — Notification about the mode of operation of the proxy
- TCPS-701 — The parent process finds out that all its children terminated
- TCPS-702 — The parent process finds out that a child was terminated by a signal
- TCPS-704 — The parent process finds out that a child exited
- TCPS-705 — The select() syscall returned and reported no ready file descriptor
- TCPS-706 — The proxy accepted a new connection from a client
- TCPS-707 — A client connection was handled
- TCPS-708 — Log level incremented in response to a received signal
- TCPS-709 — Log level decremented in response to a received signal
- TCPS-710 — Graceful proxy termination is performed after receiving a signal
- TCPS-711 — Immediate proxy termination is performed after receiving a signal
- TCPS-712 — Log level incremented in response to a received signal
- TCPS-713 — Log level decremented in response to a received signal
- TCPS-714 — The proxy parent process is waiting for termination of children
- TCPS-715 — Connection to a client was closed, proxy is waiting for another client
- TCPS-716 — The proxy has received an information request signal
- TCPS-717 — Statistical message about management of child processes
- TCPS-718 — The proxy has been initialized and is ready to accept packets
- TCPS-719 — Termination of a proxy process by a signal
- TCPS-722 — The proxy has unbound the sockets used for listening for clients
- TCPS-723 — The proxy has finished
- TCPS-730 — Log file will be reopened
- TCPS-731 — An alternative locking algorithm will be used
- TCPS-732 — The standard flock(2) locking algorithm will be used
- TCPS-733 — Kernun TCP server created communication socket for listener
- TCPS-800 — An address in an unsupported address family was specified for a socket
- TCPS-802 — There is not place for storing state of a new process
- TCPS-804 — A client connection was finished with error
- TCPS-805 — The child process with given PID cannot be found in the scoreboard
- TCPS-810 — The configured maximum of proxy child processes has been reached
- TCPS-811 — The tcpserver cannot be initialized properly
- TCPS-812 — Proxy runtime monitoring support cannot be initialized
- TCPS-813 — The tcpserver cannot be initialized properly
- TCPS-900 — Information about the number of server sockets
- TCPS-902 — The proxy starts serving connections from clients
- TCPS-903 — A client connection accepted, handling function will be called
- TCPS-904 — A new child process was started
- TCPS-905 — Initial set of children is being created
- TCPS-906 — The proxy parent process started initial children and continues
- TCPS-907 — A proxy child process is terminating itself
- TCPS-908 — Immediate child termination is performed after receiving a signal
- TCPS-909 — Graceful child termination is performed after receiving a signal
- TCPS-910 — Log level incremented in response to a received signal
- TCPS-911 — Log level decremented in response to a received signal
- TCPS-912 — The child process is superfluous and should exit
- TCPS-913 — The child process got SIGHUP, but there is no command from the parent
- TCPS-914 — The child process is superfluous and exits
- TCPS-915 — There are not enough idle children, parent is creating new ones
- TCPS-916 — There are too many idle children, some of them are asked to exit
- TEST-150 — Cannot display list of groups in configuration
- TEST-500 — Configuration tester expects command as -t option
- TEST-530 — Too high phase number requested
- UDPP-121 — Udp-proxy was not able to find an ACL appropriate to session
- UDPP-709 — Final proxy termination message
- UDPP-712 — The proxy is unable to verify user authentication
- UDPP-810 — A datagram from a client has arrived, a session has started
- UDPP-811 — Session initialized, proxy is ready to mediate communication
- UDPP-812 — Session finished
- UDPP-821 — ACL decision has been made, operation either accepted or rejected
- UDPP-888 — Unified UDP proxy statistics message
- UDPS-011 — An error occurred during waiting for a child process
- UDPS-109 — General select() error
- UDPS-110 — The proxy is unable to create a child process
- UDPS-121 — No route to client
- UDPS-141 — No route to server
- UDPS-242 — The proxy cannot initialize communication with a server
- UDPS-320 — The number of active sessions reached table size
- UDPS-350 — UDP datagram is being sent
- UDPS-360 — The proxy received too large datagram
- UDPS-368 — Amount of data transferred exceeded its limit during a session
- UDPS-369 — The number of datagrams reached its limit during a session
- UDPS-501 — There are no addresses on which the proxy should wait for datagrams
- UDPS-510 — The proxy has failed
- UDPS-540 — Cannot resolve name needed for server connection
- UDPS-541 — Session is non-transparent and no plug-to server found in acl
- UDPS-542 — Proxy cannot receive responses from server
- UDPS-543 — Cannot use aliased interface for source-port broadcast input and output
- UDPS-630 — Data from invalid host on server side socket
- UDPS-631 — Data from server occured in session of one-way type
- UDPS-700 — Notification about the mode of operation of the proxy
- UDPS-701 — The proxy has been initialized and is ready to accept packets
- UDPS-705 — Proxy-specific code encapsulated in special function has finished
- UDPS-708 — The proxy has unbound the sockets used for listening for clients
- UDPS-709 — The proxy has finished
- UDPS-710 — The child process was unexpectedly terminated
- UDPS-711 — The child process was unexpectedly terminated by a signal
- UDPS-730 — Server addres of an any-port or any-sock session will be fixed
- UDPS-751 — Session lasts longer than allowed and will be terminated
- UDPS-752 — The peer has not sent any data for too long
- UDPS-810 — Child process PID info
- UDPS-812 — Proxy runtime monitoring support cannot be initialized
- URIP-710 — Processing of %xx sequences in URI failed
- URIP-720 — URI cannot be parsed
- URIP-730 — Internal form of URI is invalid