<?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: Running splunk on Godaddy CentOS server in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68274#M3631</link>
    <description>&lt;P&gt;Do you think I could install a proxy server or something to access it?&lt;/P&gt;</description>
    <pubDate>Wed, 20 Apr 2011 15:26:25 GMT</pubDate>
    <dc:creator>jamesingham</dc:creator>
    <dc:date>2011-04-20T15:26:25Z</dc:date>
    <item>
      <title>Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68268#M3625</link>
      <description>&lt;P&gt;Hey&lt;/P&gt;

&lt;P&gt;I've got my splunk install running on my godaddy server. When I call &lt;CODE&gt;./splunk start&lt;/CODE&gt; I get a message saying this:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;P&gt;The Splunk web interface is at &lt;A href="http://xxx.secureserver.net:8000" rel="nofollow"&gt;http://xxx.secureserver.net:8000&lt;/A&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;However when I call this it doesn't load, and if I change the port I get a default pageok godaddy page.&lt;/P&gt;

&lt;P&gt;Is there anyway to change the url that splunk loads from? Maybe feeding it into my html folder or something?&lt;/P&gt;

&lt;P&gt;EDIT:&lt;/P&gt;

&lt;P&gt;This is what I get when I call &lt;CODE&gt;./splunk start&lt;/CODE&gt;:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;P&gt;Splunk&amp;gt; Take the sh out of IT.&lt;/P&gt;
  
  &lt;P&gt;Checking prerequisites...&lt;/P&gt;
  
  &lt;P&gt;Checking http port [8000]: open&lt;/P&gt;
  
  &lt;P&gt;Checking mgmt port [8089]: open&lt;/P&gt;
  
  &lt;P&gt;Checking configuration...  Done.&lt;/P&gt;
  
  &lt;P&gt;Checking index directory...&lt;/P&gt;
  
  &lt;P&gt;Validated databases: _audit _blocksignature _internal _thefishbucket history main summary&lt;/P&gt;
  
  &lt;P&gt;Done&lt;/P&gt;
  
  &lt;P&gt;Success&lt;/P&gt;
  
  &lt;P&gt;Checking conf files for typos...&lt;/P&gt;
  
  &lt;P&gt;All preliminary checks passed.&lt;/P&gt;
  
  &lt;P&gt;Starting splunk server daemon (splunkd)... &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;                                                       [  OK  ]

                                                       [  OK  ]
&lt;/CODE&gt;&lt;/PRE&gt;
  
  &lt;P&gt;Done.Starting splunkweb... Done.&lt;/P&gt;
  
  &lt;P&gt;If you get stuck, we're here to help.  &lt;/P&gt;
  
  &lt;P&gt;Look for answers here: &lt;A href="http://www.splunk.com/base/Documentation" rel="nofollow"&gt;http://www.splunk.com/base/Documentation&lt;/A&gt;&lt;/P&gt;
  
  &lt;P&gt;The Splunk web interface is at &lt;A href="http://xxx.secureserver.net:8000" rel="nofollow"&gt;http://xxx.secureserver.net:8000&lt;/A&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;When I say the page doesn't load, I mean it sends the request but just times out.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2011 06:21:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68268#M3625</guid>
      <dc:creator>jamesingham</dc:creator>
      <dc:date>2011-03-26T06:21:59Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68269#M3626</link>
      <description>&lt;P&gt;When it "doesn't load", what precisely happens?  Does it come back immediately, or does it sit for 30-60 seconds and time out?&lt;/P&gt;

&lt;P&gt;The most likely problem is a firewall issue, either on your virtual host or a restriction enforced by GoDaddy. You'd trypically see a delay rather than an immedaite response if that's the case.&lt;/P&gt;

&lt;P&gt;A couple of very generic things to try:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;&lt;P&gt;If it's on the CentOS host, you may need to edit &lt;CODE&gt;/etc/sysconfig/iptables&lt;/CODE&gt; and add a rule to permit access to port 8000.  This &lt;A href="http://www.cyberciti.biz/faq/rhel-fedorta-linux-iptables-firewall-configuration-tutorial/" rel="nofollow"&gt;link&lt;/A&gt; may help.&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;Also, try running &lt;CODE&gt;netstat -an --tcp&lt;/CODE&gt;, and make sure that you see Splunk listening on port 8000.&lt;/P&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Sat, 26 Mar 2011 08:35:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68269#M3626</guid>
      <dc:creator>southeringtonp</dc:creator>
      <dc:date>2011-03-26T08:35:44Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68270#M3627</link>
      <description>&lt;P&gt;If you look at my edit, it appears that the http port is open. I guess I need it listening on TCP as well? When I run netstat the first thing I see is &lt;CODE&gt;tcp  0  0 0.0.0.0:8000   0.0.0.0:*   LISTEN&lt;/CODE&gt; I see this for 8089 as well but nothing else for either port.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2011 18:15:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68270#M3627</guid>
      <dc:creator>jamesingham</dc:creator>
      <dc:date>2011-03-26T18:15:51Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68271#M3628</link>
      <description>&lt;P&gt;Also, in the sysconfig folder (there is no systconfig :/) in /etc, I see no iptables! My linux build is CentOS release 5.2 (Final).&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2011 18:19:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68271#M3628</guid>
      <dc:creator>jamesingham</dc:creator>
      <dc:date>2011-03-26T18:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68272#M3629</link>
      <description>&lt;P&gt;Agree with southeringtonp. It's probably a firewall/iptables setting blocking external access to that port. The port is open as you have noted, but is being blocked by the OS iptables firewall/filter.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2011 23:11:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68272#M3629</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-03-26T23:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68273#M3630</link>
      <description>&lt;P&gt;Sorry, typo. There's no 't' in sysconfig. See edit and additional link above.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Mar 2011 01:47:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68273#M3630</guid>
      <dc:creator>southeringtonp</dc:creator>
      <dc:date>2011-03-29T01:47:28Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68274#M3631</link>
      <description>&lt;P&gt;Do you think I could install a proxy server or something to access it?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Apr 2011 15:26:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68274#M3631</guid>
      <dc:creator>jamesingham</dc:creator>
      <dc:date>2011-04-20T15:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68275#M3632</link>
      <description>&lt;P&gt;I talked to a godaddy representative and he confirmed that they had a security policy blocking access to the 8000 port.  They declined to make an exception to the security policy.&lt;/P&gt;</description>
      <pubDate>Wed, 04 May 2011 18:52:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68275#M3632</guid>
      <dc:creator>perrydc</dc:creator>
      <dc:date>2011-05-04T18:52:25Z</dc:date>
    </item>
    <item>
      <title>Re: Running splunk on Godaddy CentOS server</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68276#M3633</link>
      <description>&lt;P&gt;In that case, have SplunkWeb (port 8000) run on another port by editing web.conf, either in an app or in etc/system/local:&lt;/P&gt;

&lt;P&gt;[settings]&lt;BR /&gt;
httpport=1234&lt;/P&gt;

&lt;P&gt;(change to represent port you wish to use)&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2012 14:12:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Running-splunk-on-Godaddy-CentOS-server/m-p/68276#M3633</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2012-09-21T14:12:40Z</dc:date>
    </item>
  </channel>
</rss>

