ID |
Lvl Name |
|
Description |
0001 |
INF start |
|
Pserv has started. The server is mostly initialized. |
0004 |
BUG left_main_loop |
|
Somehow the main loop was terminated. This should never
happen. |
0005 |
INF shutdown_server |
|
The pserv server is shut down. |
0006 |
ADM dir_access_failed |
|
The opendir() system call on a mailbox directory failed. This
probably means that something is wrong with permissions in the pop
spool. |
0007 |
SOS out_of_memory |
|
Pserv couldn't allocate memory to hold a mail message
structure. |
0008 |
ADM name_too_long |
|
The name of a mailbox directory and file is too long. |
0009 |
ADM stat_failed |
|
The stat() system call failed for a mail message file. The message
will not be listed. This should never happen and probably means that
somebody tinkered around with a mailbox file by hand and got the
permission wrong. |
000a |
INF log_reopen |
|
The logfile will be reopened now. This should be the last message of
the parent process of the server to the log file. (See 000c for the
message in the new log file) |
000b |
SOS log_reopen_failed |
|
Reopening of the log file failed for some reason. The old file will
be kept open. |
000c |
INF log_reopened |
|
|
0014 |
SOS out_of_memory |
|
Pserv can't allocate memory for a msglist structure. |
0018 |
ERR unknown_command |
|
The client sent an unknown POP command. |
0019 |
SOS no_session_found |
|
The pserv parent process got a process id from wait() that he doesn't
know about, i.e. that shouldn't be one of his children. This should never
happen and probably means that there is some serious data corruption or a
bug in the program. pserv will immediately exit. |
0020 |
ADM child_died |
|
A child of pserv or pproxy died with non-zero exit code. See the log
entries of the child for more details about what happend. |
0021 |
SOS child_died_signal |
|
A child of pserv or pproxy died because of a signal. This can either
mean that there is a bug in the program of the system has big problems
(like running out of memory). |
0022 |
SOS out_of_memory |
|
There is no memory to allocate an io context struct. The program is
immediately terminated. |
0023 |
ERR getpeername_failed |
|
The getpeername() call failed. This probably means that the client
and subsequently the proxy has closed the connection. |
0024 |
ADM mailbox_too_long |
|
The mailbox name that the proxy sent to the pserv is too
long. |
0025 |
ADM mailbox_too_long |
|
The mailbox name that the proxy sent to the pserv is too
long. |
0026 |
ADM bad_mailbox |
|
The mailbox name that the proxy sent to the pserv has a leading
'/'. |
0027 |
ADM bad_mailbox |
|
The mailbox name that the proxy sent to the pserv has funny chars in
it. Only the following chars are allowed: a-z, A-Z, 0-9, '_', '-', '+',
'/', '=', '%'. Two adjacent dots ("..") are not
allowed. |
0028 |
ADM id_too_long |
|
The id that the proxy sent to the pserv is too long. |
0029 |
ADM id_too_long |
|
The id that the proxy sent to the pserv is too long. |
0030 |
ADM bad_id |
|
The id that the proxy sent to the pserv has funny chars in it. Only
the following chars are allowed: a-z, A-Z, 0-9, '.', '_', '-'. |
0031 |
ADM flags_too_long |
|
The flags that the proxy sent to the pserv are too long. |
0032 |
ADM flags_too_long |
|
The flags that the proxy sent to the pserv are too long. |
0033 |
ADM bad_flags |
|
The flags that the proxy sent to the pserv have funny chars in it.
Only a-z, A-Z, 0-9 are allowed. |
0034 |
INF login |
|
A new connection from the proxy is coming in and the mailbox name,
the logging id and the flags have been received. |
0035 |
ADM null_byte_in_input |
|
A null byte was encountered in input from a network socket. This can
never happen in a normal POP3 connection. |
0037 |
ADM msg_unlink_failed |
|
After the QUIT command has been received, the server tried to delete
a message but failed. |
0038 |
ADM msg_rename_failed |
|
After the QUIT command has been received, the server tried to rename
a message from the 'new' into the 'cur' directory but failed. |
0039 |
INF quit |
|
This message is logged after the client send a QUIT. It contains
statistics about the number of mails in mailbox, the number of new mails,
the number of read mails, and the number of deleted mails. |
003a |
SOS socket_call_failed |
|
When trying to open a listening socket, the socket system call
failed. |
003b |
SOS setsockopt_failed |
|
When trying to open a listening socket, the setsockopt call to set
SO_REUSEADDR failed. |
003c |
SOS bind_failed |
|
When trying to open a listening socket, the bind() failed. |
003d |
SOS listen_failed |
|
When trying to open a listening socket, the listen() failed. |
003e |
ERR accept_error |
|
The accept() call failed. This probably means that the client closed
the connection before the server could accept it. If this occures only
occasionally, it is harmless. If it occures more often, it might indicate
network problems. |
003f |
SOS fork_failed |
|
Pserv tried to fork a child and that failed. This probably means that
the system is overloaded. The connection to the client will be closed and
we try to keep going. |
0042 |
SOS select_error |
|
The select () syscall in the main loop returned an error that is not
handled. This should never happen. |
0047 |
ERR unknown_command |
|
An unknown POP3 command was received from the client. The client got
an error message. No action needs to be taken. |
0048 |
ERR user_name_too_long |
|
The user name that the client sent is too long for some internal
buffer. The buffer should be big enough for any sensible name. |
0049 |
ERR write_error |
|
An error occurred while writing to the client. This probably means
that the client closed the connection. |
004a |
ERR unknown_command |
|
An unknown POP3 command was received from the client. The client got
an error message. No action needs to be taken. |
004b |
ERR password_too_long |
|
The password that the client sent is too long for some internal
buffer. The buffer should be big enough for any sensible
password. |
004c |
ADM pdm_reload_failed |
|
The reloading of a pdm module failed because this module doesn't
support the pdm_reload() function. |
004d |
SOS pdm_error |
|
A module returned an internal error while checking a user. This means
that the module is confused, maybe the underlain database is corrupted.
Check for log messages from the module itself to find out more. |
004e |
SOS pdm_error |
|
A module returned an internal error while checking a user. This means
that the module is confused, maybe the underlain database is corrupted.
Check for log messages from the module itself to find out more. |
004f |
ERR readln_timeout |
|
A timeout occurred while waiting for an input line from a socket.
This probably means that the client went away. |
0050 |
ERR readln_error |
|
An error occurred while waiting for an input line from a socket. This
probably means that the client went away. |
0051 |
ERR readln_eof |
|
An end-of-file occurred while waiting for an input line from a
socket. This probably means that the client went away. |
0052 |
ERR readln_too_long |
|
A line was read that is too long. This might indicate an attack. The
buffer is long enough for any reasonable POP3 command etc. |
0053 |
ADM stat_failed |
|
The stat() of a mail message file failed. A size of 0 will be used.
The quota can't be calculated accurately. |
0054 |
ADM rename_failed |
|
After the mail message has been written to the 'tmp' directory, it
can't be renamed to the 'new' directory. |
0055 |
INF delivered |
|
A mail has been delivered successfully. |
0056 |
ADM opendir_failed |
|
The opendir() system call failed while trying to determine the
mailbox size. |
0057 |
ERR quota_exceeded |
|
The quota on a mailbox was exceeded. No mail will be
delivered. |
0058 |
ERR quota_exceeded |
|
The quota on a mailbox was exceeded. No mail will be
delivered. |
0059 |
SOS mailboxdir_error |
|
Pdeliver can't change into the mailbox directory. |
005a |
ADM open_tmpfile_failed |
|
Opening the tmp file for a new mail message failed. |
005b |
ADM fdopen_failed |
|
fdopen() on new tmp file for mail message failed. |
005c |
ADM write_mail_failed |
|
A write to the tmp file for a new mail message failed. |
005d |
ADM close_failed |
|
The close on the tmp file for a new mail message failed. |
005e |
INF debug_type |
|
The debug options were changed through pcontrol. These are the new
options that are used from now on. |
005f |
INF shutdown_all_received |
|
The command 'shutdown all' was received from pcontrol. The server
will shut down all it's children and the exit itself. |
0060 |
INF shutdown_parent_received |
|
The command 'shutdown parent' was received from pcontrol. The server
will shut down itself, but not its children. |
0061 |
ADM pcontrol_recvfrom_failed |
|
The call to recvfrom() to get a command from pcontrol
failed. |
0062 |
ADM pcontrol_sendto_failed |
|
The call to sendto() to send an answer to pcontrol failed. |
0063 |
ADM no_mailbox |
|
Changing into mailbox directory failed. |
0064 |
ADM mkdir_failed |
|
Creation of the mailbox directory failed. |
0065 |
ADM no_mailbox |
|
Changing into mailbox directory failed. |
0066 |
ADM mkdir_failed |
|
Creation of the 'new' directory failed. |
0067 |
ADM mkdir_failed |
|
Creation of the 'cur' directory failed. |
0068 |
ADM mkdir_failed |
|
Creation of the 'tmp' directory failed. |
0069 |
INF checking |
|
Checking user in POPular database modules. |
006a |
INF result_user_accepted |
|
The user was accepted by a pdm module. |
006b |
INF result_user_exists |
|
The user was found by a pdm module but authentication
failed. |
006c |
INF result_pdm_internal_error |
|
A pdm module returned an internal error. |
006d |
INF result_unknown_user |
|
The user was not found by any pdm module. |
006e |
INF result_unknown_result_code |
|
An unknown result code was returned by pdm_auth_user(). |
006f |
ADM unknown_protocol |
|
An unknown protocol identifier was used in the command file. The
program is terminated. |
0070 |
INF start |
|
Pcheckd has been started and partially initialized. |
0072 |
ADM invalid_mailbox |
|
The mailbox name that the client sent is invalid. The name is not
allowed to start with a '/' |
0073 |
ERR opendir_failed |
|
The 'new' directory for the given mailbox can't be opened. This
probably means that the mailbox hasn't been created yet. |
0074 |
ADM opendir_failed |
|
The 'cur' directory for the given mailbox can't be opened. |
0075 |
ADM unknown_request |
|
The client sent an unknown request. Allowed are 'L' for load check
and 'M' for mailbox check. |
0076 |
ERR sendto_failed |
|
Sending the answer of the requested check back to the client
failed. |
0077 |
SOS select_error |
|
The select () syscall in the main loop returned an error that is not
handled. This should never happen. |
0078 |
INF shutdown |
|
pcheckd received a QUIT, INT, TER, or PWR signal and is shutting
down. |
0079 |
INF debug_disabled |
|
pcheckd received a SIGUSR1 and disabled debuglogging. |
007a |
INF debug_enabled |
|
pcheckd received a SIGUSR2 and enabled debuglogging. |
007c |
SOS no_session_found |
|
The pproxy parent process got a process id from wait() that he
doesn't know about, i.e. that shouldn't be one of his children. This
should never happen and probably means that there is some serious data
corruption or a bug in the program. pproxy will immediately exit. |
007d |
INF shutdown_server |
|
The pproxy server is shut down. |
0084 |
INF open_port |
|
Pproxy has been instructed to listen to a new IP number and
port. |
0085 |
SOS port_open_send_failed |
|
Sending a port open request to the ringd process failed. |
0086 |
SOS port_open_failed |
|
Opening of the port failed for some reason on the pproxy
side. |
0087 |
SOS listen_failed |
|
The listen() system call on the just opened and bound socket
failed. |
0089 |
SOS fork_failed |
|
Pproxy tried to fork a child and that failed. This probably means
that the system is overloaded. The connection to the client will be closed
and we try to keep going. |
008a |
INF start |
|
PProxy has started and is mostly initialized. |
008d |
ADM pidfile_symlink_failed |
|
The symlink to the pidfile failed. The server will continue to
run. |
008e |
SOS select_error |
|
The select () syscall in the main loop returned an error that is not
handled. This should never happen. |
008f |
BUG left_main_loop |
|
Somehow the main loop was terminated. This should never
happen. |
0096 |
SOS backend_socket_call_failed |
|
Creating a socket for a connection to the backend failed. |
0097 |
SOS connect_to_backend_failed |
|
The connect to a backend failed. |
0098 |
SOS backend_read_err |
|
A read from a POP3 backend failed. |
0099 |
SOS backend_not_ready |
|
A POP3 backend sent a -ERR reply on connection. |
009a |
SOS backend_read_err |
|
A write to a POP3 backend failed. |
009b |
SOS backend_read_err |
|
A read from a POP3 backend failed. |
009c |
ADM login_failed |
|
The login to a POP3 backend server failed. The answer to the USER
command was -ERR. |
009d |
SOS backend_read_err |
|
A write to a POP3 backend failed. |
009e |
SOS backend_read_err |
|
A read from a POP3 backend failed. |
009f |
ADM login_failed |
|
The login to a POP3 backend server failed. The answer to the PASS
command was -ERR. |
0100 |
SOS socket_call_failed |
|
The creation of a UDP socket to talk to the pcheckd on a backend
failed. |
0101 |
SOS connect_failed |
|
The connect() call on the UDP socket to the pcheckd on a backend
failed. |
0102 |
SOS buffer_to_small |
|
A buffer for sending a mailbox name to the pcheckd is too
small. |
0103 |
SOS send_failed |
|
The send() call sending a request to the pcheckd failed. |
0104 |
SOS select_failed |
|
The select () call waiting for answer from pcheckd failed in an
unexpected way. |
0105 |
SOS recv_failed |
|
Recv() call failed when reading answer from pcheckd. |
0106 |
ERR check_udp_timeout |
|
Pproxy timed out waiting for an answer from pcheckd. |
0107 |
ERR timeout |
|
A timeout occurred while proxying data. |
0108 |
INF quit |
|
The proxy child shuts down after its work is done. The proxied bytes
in both directions are reported. |
0109 |
INF quit |
|
The client closed the connection while faking a POP3 dialog. |
010a |
INF quit |
|
The client send a quit while faking a POP3 dialog. |
010c |
SOS out_of_memory |
|
There is not enought memory to allocate an IO context. |
010d |
SOS write_to_backend_failed |
|
A write call to the backend failed. |
010f |
SOS out_of_memory |
|
There is not enought memory to allocate an IO context. |
0110 |
BUG illegal_value |
|
The do_pop3_auth() function returned an illegal value. |
0111 |
ERR getsockname_error |
|
getsockname() returned an error. This probably means that the client
disconnected before we could look at the socket. |
0112 |
ERR getpeername_error |
|
getpeername() returned an error. This probably means that the client
disconnected before we could look at the socket. |
0113 |
INF connect |
|
Incoming connection from client. |
0114 |
BUG unknown_protocol |
|
No protocol information for this virtual server is found. This should
never happen. |
0116 |
SOS out_of_memory |
|
There is not enought memory to allocate an IO context. |
0117 |
INF virt_serv_disabled |
|
The virtual server is disabled |
0118 |
ERR write_error |
|
A write to the client failed. |
0119 |
ERR write_error |
|
A write to the client failed. |
011b |
ERR quit |
|
Client sent QUIT command in authentication phase. |
011c |
INF virt_serv_fake |
|
The virtual server is to be faked. |
011d |
ERR auth_fail |
|
The authorisation of the user failed because of the client IP
number. |
011e |
ERR auth_fail |
|
The authorisation of the user failed because of the protocol
used. |
011f |
ERR auth_fail |
|
The authorisation of the user failed because the wrong password was
given. |
0120 |
ERR auth_fail |
|
The authorisation of the user failed for unknown reasons. |
0121 |
BUG illegal_auth_result |
|
A PDM module returned an illegal result code. |
0122 |
SOS unknown_backend |
|
A PDM module told us which backend to use. Unfortunately this backend
is not configured. |
0123 |
INF user_auth |
|
User was authenticated. |
0124 |
INF operation |
|
The backend is configured to be faked. |
0125 |
INF quit |
|
The backend is configured to be offline. |
0126 |
INF operation |
|
The backend uses POP3 protocol. Proxying will now be
started. |
0127 |
INF operation |
|
The backend pcheckd told us that the mailbox is empty, the load on
the storage server is too high, or the maximum number of sessions is
reached on the storage server or a timeout occured while waiting for the
answer from the pcheckd. The POP connection will be faked
locally. |
0128 |
INF operation |
|
The backend uses XPOP protocol. Proxying will now be
started. |
0129 |
BUG invalid_value |
|
Invalid value for the backend protocol. |
012a |
BUG invalid_value |
|
Invalid value for the backend state. |
012b |
INF shutdown_children_received |
|
The command 'shutdown children' was received from pcontrol. The
server will shut down all it's children. |
012c |
INF shutdown_children |
|
The pproxy server is shutting down all its children. |
012d |
INF shutdown_children |
|
The pserv server is shutting down all its children. |
012e |
INF shutdown_delayed |
|
The pproxy server closed all listening ports. After all children have
died, it will close down. |
012f |
INF shutdown_delayed_received |
|
The command 'shutdown delayed' was received from pcontrol. The server
will not accept new connections and shut down itself after the last child
has died. |
0130 |
INF all_children_gone |
|
All children have died and the server got a delayed shutdown command
earlier. It will shutdown now. |
0131 |
INF all_children_gone |
|
All children have died and the server got a delayed shutdown command
earlier. It will shutdown now. |
0132 |
INF shutdown_delayed |
|
The pserv server closed the listening ports. After all children have
died, it will close down. |
0133 |
INF got_term_signal |
|
The child got a TERM or INT signal and will shut down. This signal
was either delivered to the parent between the last check for signals and
the fork, or it was delivered to the child before the child could change
its signal handling to the default behaviour. In any case, calling exit
immediately is the right thing to do here. |
0135 |
SOS open_statefile |
|
Open of the state file failed. The program will be
terminated. |
0136 |
SOS seek_statefile |
|
Seeking inside the state file failed. The program will be terminated.
Try deleting the state file before restarting. |
0137 |
SOS write_statefile |
|
Writing to state file failed. The program will be terminated. Try
deleting the state file before restarting. |
0138 |
SOS mmap_statefile |
|
Mmapping the state file failed. The program will be terminated. Try
deleting the state file before restarting. |
0139 |
ADM symlink_statefile_failed |
|
The symlinking of the real state file to its symbolical name failed.
The server will still work, but the pstatus program will not find the
state file. |
013a |
SOS control_socket_open_failed |
|
Opening of the UNIX domain control socket failed. The program will be
terminated. |
013b |
SOS control_bind_failed |
|
Binding the UNIX domain control socket failed. The program will be
terminated. |
013c |
SOS control_symlink_failed |
|
Linking the UNIX domain control socket to the canonical name failed.
The programm will be terminated. |
0140 |
ADM pidfile_open_failed |
|
The opening of the pidfile failed. The server will continue to
run. |
0141 |
ADM unlink_file_in_rundir_failed |
|
An unlink() operation in the run directory failed. The file can be a
pid file, the state file or the control socket. |
0142 |
ADM unlink_link_in_rundir_failed |
|
An unlink() operation in the run directory failed. The filename is a
link to either a pid file, a state file or a control socket. |
0143 |
SOS port_open_no_fd |
|
The opening and binding of the port by the ringd process failed for
some reason. The message from the ringd process is printed with this
message. |
0144 |
INF stat |
|
Statistics from pcheckd: 'requests' is the number of all requests
that pcheckd got, 'mailchecks' is the number of new format mailcheck
requests, 'mailchecks_old' the number of old format mailcheck requests,
'empty' the number of requests finding an empty mailbox, 'not_empty' the
number of requests finding a not empty mailbox, 'load_too_high' the number
of requests answered with that message, and the number of messages send
while the maximum number of pserv sessions was used. The statistics are
logged and cleared on SIGHUP. |
0145 |
SOS select_error |
|
An error occurred in the select () system call while proxying
data. |
0146 |
ERR accept_failed |
|
The accept () system call failed for some reason. |
0147 |
ERR msg_rename_failed |
|
Renaming of a mail file failed, because it is not there. Another
pserv process probably got to this file before we did. |
0148 |
ERR msg_unlink_failed |
|
Deleting of a mail message failed. Probably another pserv process was
faster. |
0149 |
ADM config_set |
|
A config variable was set to a new value. |
014a |
BUG sigaction_failed |
|
A sigaction () system call failed. This should never happen. |
014b |
ADM config_set |
|
A config variable was set to a new value. |
014d |
ADM config_set |
|
A config variable was set to a new value. |
014e |
ADM server_now_online |
|
The server listens on a port now and accepts connections. You should
see this log message in response to a 'server online' command. |
014f |
ADM server_now_offline |
|
The server closed its listening port and doesn't accept any new
connections. You should see this log message in response to a 'server
offline' command. |
0150 |
ADM config_capa |
|
Capability was configured |
0151 |
ADM config_capa |
|
Capability was configured |
0152 |
ADM config_capa |
|
Capability was configured |
0153 |
ADM config_capa |
|
Capability was configured |
0154 |
ADM bad_mailbox |
|
The mailbox name that the proxy sent to the pserv has funny chars in
it. Only the following chars are allowed: a-z, A-Z, 0-9, allowed. |
0155 |
SOS fork_failed |
|
The fork () system call in pcheckd failed. |
0156 |
ADM child_died |
|
A child of pcheckd died with non-zero exit code. See the log entries
of the child for more details about what happened. |
0157 |
ADM child_died_signal |
|
A child of pcheckd died because of a signal. This can either mean
that there is a bug in the program of the system has big problems (like
running out of memory). |
0158 |
ERR mailfile_does_not_exist |
|
A mail message file does not exist. This probably means that the mail
has been deleted by another POP session running at the same time. |
0159 |
ADM mailfile_open_failed |
|
Opening a mail message file for reading failed. |
015a |
SOS mailfile_mmap_failed |
|
The mmap () system call on the mail message file failed. |
015b |
SOS mailfile_munmap_failed |
|
The unmap () system call on the mail message file failed. |
015d |
ERR write_error |
|
Error writing mail message to proxy socket. |
015e |
ERR write_error |
|
Error writing mail message to proxy socket. |
015f |
ERR write_error |
|
Error writing mail message to proxy socket. |
0160 |
ADM config_set |
|
A boolean config variable was set to a new value. (0=no=off=false,
1=yes=on=true) |
0161 |
ERR write_error |
|
Error writing mail message to proxy socket. |
0162 |
ADM msg_size_zero |
|
A mail message has size zero. It will not be listed. |
0163 |
ADM config_backend_del |
|
A 'backend del' command was executed. |
0164 |
ADM config_backend_flush |
|
A 'backend flush' command was executed. |
0165 |
ADM config_backend_conf |
|
A 'backend conf' command was executed. |
0166 |
ADM config_vserv_conf |
|
A 'vserv conf' command was executed. |
0167 |
ADM config_vserv_flush |
|
A 'vserv flush' command was executed. |
0168 |
ADM config_vserv_del |
|
A 'vserv del' command was executed. |
0169 |
ADM config_capa_load |
|
A 'capa load' command was executed. |
016a |
ADM config_capa_del |
|
A 'capa del' command was executed. |
016b |
ADM config_pdm_add |
|
A 'pdm add' command was executed. |
016c |
ADM config_pdm_del |
|
A 'pdm del' command was executed. |
016d |
ADM config_pdm_reload |
|
A 'pdm reload' command was executed. |
016e |
ADM config_pdm_flush |
|
A 'pdm flush' command was executed. |
016f |
BUG illegal_session_state |
|
The state in sess_ok() has an illegal value. This can never happen.
The server keeps going but might log strange things. |
0170 |
ADM session_state |
|
The session state is printed. This can be one of 'OK', 'WARN', 'MAX'.
See the documentation for the exact meaning of these messages. |
0171 |
BUG illegal_load_state |
|
The state in sess_load() has an illegal value. This can never happen.
The server keeps going but might log strange things. |
0172 |
ADM load_state |
|
The load state is printed. This can be one of 'OK', 'WARN', 'MAX'.
See the documentation for the exact meaning of these messages. |
0173 |
SOS touch_failed |
|
Creating or 'touching' of a flag file failed. |
0174 |
SOS unlink_failed |
|
Unlink of a flag file failed. |
0177 |
ERR auth_fail |
|
The authorisation of the user failed because the user is
unknown. |
0178 |
ADM select_error |
|
The rel_select() call failed. |
0179 |
INF operation |
|
The backend uses XPOP protocol. Proxying will now be
started. |
017a |
ADM config_set |
|
A config variable was set to a new value. |
017c |
ERR child_died_timeout |
|
A child of pserv or pproxy died because of an ALRM signal. This means
that 'sessiontimeout' (or, for pproxy, 'authtimeout') ran out. |
017d |
INF msg_info |
|
A message was deleted. |
017e |
INF msg_info |
|
A message was moved from new to cur. |
017f |
ERR too_many_bad_commands |
|
Too many bad commands were received while in auth phase. The server
will close the connection. The number is configured in the
MAX_BAD_COMMANDS define in pconfig.h |
0180 |
ERR too_many_bad_commands |
|
Too many bad commands were received while in auth phase. The server
will close the connection. The number is configured in the
MAX_BAD_COMMANDS define in pconfig.h |
0181 |
SOS sock_open_failed |
|
Pproxy tried to open a unix domain socket to talk to the ringd and
this failed |
0182 |
SOS sock_connect_failed |
|
Pproxy tried to connect to the unix domain socket of the ringd and
this failed |
0183 |
INF start |
|
ringd has started. |
0184 |
SOS open_socket |
|
ringd can't open the unix domain socket to listen for
commands. |
0185 |
SOS chown_socket |
|
ringd can't chown its unix domain socket. |
0186 |
INF quit |
|
ringd go a signal and will quit now. |
0187 |
SOS socket_max_reached |
|
The maximum number of sockets is reached. If you need more sockets
change RINGD_MAX_SOCK and recompile. |
0188 |
ADM socket_error |
|
The socket system call returned an error. |
0189 |
ADM setsockopt_error |
|
The setsockopt system call returned an error. |
018a |
SOS bind_error |
|
The bind system call returned an error. |
018b |
INF port_list |
|
List of currently opend ports. |
018c |
ADM unknown_command |
|
ringd received an unknown command. |
018d |
ADM space_char_missing |
|
ringd misses the space char at the 2nd position in the command string
which separates the command from arguments. |
018e |
ADM space_char_missing |
|
ringd misses the space char in the command string which separates the
first from the second argument |
018f |
ADM port_invalid |
|
The port number given as second argument to a ringd command is
syntactically invalid. |
0190 |
ADM port_out_of_range |
|
The port number given as second argument to a ringd command is out of
range. |
0191 |
ADM port_forbidden |
|
The port number given as second argument to a ringd command is
forbidden by configuration (change ALLOWED_PORTS and recompile). |
0192 |
ADM invalid_ip |
|
The port number given as first argument to a ringd command is is
invalid. |
0193 |
INF close_port |
|
Pproxy has been instructed to listen to a new IP number and
port. |
0194 |
SOS port_close_send_failed |
|
Sending a port close request to the ringd process failed. |
0195 |
SOS port_close_failed |
|
Closing of the port failed for some reason on the pproxy
side. |
0196 |
SOS server_method_failed |
|
A SSL*_server_method() call failed. This probably means that there is
something wrong with your openssl library setup. |
0199 |
ERR tls_init_failed |
|
Initialization of new TLS connection failed (SSL_new call
failed). |
019a |
ERR tls_set_fd_failed |
|
Initialization of new TLS connection failed (SSL_set_fd call
failed). |
019b |
ERR tls_accept |
|
Initialization of new TLS connection failed (SSL_accept call
failed). |
019c |
BUG unknown_protocol |
|
No protocol information for this virtual server is found. This should
never happen. |
019d |
ADM key_file_error |
|
The TLS key file could not be opened. (Call to
SSL_CTX_use_RSAPrivateKey_file failed.) |
019e |
ADM certificate_file_error |
|
The TLS key file could not be opened. (Call to
SSL_CTX_use_RSAPrivateKey_file failed.) |
019f |
ERR tls_init_after_stls_failed |
|
Initialization of new TLS connection after STLS failed. The
connection will be dropped because we can't do anything else at this
point. The +OK was already sent because we had to send it before
initializing TLS on this socket. |
0200 |
INF switch_to_tls |
|
Connection is switched to TLS after STLS command. |
0201 |
INF switch_to_tls |
|
Connection is switched to TLS after STLS command. |
0202 |
ERR tls_init_after_stls_failed |
|
Initialization of new TLS connection after STLS failed. The
connection will be dropped because we can't do anything else at this
point. The +OK was already sent because we had to send it before
initializing TLS on this socket. |
0203 |
SOS tls_seed_failed |
|
Initialization of the TLS pseudo random number generator failed. This
is serious because it could potentially mean that there is no security at
all. |