<?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>question Re: ambari-agent is not creating pid file in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-agent-is-not-creating-pid-file/m-p/142871#M19614</link>
    <description>&lt;A rel="user" href="https://community.cloudera.com/users/392/rbalam.html" nodeid="392"&gt;@rbalam&lt;/A&gt;&lt;P&gt;you might have a stale pid with wrong permissions. I've seen this before. Delete the pid, check permissions on directory, make sure directory is not mounted as noexec.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Feb 2016 19:08:46 GMT</pubDate>
    <dc:creator>aervits</dc:creator>
    <dc:date>2016-02-16T19:08:46Z</dc:date>
    <item>
      <title>ambari-agent is not creating pid file</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-agent-is-not-creating-pid-file/m-p/142869#M19612</link>
      <description>&lt;P&gt;The agent which is running on ambari-server node is not able to create pid file but when we check the process, the agent process is running in the back ground.However when we check the status using ambari-agent status.. it is reporting as the agent NOT running. The reason is because there is no pid file created when we tried to start the ambari-agent.&lt;/P&gt;&lt;P&gt;Could you please help us identify the reason why it is not create PID file?&lt;/P&gt;&lt;P&gt;We have ambari 2.2.0 running on RH 6.6 and ambari-server and ambari-agent are running as root.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 12:10:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-agent-is-not-creating-pid-file/m-p/142869#M19612</guid>
      <dc:creator>rbalam</dc:creator>
      <dc:date>2016-02-16T12:10:32Z</dc:date>
    </item>
    <item>
      <title>Re: ambari-agent is not creating pid file</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-agent-is-not-creating-pid-file/m-p/142870#M19613</link>
      <description>&lt;P&gt;In /etc/ambari-agent/conf/ambari-agent.ini check an entry called pidlookuppath, the pid file will be written there. The path is usually /var/run/ and ambari-agent will create a directory there called, predictably, ambari-agent. Create that directory if it doesn't exist and try to restart the agent. Also check permissions, those of directories should be 755, and ownership root:root if you run the agent as root.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 13:02:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-agent-is-not-creating-pid-file/m-p/142870#M19613</guid>
      <dc:creator>pminovic</dc:creator>
      <dc:date>2016-02-16T13:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: ambari-agent is not creating pid file</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-agent-is-not-creating-pid-file/m-p/142871#M19614</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/392/rbalam.html" nodeid="392"&gt;@rbalam&lt;/A&gt;&lt;P&gt;you might have a stale pid with wrong permissions. I've seen this before. Delete the pid, check permissions on directory, make sure directory is not mounted as noexec.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 19:08:46 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-agent-is-not-creating-pid-file/m-p/142871#M19614</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-02-16T19:08:46Z</dc:date>
    </item>
  </channel>
</rss>

