From owner-freebsd-questions@FreeBSD.ORG Mon Jan 9 08:08:17 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10CCC16A41F for ; Mon, 9 Jan 2006 08:08:17 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 653F243D45 for ; Mon, 9 Jan 2006 08:08:15 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-8) with SMTP id k0988CVO030697; Mon, 9 Jan 2006 10:08:13 +0200 Received: by flame.pc (Postfix, from userid 1001) id 8168311825; Mon, 9 Jan 2006 10:06:46 +0200 (EET) Date: Mon, 9 Jan 2006 10:06:46 +0200 From: Giorgos Keramidas To: "Jay O'Brien" Message-ID: <20060109080646.GA25172@flame.pc> References: <43C2146B.4060806@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43C2146B.4060806@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: FTP stopped working X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2006 08:08:17 -0000 On 2006-01-08 23:44, Jay O'Brien wrote: > I'm embarassed to say that FreeBSD was working so good for me > that I forgot how to make it work. It was up for over 300 days > when I rebooted today. Oops :) > All of a sudden I cannot access the computer via ftp. I have > been able to do so using WS_FTP Pro on my Windows CP Pro > computer, but now it doesn't even seem to accept the connect. > The connect is via a local LAN, using fixed IPs. > > Guidance in a troubleshooting mode would really be appreciated. First check that you truly have the ftpd binary: root@flame:/root# ls -l /usr/libexec/ftpd -r-xr-xr-x 1 root wheel 96360 Jan 8 13:00 /usr/libexec/ftpd Then see if ftpd is supposed to start as 'standalone' or as a service controlled by inetd: root@flame:/root# grep ftp /etc/rc.conf root@flame:/root# grep inetd /etc/rc.conf inetd_enable="YES" root@flame:/root# pgrep inet 651 root@flame:/root# grep '^[[:space:]]*ftp' /etc/inetd.conf ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l If inetd is running, pgrep should report its PID as above. Seeing no PID means that inetd failed to start. Your system logs at /var/log/messages will almost certainly have clues about the reason of the failure. Then, start checking if something *is* listening at port 21: root@flame:/root# netstat -na | fgrep LISTEN | grep [:.]21 tcp4 0 0 *.21 *.* LISTEN root@flame:/root# sockstat -4 -l -p 21 USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root inetd 651 5 tcp4 *:21 *:* root@flame:/root# If you don't have any indication how ftpd was started it's possible that you manually fired up ftpd and then promptly forgot about it, until you had to reboot. Stability is nice, isn't it? :)