Enhanced PHP File Manager

⬆️ Go Up (..)

📊 Server Information

Server:

nginx/1.28.0

System:

Linux 6.8.0-90-generic

PHP Version:

8.4.15

User:

alqudsvolunteers

Directory:

/home/alqudsvolunteers/rootlink/usr/share/doc/proftpd-doc/howto

Free Space:

81.7 GB

🔧 Quick Actions

✏️ Editing: LogMessages.html

<!DOCTYPE html>
<html>
<head>
<title>ProFTPD Logging: Log Messages</title>
</head>

<hr>
<center><h2>ProFTPD Logging: Log Messages</h2></center>
<hr>

Log Messages
This document attempts to list the most common messages logged (either via
<code>syslog</code> or the <code>SystemLog</code> file), grouped by the
<a href="LogLevels.html">log level</a> for the message.

<a name="EMERG">
<code>EMERG</code> Log Messages 
There are currently no <code>EMERG</code>-level messages logged by
<code>proftpd</code>.

<a name="ALERT">
<code>ALERT</code> Log Messages 
<code>ALERT</code>-level messages are logged by <code>proftpd</code> when a
crucial system resource (e.g. memory, CPU, file descriptors, disk
space) has been exhausted.

<ul>
 <li>"Out of memory!" 
 This log message can be generated by various core subsystems and modules,
 and indicates that <code>proftpd</code> could not allocate enough memory.
 </li>

<li>"unable to fork" 
 This log message indicates that <code>proftpd</code> tried to fork a new
 process (e.g. to read passphrases, execute a script, etc) and
 failed. This can happen when the process table is full, or when there is
 not enough system memory to create a new process.
 </li>

<li>"cannot write ExtendedLog", or "failed to write file: No space on device" 
 These log messages indicate that the filesystem on which the files are
 being written is out of space.
 </li>
</ul>

<a name="CRIT">
<code>CRIT</code> Log Messages 
There are currently no <code>CRIT</code>-level messages logged by
<code>proftpd</code>.

<a name="ERR">
<code>ERR</code> Log Messages 
<code>ERR</code>-level messages are logged by <code>proftpd</code> when
<code>proftpd</code> cannot start up because it cannot use the given
configuration for some reason: no DNS resolution for hostnames, unable to listen
on addresses/ports, or necessary cryptographics keys/certs are unusable.
<ul>
 <li>Failed binding to address, port port 
 Check the ServerType directive to ensure you are configured correctly 
 Check to see if inetd/xinetd, or another proftpd instance, is already using address, port port 
 
 When <code>proftpd</code> starts up, it will attempt to bind sockets to,
 and listen on, all of the configured addresses/ports. If it cannot bind
 to an address/port, the above message is logged. As mentioned in the log
 message, the most common cause is that another <code>proftpd</code> daemon
 is running and is using the address/port, or that
 <code>inetd/xinetd</code> is using the address/port because your FTP
 server is supposed to be run that way; if so, check that the
 <a href="ServerType.html"><code>ServerType</code></a> in the
 <code>proftpd.conf</code> file is "inetd" and not "standalone".
 </li>

<li>"unable to listen on address#port" 
 When <code>proftpd</code> starts up, it will attempt to bind sockets to,
 and listen on, all of the configured addresses/ports. If it cannot listen
 on an address/port, the above message is logged. The most common cause of
 this message is the use of different DNS names in
 <code>&lt;VirtualHost&gt;</code> sections which resolve to the same IP
 address(es). FTP, unlike HTTP, only deals with IP addresses, and thus
 <code>proftpd</code> resolves the <code>&lt;VirtualHost&gt;</code> DNS name
 to its IP address, then listens on that address. If two different
 <code>&lt;VirtualHost&gt;</code> sections have different DNS names which
 resolve to the same IP address, then the first section will get the
 address, and listening to the second address will fail (probably with the
 "Address already in use" error).
 </li>

<li>"(Running from command line? Use `ServerType standalone' in config file!)" 
 This log message almost always happen when you have "ServerType inetd" in
 your <code>proftpd.conf</code>, but you are attempting to start
 <code>proftpd</code> from the command line (or some init script). Chances
 are that you do not really want to be doing this; if you do, see the
 <a href="ServerType.html"><code>ServerType</code></a> docs for more
 information.
 </li>

<li>"unable to accept incoming connection" 
 The server cannot accept a TCP connection from a remote client; the most
 likely cause is too many open files (which includes sockets) and hitting
 the per-process, or the system-wide, open file limit.
 </li>

<li>"chroot to directory failed for user name" 
 Restricting users via the <a href="Chroot.html">DefaultRoot</a> directive
 requires that the logging-in user have the execute permission on
 the target directory. Without that permission -- or if there are other
 filesystem permission errors -- the above message will be logged.
 </li>

