On Thu, 24 Jul 2003, Mark Stevens wrote:
> Sorry for the HTML message. My first time posting to the list and I guess
> at some point it became the default for Eudora to send HTML e-mails.
>
> I was restarting xinetd just in case. Process of elimination.
>
> Results of Verify:
> S.5....T c /etc/vsftpd.ftpusers
> S.5....T c /etc/vsftpd/vsftpd.conf
> .M...UG. /var/ftp
> .M...UG. /var/ftp/pub
>
> Results of Netstat:
> tcp 0 0
> *:ftp *:* LISTEN 1557/xinetd
>
>
> Ftp user is in /etc/passwd and /etc/shadow
>
> Ftp directory is correct.
>
> Replaced the config file with one straight out of the rpm, unchanged, and
> started the service.
>
> service vsftpd status - vsftpd dead but subsys locked.
>
> This is just crazy. I think I am going to remove the vsftpd and reinstall
> it. Hopefully it will be easy with the rpm manager.
>
> Any other ideas?
Are you sure that /etc/vsftpd/vsftpd.conf has
listen=YES
tcp_wrappers=YES
?
I had a problem similar to yours when I upgraded from RH8's vsftpd to
RH9's. That was the change necessary to get vsftpd to run as a daemon.
> >Date: Wed, 23 Jul 2003 19:00:49 +0200
> >From: Michael Schwendt <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: Re: vsftpd dead but subsys locked
> >Reply-To: [EMAIL PROTECTED]
> >
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >On Wed, 23 Jul 2003 08:55:08 -0500, Mark Stevens wrote:
> >
> > > I am running vsftpd on a RedHat 9.0 professional server.
> > >
> > > Following 'service vsftpd status' i get "vsftpd dead but subsys locked"
> >
> >Normally, I won't reply to HTML messages since they are automatically
> >moved to my trash folder or even to /dev/null. So in case you reply
> >with HTML, it is likely that I won't see your reply.
> >
> > > The server was working fine. Monday morning at 7:30am files were uploaded
> > > to the server. At 8am we rebooted the server. After the restart the error
> > > started.
> > >
> > > I have posted to linuxquestions.org, sent an e-mail to chris at
> > beasts.org,
> > > spoken with RedHat tech support. No luck so far.
> > >
> > > Here is what I have tried to date:
> > > Restart vsftpd
> > > Restart xinetd
> >
> >Why restart xinetd? In Red Hat Linux 9 vsftpd runs as a standalone
> >daemon.
> >
> > > check all log files, nothing of notice on failure
> > > check config file. config file never changed and replaced with a back up
> > > copy (I have two of every config file)
> > >
> > > Please can't someone help me?
> >
> >First of all, verify the vsftpd package integrity:
> >
> > rpm --verify vsftpd
> >
> >Then stop the service:
> >
> > service vsftpd stop
> >
> >Look if the ftp port is free:
> >
> > netstat -tpa | grep ftp
> >
> >Verify that you have user "ftp" in /etc/passwd (and /etc/shadow).
> >Verify ftp's home directory.
> >
> >Then -- although you write you've done this already -- start with a
> >config file that is known to be 100% error-free. Simple mistakes
> >like a coment '#' removed from the beginning of a comment-line can
> >be enough to confuse vsftpd.
> >
> > service vsftpd start
> >
> >What do you get?
>
>
>
>
--
Matthew Saltzman
Clemson University Math Sciences
[EMAIL PROTECTED]
http://www.math.clemson.edu/~mjs
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
