Hi people ,
I have been running through some configurations for vsftpd and I am unable
to stop and restart vsftpd so that the new configurations can take affect.
When I go to stop it , it comes up with the error message of "Failed" to
stop and if I do a service status query on vsftpd it comes up with the
message.
vsftpd dead and locked by subsys.

When I go to check /var/lock/subsys , I find that there is a lock file for
vsftpd and if I remove it , the thing comes back every time I issue a
service vsfpd command.
Does anybody know what could be the problem and how do I get to stop vsftpd
so that I can restart it again.

Thanks.



--
----------------------------------------------------------------------------
--------------------------------------
True Multitasking is having three computers and a chair with wheels.


Sandgroper
------------------------------------
Remove KNICKERS to Email
steveray@KNICKERSiinet.net.au

[ Post a follow-up to this message ]

"Sandgroper" <steveray@KNICKERSiinet.net.au> skrev i en meddelelse
news:454f7b8d$0$3025$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
> Hi people ,
> I have been running through some configurations for vsftpd and I am unable
> to stop and restart vsftpd so that the new configurations can take affect.
> When I go to stop it , it comes up with the error message of "Failed" to
> stop and if I do a service status query on vsftpd it comes up with the
> message.
> vsftpd dead and locked by subsys.
>
> When I go to check /var/lock/subsys , I find that there is a lock file for
> vsftpd and if I remove it , the thing comes back every time I issue a
> service vsfpd command.
> Does anybody know what could be the problem and how do I get to stop
> vsftpd so that I can restart it again.
>

I've had that same problem a few times, with that vsftpd reports "vsftpd
dead and locked by subsys"... It has always been a configuration error in
the vsftpd.conf file, that has been the problem for me. Ex.. there is a
whitespace after a setting... like
anonymous_enable=NO WHITESPACE HERE...

There cant be any whitespaces after the NO or YES option. I've also had the
problem, with my SSL certificate because I'd moved the vsftpd.pem file to
another dir, but forgot to update the configuration file.

So re-check your vsftpd.conf file for whitespaces and spelling-errors.

Regards Jacob

[ Post a follow-up to this message ]