ProFTPD 1.3.4c released

Thanks, updated on files1.
Please allow up to 24 hours for the other files mirrors to get the rsync.

John
 
We're facing issues with ProFTPd 1.3.4c, we use it as sFTP server. It started segfaulting with "ProFTPD terminating (signal 11)" error in logs soon after we upgraded. I have no idea why that happens. One thing I might say, after re-start it keeps working and allowing connection for about 2-8 hours, and then stops allowing new connections.

In filezilla you may see:

Response: fzSftp started
Command: open "[email protected]" xxxx
Error: Server unexpectedly closed network connection
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to "[email protected]" xxxx...
Response: fzSftp started
Command: open "[email protected]" xxxx
Error: Server unexpectedly closed network connection
Error: Could not connect to server
Click to expand...

So we (I mean my particular case, not all of you) need either reboot it with cron, or downgrade, as for now I have no idea why that happens.
 
I guess it's somehow relates to SIGHUP, as the errors appears soon after it:

Code: 
[root@host rotated]# grep SIGHUP system.log.1 --after=2
Mar 13 18:06:02 host.domain.com proftpd[6124] 195.bb.cc.dd: received SIGHUP -- master server reparsing configuration file
Mar 13 18:07:52 host.domain.com proftpd[705] 195.bb.cc.dd (37.192.cc.dd[37.192.cc.dd]): SSH2 session opened.
Mar 13 18:07:53 host.domain.com proftpd[705] 195.bb.cc.dd (37.192.cc.dd[37.192.cc.dd]): ProFTPD terminating (signal 11)
--
Mar 13 18:13:06 host.domain.com proftpd[6124] 195.bb.cc.dd: received SIGHUP -- master server reparsing configuration file
Mar 13 18:13:06 host.domain.com proftpd[4969] 195.bb.cc.dd (37.192.cc.dd[37.192.cc.dd]): SSH2 session opened.
Mar 13 18:13:06 host.domain.com proftpd[4969] 195.bb.cc.dd (37.192.cc.dd[37.192.cc.dd]): ProFTPD terminating (signal 11)
--
Mar 13 18:38:03 host.domain.com proftpd[6124] 195.bb.cc.dd: received SIGHUP -- master server reparsing configuration file
Mar 13 18:44:02 host.domain.com proftpd[6124] 195.bb.cc.dd: received SIGHUP -- master server reparsing configuration file
Mar 13 18:47:02 host.domain.com proftpd[7818] 195.bb.cc.dd (37.192.cc.dd[37.192.cc.dd]): SSH2 session opened.
Mar 13 18:47:02 host.domain.com proftpd[7818] 195.bb.cc.dd (37.192.cc.dd[37.192.cc.dd]): ProFTPD terminating (signal 11)
--
Mar 14 04:05:40 host.domain.com proftpd[13225] 195.bb.cc.dd: received SIGHUP -- master server reparsing configuration file
Mar 14 04:06:10 host.domain.com proftpd[13225] 195.bb.cc.dd: received SIGHUP -- master server reparsing configuration file
[root@host rotated]#
 
Yes, confirmed, as soon as I do:

Code: 
/usr/bin/kill -HUP `cat /var/run/proftpd.pid 2>/dev/null`

ProFTPd (working as sFTP server) stops accepting new connections.
 
To downgrade you need to add

Code: 
proftpd:1.3.4b:0871e0b93c9c3c88ca950b6d9a04aed2

into /usr/local/directadmin/custombuild/versions.txt instead of

Code: 
proftpd:1.3.4c:65f61e953bea249f8377e681594143a5

and run

Code: 
./build proftpd

The version has not the bug mentioned above.

The bug is reported to http://bugs.proftpd.org/show_bug.cgi?id=3918
 
Last edited:
zEitEr said:
And here is a patch: http://bugs.proftpd.org/attachment.cgi?id=3973
Click to expand...

Hi Alex,

Many thanks your investigation I was experiencing the exact same problem and was going crazy trying to find out what was causing it. My sFTP connection would also stop working after about 8 hours, a restart of the proftpd daemon solved it but only temporary until the same problem occurred again, I'll apply this patch to fix the issue properly.

Edit: Here's my way of patching and installing on CentOS 6.4:

1. Decompress the proftpd-1.3.4c.tar.gz at /usr/local/directadmin/custombuild:

Code: 
tar zxf proftpd-1.3.4c.tar.gz

2. You'll then have a folder called proftpd-1.3.4c within the custombuild folder. Switch into it:

Code: 
cd proftpd-1.3.4c

3. Run the patch file with:

Code: 
patch -p0 < /path/to/patchfile

It will fail on a couple of lines, but they are non issues and won't affect anything.

4. Now run ./configure but make sure you use these properties. These are the paths for CentOS/Redhat for FreeBSD and other you may have to modify them:

Code: 
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var/run --mandir=/usr/share/man --without-pam --disable-auth-pam --enable-nls --with-modules=mod_ratio:mod_readme:mod_sftp

5. Now compile and install the patched version of ProFTPD 1.3.4c with the SFTP fixes:

Code: 
make & make install

6. Finally restart ProFTPD with:

Code: 
service proftpd restart

Use the variant for restarting daemons applicable to your Server OS if your not running Redhat/CentOS

You should be now running the patched version ProFTPD 1.3.4c. Connect to SFTP with a FTP client to first confirm SFTP is working, and to finally confirm the patch is working run:

Code: 
/usr/bin/kill -HUP `cat /var/run/proftpd.pid 2>/dev/null`

Now try and reconnect to the SFTP. You should be able to connect again with no problems. (The broken 1.3.4c binaries would stop allowing SFTP connections at this point).

Hope this helps.
 
Last edited:
Thank you for your input. It would be nice if DA team apply the patch to the distro they host on their servers. So we could install patched ProFTPd without need to patch it extra.
 
Silly question. I am having problem running
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var/run --mandir=/usr/share/man --without-pam --disable-auth-pam --enable-nls --with-modules=mod_ratio:mod_readme:mod_sftp
Click to expand...

As in I am running it from the wrong place (custombuild) because I'm getting the error
-bash: ./configure: is a directory
Click to expand...
 
Code: 
cd /usr/local/directadmin/custombuild/proftpd-1.3.4c

patch it and run

Code: 
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var/run --mandir=/usr/share/man --without-pam --disable-auth-pam --enable-nls --with-modules=mod_ratio:mod_readme:mod_sftp
 
You must log in or register to reply here.
Back
Top