<li>"RELINQUISH PRIVS", "REVOKE PRIVS", "ROOT PRIVS", "SETUP PRIVS", "USER PRIVS", "unable to set UID/GID"
 These log messages indicate that changing the UID/GID of the current
 process (as during authentication, or the handling of
 <a href="../modules/mod_core.html#UserOwner"><code>UserOwner</code></a>/<a href="../modules/mod_core.html#GroupOwner"><code>GroupOwner</code></a>
 directives) has failed for some reason. The most common cause of these
 messages is starting <code>proftpd</code> as a non-root user.
 </li>

<li>"unable to open log-file: parent-dir is a world-writable directory" 
 These log messages indicate that your logging configuration is
 insecure. Log files in a world-writable directory can be deleted or
 modified by any user on the system, which means that your logged
 data cannot be trusted. For this reason, <code>proftpd</code> refuses to
 write log files to such directories.
 </li>

<li>"unable to open log-file: log-file is a symbolic link" 
 These log messages indicate that your logging configuration may be
 insecure. Symbolic links are subject to race conditions, where a local
 user on the system might try to replace portions of the symlink path with
 their own directories, changing the symlink to point somewhere else, such
 as causing the log file to overwrite an existing file (e.g.
 <code>/etc/passwd</code>).

For this reason, <code>proftpd</code> refuses to write log files to
 symlinks, unless configured to do so via the <a href="../modules/mod_log.html#AllowLogSymlinks"><code>AllowLogSymlinks</code></a> directive.
 </li>

<li>"unable to open log-file" 
 These log messages indicate that the log file could be not used for some
 other reason, such as lack of permissions or nonexistent directories.
 </li>

<li>"mod_sql: unrecoverable backend error" 
 Backend database server (e.g. MySQL, Postgres, SQLite, etc)
 rejected the SQL statement being executed. This usually happens when a
 table or column in the SQL statement does not exist, or if the table/column
 names have a typo/mismatch between the config file and database server.
 </li>

<li>"error: unable to set groups: Invalid argument" 
 Setting the list of GIDs to use for the logged-in user uses the
 <code>setgroups(2)</code> system call, which has some restrictions. Most
 notably, attempting to make the user be a member of too many groups will
 cause the above error. The maximum number of groups varies from platform
 to platform, but can be anywhere from 4 to 32 (or more).
 </li>

<li>"error opening scoreboard" 
 The <a href="Scoreboard.html"><code>ScoreboardFile</code></a> is needed for
 useful things like <code>ftpwho</code> and <code>ftptop</code>, thus if the
 path cannot be opened, <code>proftpd</code> will fail to start. The most
 common cause for this failure is that the configured
 <code>ScoreboardFile</code> is in a directory which does not exist; the
 parent directory must exist prior to starting <code>proftpd</code>.
 </li>

<li>"Malformed entry in AuthUserFile/AuthGroupFile" 
 The configured <a href="AuthFiles.html">AuthUserFile/AuthGroupFile</a>
 has a line which is not in the necessary format. The most common cause
 for this is when one of the file fields is missing, or if there an extra
 colon (':') character in a field (e.g. in the name field).
 </li>
</ul>

<a name="WARNING">
<code>WARNING</code> Log Messages

<a name="NOTICE">
<code>NOTICE</code> Log Messages

<a name="INFO">
<code>INFO</code> Log Messages 
<code>INFO</code>-level messages are logged by <code>proftpd</code> when
common events happen: a connection session begins/ends, a user logs in,
idle connections are dropped, etc.
<ul>
 <li>"FTP/SSH2 session opened/closed" 
 When a client connects, a session process begins. The type of session
 (i.e. FTP, SSH2, etc) is determined by the server to which
 the client connected.
 </li>

<li>"USER user: Login successful" or "ANON user: Login successful" 
 Successful authentication (via password, or anonymously) happened, as
 opposed to a failed authentication/login.
 </li>

<li>"address:port masquerading as address" 
 This message is logged when the <a href="../modules/mod_core.html#MasqueradeAddress"><code>MasqueradeAddress</code></a> directive is in effect.
 </li>

<li>"Client session idle timeout, disconnected" 
 The configured <a href="../modules/mod_core.html#TimeoutIdle"><code>TimeoutIdle</code></a> was reached while the client did nothing useful, and so the
 client had to be disconnected. This is quite common/normal.
 </li>

<li>"mod_dso: module name already loaded" 
 This log message happens when a <a href="../modules/mod_dso.html#LoadModule"><code>LoadModule</code></a> directive attempts to load a module which has
 already been loaded, either by a previous <code>LoadModule</code> directive
 or because the named module is a static module (and is thus always
 "loaded"). Either way, this log message indicates that the configuration
 has redundant <code>LoadModule</code> directives which can be removed.
 </li>
</ul>

