<?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/3493493#M16443</link>
    <description>Well, for one I don't think your vsftpd is even starting.&lt;BR /&gt;What happens when you type:&lt;BR /&gt;/etc/init.d/vsftpd status after you start it?&lt;BR /&gt;&lt;BR /&gt;My guess you will get the locked message.&lt;BR /&gt;&lt;BR /&gt;I had this same problem with snmpd and it was due to having a "faulty" line in my /etc/snmp/snmp.conf line, so you may want to look at /etc/vsftpd/vsftpd.conf file first.</description>
    <pubDate>Fri, 25 Feb 2005 15:09:07 GMT</pubDate>
    <dc:creator>TJ_16</dc:creator>
    <dc:date>2005-02-25T15:09:07Z</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/3493492#M16442</link>
      <description>Hi All&lt;BR /&gt;&lt;BR /&gt;When I try to stop the vsftpd service, executing "service vsftpd stop" the output command is :&lt;BR /&gt;NOT OK and  "vsftpd dead but subsys locked"&lt;BR /&gt;&lt;BR /&gt;Starting the service all is OK.&lt;BR /&gt;&lt;BR /&gt;Seeing the /etc/init.d/vsftpd file , I see that when the stop call run properly ($?=0) execute a a "rm /var/lock/subsys/vsftp".&lt;BR /&gt;&lt;BR /&gt;I have deleted the file manually , but the error continous.&lt;BR /&gt;&lt;BR /&gt;Do you have any idea about it?&lt;BR /&gt;&lt;BR /&gt;Linux version: Enterprise Linux AS release 3 &lt;BR /&gt;&lt;BR /&gt;Thanks for your help&lt;BR /&gt;&lt;BR /&gt;Harstad</description>
      <pubDate>Fri, 25 Feb 2005 07:35:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3493492#M16442</guid>
      <dc:creator>Harstad_1</dc:creator>
      <dc:date>2005-02-25T07:35: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/3493493#M16443</link>
      <description>Well, for one I don't think your vsftpd is even starting.&lt;BR /&gt;What happens when you type:&lt;BR /&gt;/etc/init.d/vsftpd status after you start it?&lt;BR /&gt;&lt;BR /&gt;My guess you will get the locked message.&lt;BR /&gt;&lt;BR /&gt;I had this same problem with snmpd and it was due to having a "faulty" line in my /etc/snmp/snmp.conf line, so you may want to look at /etc/vsftpd/vsftpd.conf file first.</description>
      <pubDate>Fri, 25 Feb 2005 15:09:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3493493#M16443</guid>
      <dc:creator>TJ_16</dc:creator>
      <dc:date>2005-02-25T15:09:07Z</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/3493494#M16444</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Firstable, thanks for your answer.&lt;BR /&gt;&lt;BR /&gt;I have checked the vsftpd.conf file and all seems OK. Comparing this file with the same in other server is equal&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Harstad</description>
      <pubDate>Wed, 02 Mar 2005 07:43:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3493494#M16444</guid>
      <dc:creator>Harstad_1</dc:creator>
      <dc:date>2005-03-02T07:43:57Z</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/3493495#M16445</link>
      <description>I had a similar problem and noticed that an entry in /etc/sysconfig/network was wrong. It specified:&lt;BR /&gt;&lt;BR /&gt;GATEWAY=&lt;THE ip="" of="" eth0=""&gt; &lt;BR /&gt;&lt;BR /&gt;when it should have specified: &lt;BR /&gt;&lt;BR /&gt;GATEWAY=&lt;THE ip="" of="" the="" default="" gateway=""&gt;. &lt;BR /&gt;&lt;BR /&gt;When I changed it and rebooted, vsftpd came up OK and seems to be working fine.&lt;/THE&gt;&lt;/THE&gt;</description>
      <pubDate>Wed, 09 Mar 2005 15:15:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3493495#M16445</guid>
      <dc:creator>Greg_237</dc:creator>
      <dc:date>2005-03-09T15:15:55Z</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/3493496#M16446</link>
      <description>The vspftd service has died prior to your attempt to stop it.&lt;BR /&gt;&lt;BR /&gt;This is caused by a number of factors, including problems not related to vsftpd.&lt;BR /&gt;&lt;BR /&gt;I would suggest using yum or up2date to get the latest version of vsfptd installed.&lt;BR /&gt;&lt;BR /&gt;This daemon has a log file which may give a clue as to why its dying. There are DOS type attacks or too many malicious user situations which may bring this condition about.&lt;BR /&gt;&lt;BR /&gt;There may be a clue in /var/log/messages as well.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 09 Mar 2005 15:20:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3493496#M16446</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-03-09T15:20:08Z</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/3493497#M16447</link>
      <description>I've just managed to fix the problem on FC 4.&lt;BR /&gt;I had made changes to vsftpd.conf to disable anonymous access. On using "service vsftpd start" and "service vsftpd status", Iwould get "vsftpd dead but subsys locked".&lt;BR /&gt;&lt;BR /&gt;I first went into /etc/vsftpd/ and undid all changes. Ona hunch I also deleted all excess recovery confs like vsftpd.conf~ and vsftpd.conf- created by the editors used. I then removed the /var/lock/subsys/vsftpd file.&lt;BR /&gt;&lt;BR /&gt;"service vsftpd stop", "service vsftpd start" and "service vsftpd status" now give the expected output.&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Feb 2006 01:52:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3493497#M16447</guid>
      <dc:creator>betasummerkamp</dc:creator>
      <dc:date>2006-02-21T01:52:52Z</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/3493498#M16448</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;You could try deleting the /var/run/vsftpd  pid file and try and you will get the expected results.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Feb 2006 04:56:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vsftpd-dead-but-subsys-locked/m-p/3493498#M16448</guid>
      <dc:creator>Vipulinux</dc:creator>
      <dc:date>2006-02-21T04:56:49Z</dc:date>
    </item>
  </channel>
</rss>

