<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: vsftpd dead but subsys locked in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921871#M26546</link>
    <description>just remove the following file&lt;BR /&gt;&lt;BR /&gt;/var/locl/subsys/vsftpd&lt;BR /&gt;&lt;BR /&gt;and then restart vsftpd</description>
    <pubDate>Mon, 08 Jan 2007 14:37:47 GMT</pubDate>
    <dc:creator>George Liu_4</dc:creator>
    <dc:date>2007-01-08T14:37:47Z</dc:date>
    <item>
      <title>vsftpd dead but subsys locked</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921867#M26542</link>
      <description>I am facing problem in vsftp server. I'm working on RHEL4 server. the vsftpd service was working fine but now suddenly I found&lt;BR /&gt;that it is not working. Whenever I restart or stop the service I'm getting following messages.&lt;BR /&gt;&lt;BR /&gt;1. Service vsftpd status&lt;BR /&gt;&lt;BR /&gt;Vsftpd dead but subsys locked&lt;BR /&gt;&lt;BR /&gt;2. Service vsftpd stop &lt;BR /&gt;&lt;BR /&gt;Shutting Down vsftpd: [Failed]&lt;BR /&gt;&lt;BR /&gt;3. Service vsftpd start&lt;BR /&gt;&lt;BR /&gt;Starting vsftpd for vsftpd: [ok]&lt;BR /&gt;&lt;BR /&gt;4.Service vsftpd status&lt;BR /&gt;&lt;BR /&gt;Vsftpd dead but subsys locked&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Kindly suggest....what can be done so that the vsftpd service work properly&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 06 Jan 2007 12:20:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921867#M26542</guid>
      <dc:creator>Muhammad Shamroze</dc:creator>
      <dc:date>2007-01-06T12:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd dead but subsys locked</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921868#M26543</link>
      <description>By default vsftpd runs from xinetd. &lt;BR /&gt;Try to stop the xinetd and to restart the vsftpd service.</description>
      <pubDate>Sat, 06 Jan 2007 12:42:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921868#M26543</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2007-01-06T12:42:02Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd dead but subsys locked</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921869#M26544</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Many deamons have a lock file in /var/run&lt;BR /&gt;&lt;BR /&gt;This message indicates that vsftpd did not terminate normally, but did terminate.&lt;BR /&gt;&lt;BR /&gt;Erase the lock file and it will restart.&lt;BR /&gt;&lt;BR /&gt;vsftpd is not run with xinetd unless you specifically altered its configuration. Contrary to wu-ftpd, it has its own configuration file and independent daemon infrastructure.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 07 Jan 2007 05:51:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921869#M26544</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-01-07T05:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd dead but subsys locked</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921870#M26545</link>
      <description>Run:&lt;BR /&gt;&lt;BR /&gt;service vsftpd stop&lt;BR /&gt;service vsftpd start&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;And just after that, check /var/log/messages. You probably have a problem in your configuration file. Error should be reported to that file.&lt;BR /&gt;&lt;BR /&gt;Or run:&lt;BR /&gt;&lt;BR /&gt;service vsftpd stop&lt;BR /&gt;vsftpd&lt;BR /&gt;&lt;BR /&gt;This will start the daemon manually and any errors you will get to your terminal, like this:&lt;BR /&gt;&lt;BR /&gt;500 OOPS: missing value in config file for: &lt;BR /&gt;&lt;BR /&gt;You must be aware that all configuration options in the vsftpd.conf file must not start with a space, for example:&lt;BR /&gt;&lt;BR /&gt;- Correct&lt;BR /&gt;anonymous_enable=YES&lt;BR /&gt;&lt;BR /&gt;- Incorrect&lt;BR /&gt;&lt;SPACE&gt;anonymous_enable=YES&lt;BR /&gt;&lt;BR /&gt;If you have an space in your configuration file before the config options, you will get an error.&lt;/SPACE&gt;</description>
      <pubDate>Mon, 08 Jan 2007 09:00:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921870#M26545</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-01-08T09:00:03Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd dead but subsys locked</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921871#M26546</link>
      <description>just remove the following file&lt;BR /&gt;&lt;BR /&gt;/var/locl/subsys/vsftpd&lt;BR /&gt;&lt;BR /&gt;and then restart vsftpd</description>
      <pubDate>Mon, 08 Jan 2007 14:37:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3921871#M26546</guid>
      <dc:creator>George Liu_4</dc:creator>
      <dc:date>2007-01-08T14:37:47Z</dc:date>
    </item>
  </channel>
</rss>

