Colin,
Could this be a Passive FTP problem? we found (because of the firewall
we are using) that we had to specify the PASV port range in the /etc/
proftpd.conf file because we didn't want to allow external connections
on everything from 49152 to 65535... and in our infinite wisdom, the
first time we did this, the firewall got configured first. Suddenly
file transfers were being rejected all over the place... but only
about 2/3 of them. It took a while to figure out what happened because
the connection problems were escalated and the port change was put on
hold (so much for the operation plan...). Anyway once we took a step
back and remembered... oh yeah...
Greg
On Mar 19, 2009, at 5:31 am, Colin Jack wrote:
> Not thinking - of course trying to stop and start the service won't
> work if it is run from inetd.
>
> The service is running - it allows logon but every now and then
> doesn't allow putting or getting files :(
>
> Colin
>
>
>> -----Original Message-----
>> From: Larry Smith [mailto:lesmith (at mark) ecsis.net]
>> Sent: Wednesday, March 18, 2009 11:24 PM
>> To: coba-e (at mark) bluequartz.org
>> Subject: [coba-e:15356] Re: Re Broken FTP
>>
>> On Wed March 18 2009 18:14, Colin Jack wrote:
>>> And this ...
>>>
>>> [root@server7 log]# service proftpd restart
>>> Shutting down proftpd: [FAILED]
>>> Starting proftpd: [FAILED]
>>> [root@server7 log]# service proftpd restart
>>> Shutting down proftpd: [FAILED]
>>> Starting proftpd: [FAILED]
>>> [root (at mark) server7 log]# /usr/sbin/swatch -c /etc/swatch.conf
>>> [root@server7 log]#
>>
>> Interesting, on my server proftpd is run from inetd (xinetd) and
>> not from the config (chkconfig --list proftpd shows OFF for all
>> columns)
>> and mine is working fine.
>>
>> Check under /etc/xinetd.d for file proftpd and see if parameter
>> disable = no
>>
>> If so, service proftpd stop, and then try testing again, you may have
>> been trying to bring up multiple copies.
>>
>> --
>> Larry Smith
>> lesmith (at mark) ecsis.net
>>
>
>