<?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: Universal forwarder adds -root to servername? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60781#M12093</link>
    <description>&lt;P&gt;Sorry, no answer, just want to add the fact this is a problem in certain environments where a deployment server is used as it should be to deploy clients. We initially deployed manually (no deployment server) and would remove the [default] host = computer name from the /etc/local/inputs.conf. This resulted in the host name being the FQDN...perfect. Now we are trying to migrate to the new Universal Forwarders using a deployment server, a test run on one host worked great with the exception that it now has a capitalized computer name in Splunk...so now I have two host names for the same box. I understand I can put [default] host = fqdn in the inputs.conf, but that defeats the purpose of a deployment server, I basically need an entry for every device (&amp;gt;300) in my serverclass.conf&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jun 2011 15:33:29 GMT</pubDate>
    <dc:creator>kevins1112</dc:creator>
    <dc:date>2011-06-08T15:33:29Z</dc:date>
    <item>
      <title>Universal forwarder adds -root to servername?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60777#M12089</link>
      <description>&lt;P&gt;As I don't know if this is a bug or intended I'll try to see if anyone know.&lt;/P&gt;

&lt;P&gt;When doing a new install of the universal forwarder the servername adds a -root for some specific reason.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[root@splunktest opt]# rpm -i splunkforwarder-4.2-96430-linux-2.6-x86_64.rpm

[root@splunktest opt]# /opt/splunkforwarder/bin/splunk start --accept-license

[root@splunktest opt]# /opt/splunkforwarder/bin/splunk show servername
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Server name: splunktest.domain.com*&lt;EM&gt;-root&lt;/EM&gt;*&lt;/P&gt;

&lt;P&gt;Looks kinda weird since all my old 4.1.7 forwarders don't append -root to their servernames.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Mar 2011 22:34:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60777#M12089</guid>
      <dc:creator>drohr</dc:creator>
      <dc:date>2011-03-16T22:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder adds -root to servername?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60778#M12090</link>
      <description>&lt;P&gt;Note: the same on Solaris10 x86&lt;/P&gt;</description>
      <pubDate>Thu, 17 Mar 2011 01:27:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60778#M12090</guid>
      <dc:creator>LCM</dc:creator>
      <dc:date>2011-03-17T01:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder adds -root to servername?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60779#M12091</link>
      <description>&lt;P&gt;The variable in etc/system/default/server.conf has always been $HOSTNAME-$USERNAME or whatever like that.&lt;/P&gt;

&lt;P&gt;Usually this has never mattered, because it got set to servername in install in so-called "first time run.&lt;/P&gt;

&lt;P&gt;However, there was a goal to do mass rollouts of the Universal Forwarder with no config tweaks at all, pre-installed etc, so you are now seeing these variable expansions take place.&lt;/P&gt;

&lt;P&gt;I was never sure of the goal of having $USER in there.  I suspect it was for development purposes at HQ.  If it causes any operational difficulties/annoyances we should get a bug or at least a ticket filed to discuss.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Mar 2011 15:26:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60779#M12091</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2011-03-18T15:26:43Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder adds -root to servername?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60780#M12092</link>
      <description>&lt;P&gt;As Josh said, Splunk will default to hostname-username if &lt;CODE&gt;serverName&lt;/CODE&gt; is not set in &lt;CODE&gt;server.conf&lt;/CODE&gt;. The difference in 4.2 is that Splunk now doesn't query &lt;CODE&gt;hostname&lt;/CODE&gt; on first boot (to set this variable to just the hostname) like 4.1.x did. Look in &lt;CODE&gt;etc/system/local/server.conf&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;As a result, any server upgraded from 4.1.x will have just its hostname, any new install of 4.2.x will default to hostname-username.&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2011 17:37:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60780#M12092</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2011-05-12T17:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarder adds -root to servername?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60781#M12093</link>
      <description>&lt;P&gt;Sorry, no answer, just want to add the fact this is a problem in certain environments where a deployment server is used as it should be to deploy clients. We initially deployed manually (no deployment server) and would remove the [default] host = computer name from the /etc/local/inputs.conf. This resulted in the host name being the FQDN...perfect. Now we are trying to migrate to the new Universal Forwarders using a deployment server, a test run on one host worked great with the exception that it now has a capitalized computer name in Splunk...so now I have two host names for the same box. I understand I can put [default] host = fqdn in the inputs.conf, but that defeats the purpose of a deployment server, I basically need an entry for every device (&amp;gt;300) in my serverclass.conf&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2011 15:33:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarder-adds-root-to-servername/m-p/60781#M12093</guid>
      <dc:creator>kevins1112</dc:creator>
      <dc:date>2011-06-08T15:33:29Z</dc:date>
    </item>
  </channel>
</rss>

