<?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: sas-cachelocator returns code 404 in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584317#M17058</link>
    <description>&lt;P&gt;Already done.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Aug 2019 18:11:54 GMT</pubDate>
    <dc:creator>dramage</dc:creator>
    <dc:date>2019-08-27T18:11:54Z</dc:date>
    <item>
      <title>sas-cachelocator returns code 404</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584309#M17056</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Earlier today we began to have issues with our Viya machine.&amp;nbsp; After some investigation it turns out that the problem is with the cachelocator service.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm seeing this in /opt/sas/viya/config/var/log/cachelocator/default/sas-cachelocator_2019-08-27_15-59-47.log over and over again:&lt;/P&gt;&lt;P&gt;2019-08-27 17:09:37.518 INFO 28950 --- [09:37.396+0000]] c.s.c.rest.boot.vault.CertificateUtil : service [VAULT_CERTIFICATE_FOUND] Found valid SSL certificate in Vault for: localhost&lt;BR /&gt;2019-08-27 17:09:37.544 WARN 28950 --- [09:37.396+0000]] c.s.c.rest.boot.vault.CertificateUtil : service [TOMCAT_PAUSE] Pausing tomcat to update the SSL configuration.&lt;BR /&gt;2019-08-27 17:09:37.598 WARN 28950 --- [09:37.396+0000]] o.apache.tomcat.util.net.jsse.JSSEUtil : service The trusted certificate with alias [deutschetelekomrootca2] and DN [CN=Deutsche Telekom Root CA 2, OU=T-TeleSec Trust Center, O=Deutsche Telekom AG, C=DE] is not valid due to [NotAfter: Tue Jul 09 23:59:00 UTC 2019]. Certificates signed by this trusted certificate WILL be accepted&lt;BR /&gt;2019-08-27 17:09:37.598 WARN 28950 --- [09:37.396+0000]] o.apache.tomcat.util.net.jsse.JSSEUtil : service The trusted certificate with alias [certplusclass2primaryca] and DN [CN=Class 2 Primary CA, O=Certplus, C=FR] is not valid due to [NotAfter: Sat Jul 06 23:59:59 UTC 2019]. Certificates signed by this trusted certificate WILL be accepted&lt;BR /&gt;2019-08-27 17:09:37.598 INFO 28950 --- [09:37.396+0000]] c.s.c.rest.boot.vault.CertificateUtil : service [TOMCAT_RESUME] Resuming normal tomcat operations after updating SSL configuration.&lt;BR /&gt;2019-08-27 17:09:37.598 INFO 28950 --- [09:37.396+0000]] c.s.c.rest.boot.vault.CertificateUtil : service [SSL_CERTIFICATE_REISSUE] The SSL certificate is scheduled to be reissued at 2019-08-27T17:10:07.598+0000&lt;BR /&gt;2019-08-27 17:09:59.260 WARN 28950 --- [ bootstrap-4] c.s.s.oauth2.bootstrap.ClientRegisterer : service [752d6d96ccb564f3] [HTTP_ERROR] The server returned error status 404 for request to register oauth client sas.cachelocator: 404 Not Found&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance for any help.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2019 17:11:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584309#M17056</guid>
      <dc:creator>dramage</dc:creator>
      <dc:date>2019-08-27T17:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: sas-cachelocator returns code 404</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584316#M17057</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/286876"&gt;@dramage&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Please open a &lt;A href="https://support.sas.com/ctx/supportform/createForm" target="_blank" rel="noopener"&gt;track&lt;/A&gt; and our middle tier technical support will be able to assist you with this problem.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2019 17:59:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584316#M17057</guid>
      <dc:creator>alexal</dc:creator>
      <dc:date>2019-08-27T17:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: sas-cachelocator returns code 404</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584317#M17058</link>
      <description>&lt;P&gt;Already done.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2019 18:11:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584317#M17058</guid>
      <dc:creator>dramage</dc:creator>
      <dc:date>2019-08-27T18:11:54Z</dc:date>
    </item>
    <item>
      <title>Re: sas-cachelocator returns code 404</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584380#M17059</link>
      <description>&lt;P&gt;I resolved this by installing all available SAS updates.&amp;nbsp; The cachelocator package was not one of them, so I guess it was some other package that it depends on.&amp;nbsp; I wish I knew which one it was.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2019 23:06:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/sas-cachelocator-returns-code-404/m-p/584380#M17059</guid>
      <dc:creator>dramage</dc:creator>
      <dc:date>2019-08-27T23:06:37Z</dc:date>
    </item>
  </channel>
</rss>

