[BlueOnyx:16331] Re: Pootle-Patchday Issues II : ProFTPd fixed (sort of)

[Janwillem Ronken]

Hi Michael
I have the same problem on a server running at Chris¹s place.. (VM)

Oct 30 21:46:08 us1 xinetd[4819]: START: ftp pid=5183 from=189.xxx.xxx.xxx
Oct 30 21:46:08 us1 proftpd[5183]: warning: "ProFTPD" address/port
(208.67.xxx.xxx:21) already in use by "ProFTPD server"
Oct 30 21:46:08 us1 proftpd[5183]: 208.67.xxx.xxx - ProFTPD terminating
(signal 11) 
Oct 30 21:46:08 us1 proftpd[5183]: 208.67.xxx.xxx - FTP session closed.
Oct 30 21:46:08 us1 xinetd[4819]: EXIT: ftp status=0 pid=5183
duration=0(sec)

Unable to connect over FTP nor SFTP

Best regards and thanks for all your good work

Janwillem



On 30/10/14 21:27, "Michael Stauber" <mstauber at blueonyx.it> wrote:

>Hi Chris,
>
>> Make that last line:
>> /usr/sbin/swatch
>
>Right.
>
>> Is there another step required to get FTP responding?
>> With the above,
>> I get this result on 4 production boxes (so far):
>> 
>> Connected to web41 (208.77.x.y).
>> 421 Service not available, remote server has closed connection
>
>No, actually the install of the proftpd RPM itself should get the
>service back up. The swatch run is just to turn active monitor green
>right away and not up to 15 minutes later.
>
>Please check /etc/xinetd.d/proftpd and /etc/xinetd.d/proftpds to see if
>"disable = no" is set, which turns FTP on in Xinetd. Or toggle it off/on
>in the GUI.
>
>Other things to check:
>
>/etc/proftpd.conf should have not a single TLS config line.
>/etc/proftpds.conf should have all the usual TLS config lines.
>
>-- 
>With best regards
>
>Michael Stauber
>