<a name="DEBUG">
<code>DEBUG</code> Log Messages 
There are many <code>DEBUG</code>-level messages logged by
<code>proftpd</code>. This section will be filled, over time, with the
ones most commonly seen/asked about by users.

<a name="strerror">
Many of the reasons for various errors/failures that appear in log messages
(and elsewhere) come from the <code>strerror(3)</code> libc function, which
provides human readable strings, given a numeric <code>errno</code> value.
The table below lists the reason strings you may commonly see, with a fuller
description of what it means.

<table border=1 summary="Error Messages">
 <tr>
 <td>Message</td>
 <td>Code</td>
 <td>Details</td>
 </tr>

<tr>
 <td>&nbsp;Operation not permitted&nbsp;</td>
 <td>&nbsp;<code>EPERM</code>&nbsp;</td>
 <td>Indicates that the requested operation cannot be done for some reason,
 usually caused by misconfigurations or lack of system support/resources.
 Note: Some platforms (e.g. Solaris) actually translate the
 <code>EACCES</code> code to this message, which is confusing.
 </td>
 </tr>

<tr>
 <td>&nbsp;Permission denied&nbsp;</td>
 <td>&nbsp;<code>EACCES</code>&nbsp;</td>
 <td>Means that the request operation is not allowed due to access controls:
 the logged-in user does not have sufficient filesystem permissions
 to open/read/write/delete a file/directory, the logged-in user (or
 client) is barred from access by configuration, etc.
 </td>
 </tr>

<tr>
 <td>&nbsp;Invalid argument&nbsp;</td>
 <td>&nbsp;<code>EINVAL</code>&nbsp;</td>
 <td>This generic message indicates that the supplied parameters are
 considered invalid; the reasons behind this are myriad, depending on
 the requested operation.
 </td>
 </tr>

<tr>
 <td>&nbsp;No such file or directory&nbsp;</td>
 <td>&nbsp;<code>ENOENT</code>&nbsp;</td>
 <td>The requested resource does not exist; can apply to files,
 directories, and other non-filesystem resources.
 </td>
 </tr>

<tr>
 <td>&nbsp;Is a directory&nbsp;</td>
 <td>&nbsp;<code>EISDIR</code>&nbsp;</td>
 <td>The requested operation expects to operate on a file, but the
 requested resource was a directory, not a file.
 </td>
 </tr>

<tr>
 <td>&nbsp;Bad file descriptor&nbsp;</td>
 <td>&nbsp;<code>EBADF</code>&nbsp;</td>
 <td>Read/write/close/delete operation on a file was requested on a
 file descriptor which was not already opened.
 </td>
 </tr>

<tr>
 <td>&nbsp;Address already in use&nbsp;</td>
 <td>&nbsp;<code>EADDRINUSE</code>&nbsp;</td>
 <td>Process is attempting to listen on a network address/port which is
 already bound; usually some other process on the system is listening
 on that address (e.g. <code>inetd</code>/<code>xinetd</code>).
 </td>
 </tr>

<tr>
 <td>&nbsp;Broken pipe&nbsp;</td>
 <td>&nbsp;<code>EPIPE</code>&nbsp;</td>
 <td>Process tried to send something to a connected TCP peer, and found
 out that the connection had already been closed; can happen when
 a firewall/router/NAT between TCP peers silently closes the connection
 without informing one or both peers.
 </td>
 </tr>

<tr>
 <td>&nbsp;Connection reset by peer&nbsp;</td>
 <td>&nbsp;<code>ECONNRESET</code>&nbsp;</td>
 <td>Remote TCP peer sent the <code>RST</code> TCP flag, indicating that
 the connection should be reset; this almost always indicates an
 issue with the connected client (or some firewall/router/NAT device
 between the client and the server).
 </td>
 </tr>

<tr>
 <td>&nbsp;Connection refused&nbsp;</td>
 <td>&nbsp;<code>ECONNREFUSED</code>&nbsp;</td>
 <td>The remote peer refused to accept the TCP connection; could be
 firewalls/routers/NATs in the way, other network ACLs that deny the
 connection, etc.
 </td>
 </tr>

<tr>
 <td>&nbsp;Too many open files&nbsp;</td>
 <td>&nbsp;<code>EMFILE</code>&nbsp;</td>
 <td>Per-process limit of number of open files (including sockets)
 has been reached.
 </td>
 </tr>

<tr>
 <td>&nbsp;Too many open files in system&nbsp;</td>
 <td>&nbsp;<code>ENFILE</code>&nbsp;</td>
 <td>System-wide limit of number of open files (including sockets)
 has been reached.
 </td>
 </tr>
</table>

</body>
</html>

❌ Cancel

🗂️ Enhanced PHP File Manager

📊 Server Information

🔧 Quick Actions

✏️ Editing: LogMessages.html

📤 Upload File

📁 Create Folder

📄 Create File

✏️ Rename Item

🗑️ Delete Confirmation