<?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: PYTHONHTTPSVERIFY in Installation</title>
    <link>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649648#M13053</link>
    <description>&lt;P&gt;To change Splunk to run as user 'splunk' follow these steps.&lt;/P&gt;&lt;P&gt;1) Stop Splunk&lt;/P&gt;&lt;P&gt;2) Edit the init.d or splunk.service file to set the user to be 'splunk'&lt;/P&gt;&lt;P&gt;For init.d, use command like these:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;USER=splunk
...
splunk_start() {
  echo Starting Splunk...
  su - ${USER} -c '"/opt/splunk/bin/splunk" start --no-prompt --answer-yes'
  RETVAL=$?
  [ $RETVAL -eq 0 ] &amp;amp;&amp;amp; touch /var/lock/subsys/splunk
}&lt;/LI-CODE&gt;&lt;P&gt;3) Change the ownership of all files in $SPLUNK_HOME to 'splunk'&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;chown -r splunk:splunk /opt/splunk&lt;/LI-CODE&gt;&lt;P&gt;4) Start Splunk&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jul 2023 15:27:37 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-07-07T15:27:37Z</dc:date>
    <item>
      <title>PYTHONHTTPSVERIFY</title>
      <link>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649633#M13050</link>
      <description>&lt;P&gt;hi Expert Splunkers,&lt;/P&gt;&lt;P&gt;really appriciate if you take a look at bottom.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;splunkforwarder running on UBUNTU&lt;/P&gt;&lt;P&gt;Warning: Attempting to revert the SPLUNK_HOME ownership&lt;BR /&gt;Warning: Executing "chown -R root /opt/splunkforwarder"&lt;/P&gt;&lt;P&gt;Splunk&amp;gt; Now with more code!&lt;/P&gt;&lt;P&gt;Checking prerequisites...&lt;BR /&gt;Management port has been set disabled; cli support for this configuratio n is currently incomplete.&lt;BR /&gt;Checking conf files for problems...&lt;BR /&gt;Invalid key in stanza [webhook] in /opt/splunkforwarder/etc/syst em/default/alert_actions.conf, line 229: enable_allowlist (value: false).&lt;BR /&gt;Your indexes and inputs configurations are not internally consis tent. For more information, run 'splunk btool check --debug'&lt;BR /&gt;Done&lt;BR /&gt;Checking default conf files for edits...&lt;BR /&gt;Validating installed files against hashes from '/opt/splunkforwarder/spl unkforwarder-9.0.5-e9494146ae5c-linux-2.6-x86_64-manifest'&lt;BR /&gt;All installed files intact.&lt;BR /&gt;Done&lt;BR /&gt;All preliminary checks passed.&lt;/P&gt;&lt;P&gt;Starting splunk server daemon (splunkd)...&lt;BR /&gt;PYTHONHTTPSVERIFY is set to 0 in splunk-launch.conf disabling certificate valida tion for the httplib and urllib libraries shipped with the embedded Python inter preter; must be set to "1" for increased security&lt;BR /&gt;Done&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. installed splunk with root user&lt;/P&gt;&lt;P&gt;2. keep on getting that lines at the end start with PYTHONHTTPSVERIFY (first time seeing it)&lt;/P&gt;&lt;P&gt;3. inputs issue can be ignored.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 13:32:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649633#M13050</guid>
      <dc:creator>yohhpark</dc:creator>
      <dc:date>2023-07-07T13:32:12Z</dc:date>
    </item>
    <item>
      <title>Re: PYTHONHTTPSVERIFY</title>
      <link>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649637#M13051</link>
      <description>&lt;P&gt;1. Running Splunk as root is not advised for security reasons.&lt;/P&gt;&lt;P&gt;2. The PYTHONHTTPSVERIFY warning can be ignored if you're willing to accept the risk.&amp;nbsp; See&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.5/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_Splunk_Python_modules" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.5/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_Splunk_Python_modules&lt;/A&gt;&amp;nbsp;for more information.&amp;nbsp; There is a known issue with enabling this feature so you may want to leave it off for now.&amp;nbsp; See&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.1.0/ReleaseNotes/Knownissues#Authentication_and_authorization_issues" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.1.0/ReleaseNotes/Knownissues#Authentication_and_authorization_issues&lt;/A&gt;&lt;/P&gt;&lt;P&gt;3. What is the "inputs issue"?&lt;/P&gt;&lt;P&gt;Btool is reporting an invalid setting in alert_actions.conf.&amp;nbsp; Verify the "enable_allowlist" setting is correct.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 14:49:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649637#M13051</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-07-07T14:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: PYTHONHTTPSVERIFY</title>
      <link>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649641#M13052</link>
      <description>&lt;P&gt;thank you helps a lot!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;but 1. how can I undo the running on root?&lt;/P&gt;&lt;P&gt;what would be the recommendation?&lt;/P&gt;&lt;P&gt;2. thank you for clarifying those&lt;/P&gt;&lt;P&gt;3. I understand this issue, cthis one can be ignore from our end.&lt;/P&gt;&lt;P&gt;thank you&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 15:04:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649641#M13052</guid>
      <dc:creator>yohhpark</dc:creator>
      <dc:date>2023-07-07T15:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: PYTHONHTTPSVERIFY</title>
      <link>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649648#M13053</link>
      <description>&lt;P&gt;To change Splunk to run as user 'splunk' follow these steps.&lt;/P&gt;&lt;P&gt;1) Stop Splunk&lt;/P&gt;&lt;P&gt;2) Edit the init.d or splunk.service file to set the user to be 'splunk'&lt;/P&gt;&lt;P&gt;For init.d, use command like these:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;USER=splunk
...
splunk_start() {
  echo Starting Splunk...
  su - ${USER} -c '"/opt/splunk/bin/splunk" start --no-prompt --answer-yes'
  RETVAL=$?
  [ $RETVAL -eq 0 ] &amp;amp;&amp;amp; touch /var/lock/subsys/splunk
}&lt;/LI-CODE&gt;&lt;P&gt;3) Change the ownership of all files in $SPLUNK_HOME to 'splunk'&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;chown -r splunk:splunk /opt/splunk&lt;/LI-CODE&gt;&lt;P&gt;4) Start Splunk&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 15:27:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/PYTHONHTTPSVERIFY/m-p/649648#M13053</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-07-07T15:27:37Z</dc:date>
    </item>
  </channel>
</rss>

