Index: [Article Count Order] [Thread]

Date:  Wed, 18 Mar 2009 23:11:20 +0000
From:  "Colin Jack" <colin (at mark) mainline.co.uk>
Subject:  [coba-e:15354] Re: Re  Broken FTP
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <45DACA7BE1DEA245AF6C95E5B94E531B0E944A81B6 (at mark) datastore.mainline.local>
In-Reply-To:  <8CF48C7B-5D21-4D63-919E-B2080F072EDD (at mark) alpha.or.jp>
References:  <45DACA7BE1DEA245AF6C95E5B94E531B0D07A62D72 (at mark) datastore.mainline.local> <49BF9787.5030804 (at mark) virtbiz.com> <45DACA7BE1DEA245AF6C95E5B94E531B0D07A62D82 (at mark) datastore.mainline.local> <85B65413FDF8424CA9ABEEB812CF36D7 (at mark) raqware> <45DACA7BE1DEA245AF6C95E5B94E531B0D07A62D99 (at mark) datastore.mainline.local> <8CF48C7B-5D21-4D63-919E-B2080F072EDD (at mark) alpha.or.jp>
X-Mail-Count: 15354

Is this of any use?

/var/log/messages:

Mar 18 23:07:46 localhost xinetd[32455]: START: ftp pid=13123 from=87.127.93.250
Mar 18 23:07:46 localhost proftpd[13123]: warning: "ProFTPD" address/port (192.168.10.150:21) already in use by "ProFTPD server"
Mar 18 23:07:46 localhost proftpd[13123]: server7.mainline.co.uk (87.127.93.250[87.127.93.250]) - FTP session opened.
Mar 18 23:07:47 localhost proftpd[13123]: server7.mainline.co.uk (87.127.93.250[87.127.93.250]) - FTP session closed.
Mar 18 23:07:47 localhost xinetd[32455]: EXIT: ftp status=0 pid=13123 duration=1(sec)
Mar 18 23:07:52 localhost xinetd[32455]: START: ftp pid=13126 from=87.127.93.250
Mar 18 23:07:52 localhost proftpd[13126]: warning: "ProFTPD" address/port (192.168.10.150:21) already in use by "ProFTPD server"
Mar 18 23:07:52 localhost proftpd[13126]: server7.mainline.co.uk (87.127.93.250[87.127.93.250]) - FTP session opened.
Mar 18 23:08:24 localhost xinetd[32455]: EXIT: ftp status=0 pid=13126 duration=32(sec)
Mar 18 23:08:24 localhost xinetd[32455]: START: ftp pid=13132 from=87.127.93.250
Mar 18 23:08:24 localhost proftpd[13132]: warning: "ProFTPD" address/port (192.168.10.150:21) already in use by "ProFTPD server"
Mar 18 23:08:24 localhost proftpd[13132]: server7.mainline.co.uk (87.127.93.250[87.127.93.250]) - FTP session opened.
Mar 18 23:08:47 localhost xinetd[32455]: EXIT: ftp status=0 pid=13132 duration=23(sec)

Colin


-----Original Message-----
From: Hisao SHIBUYA [mailto:shibuya (at mark) alpha.or.jp] 
Sent: 18 March 2009 03:53
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:15351] Re: Re Broken FTP

Hi Colin,

Could you try to execute '/usr/sbin/swatch -c /etc/swatch.conf'.
This will check all services, if some check script will be waiting
for time out for a long time.
It maybe some error will be occurred.

Regards,
Hisao


On Mar 18, 2009, at 2:18 AM, Colin Jack wrote:

>>> Absolutely nothing has changed other than the yum update which  
>>> updated
>>> ProFTPD.
>>> The servers are colocoed at two different data centres.
>>>
>>> Nope nothing untoward in the logs.
>>
>> Look at /usr/sausalito/swatch/bin/am_ftp.exp
>> And try to run the telnet commands manually and see if you get  
>> errors.
>>   telnet localhost 21
>> Then expect response;
>>  "Connected to"
>> Then expect response;
>>  "220 "
>> Then send;
>>  QUIT or quit
>> Then expect response;
>>  "221 "
>> This should all work.
>> Then execute;
>>   swatch | cat /var/log/messages | grep cced | grep ftp
>>
>> We have found that several servers we configured and updated give  
>> 'Active
>> Monitor' errors, but FTP is actually working.
>> It may be a timeout issue. Strangely, the Stongbolt servers did not  
>> have
>> this issue.
>>
>> Gerald
>
> The FTP is definitely stopping, because I get the phone calls :)
>
> It is only for a short while and then kicks in again. It was only  
> one server that had the problem but yesterday and today we are  
> seeing it on others.
>
> I need to 'catch' it when it is down and see what is and isn't  
> running and what I can find in the logs.
>
> Thanks for the input - I will let you know how I get on.
>
> Colin
>
>
>
>