<?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: sc4s failed unauthorized access in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700337#M115982</link>
    <description>&lt;P&gt;Yes, I used that image but it still didn't work. Thanks for sharing the documentation.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Sep 2024 14:08:48 GMT</pubDate>
    <dc:creator>mayvisible</dc:creator>
    <dc:date>2024-09-27T14:08:48Z</dc:date>
    <item>
      <title>sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700097#M115948</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;I am not Splunk engineer but I have task to do.&amp;nbsp;sc4s.service is failed. Can't get the logs. It was working before.&amp;nbsp;&lt;/P&gt;&lt;P&gt;As an error it says 'Unauthorized access'. But I don't have any credentials for that.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Environment="SC4S_IMAGE=docker.io/splunk/scs:latest"&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you help me please how to fix it?&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 14:25:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700097#M115948</guid>
      <dc:creator>mayvisible</dc:creator>
      <dc:date>2024-09-25T14:25:45Z</dc:date>
    </item>
    <item>
      <title>Re: sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700142#M115951</link>
      <description>&lt;P&gt;At first glance it does not seem that that SC4S_IMAGE exists or is accessible. If you try to docker pull it, it says it either does not exist or needs credentials.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you check the journalctl logs for the service to see if there are errors or notes around that error which would add context to it?&lt;/P&gt;&lt;P&gt;sudo journalctl -u sc4s.service&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 20:58:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700142#M115951</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-09-25T20:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700220#M115968</link>
      <description>&lt;P&gt;Hi Marnall,&lt;/P&gt;&lt;P&gt;Thanks for your response. Former employee configures the sc4s. So I don't have any credentials for that. Here are the journalctl logs:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;podman[2480968]: Trying to pull docker.io/splunk/scs:latest...&lt;BR /&gt;podman[2480968]: Error: Error initializing source docker://splunk/scs:&amp;gt;&lt;BR /&gt;podman[2480968]: denied: requested access to the resource is denied&lt;BR /&gt;podman[2480968]: unauthorized: authentication required&lt;BR /&gt;systemd[1]: sc4s.service: Control process exited, code=exited status=1&amp;gt;&lt;BR /&gt;systemd[1]: sc4s.service: Failed with result 'exit-code'.&lt;BR /&gt;systemd[1]: Failed to start SC4S Container.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;docker.io/splunk/scs:latest... this is not the same location which is written is Splunk documentation. Even I change it and restart, it is still failed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 13:43:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700220#M115968</guid>
      <dc:creator>mayvisible</dc:creator>
      <dc:date>2024-09-26T13:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700264#M115974</link>
      <description>&lt;P&gt;It appears to be failing to pull the docker image.&lt;/P&gt;&lt;P&gt;This guide for setting up sc4s suggests using a different value for SC4S_IMAGE &lt;A href="https://splunk.github.io/splunk-connect-for-syslog/main/gettingstarted/podman-systemd-general/#unit-file" target="_blank"&gt;https://splunk.github.io/splunk-connect-for-syslog/main/gettingstarted/podman-systemd-general/#unit-file&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Is "ghcr.io/splunk/splunk-connect-for-syslog/container3:latest" the SC4S_IMAGE value you tried?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 19:01:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700264#M115974</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-09-26T19:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700337#M115982</link>
      <description>&lt;P&gt;Yes, I used that image but it still didn't work. Thanks for sharing the documentation.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2024 14:08:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700337#M115982</guid>
      <dc:creator>mayvisible</dc:creator>
      <dc:date>2024-09-27T14:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700444#M115996</link>
      <description>&lt;P&gt;Does it produce different errors than "Unauthorized access" when you use other images?&lt;/P&gt;</description>
      <pubDate>Sat, 28 Sep 2024 19:24:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700444#M115996</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-09-28T19:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700534#M116000</link>
      <description>&lt;P&gt;No, It gave the same error&amp;nbsp;&lt;SPAN&gt;"Unauthorized access"&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 12:47:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/700534#M116000</guid>
      <dc:creator>mayvisible</dc:creator>
      <dc:date>2024-09-30T12:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: sc4s failed unauthorized access</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/701457#M116082</link>
      <description>&lt;P&gt;Perhaps you could try remaking the sc4s using the official guide. It may take less time than trying to debug the current instance.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 19:13:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/sc4s-failed-unauthorized-access/m-p/701457#M116082</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-10-09T19:13:41Z</dc:date>
    </item>
  </channel>
</rss>

