<?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 Why is the AIM started task going down with &amp;quot;CEE5230S The signal SIGXCPU was received&amp;quot;? in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330253#M591</link>
    <description>&lt;P&gt;This is a completely new install and users have just started using it.  It has very limited use at the moment, so some times it takes a while to even notice it's down (that's another issue that we're addressing).  We're currently using v9.5.5.  Short of setting TIME=NOLIMIT in the started task PROC, is there a configuration parameter I can change?  I haven't been able to find anything in the documentation.  Any help would be appreciated.  Thanks!  &lt;/P&gt;</description>
    <pubDate>Fri, 03 Dec 2021 14:30:55 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2021-12-03T14:30:55Z</dc:date>
    <item>
      <title>Why is the AIM started task going down with "CEE5230S The signal SIGXCPU was received"?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330253#M591</link>
      <description>&lt;P&gt;This is a completely new install and users have just started using it.  It has very limited use at the moment, so some times it takes a while to even notice it's down (that's another issue that we're addressing).  We're currently using v9.5.5.  Short of setting TIME=NOLIMIT in the started task PROC, is there a configuration parameter I can change?  I haven't been able to find anything in the documentation.  Any help would be appreciated.  Thanks!  &lt;/P&gt;</description>
      <pubDate>Fri, 03 Dec 2021 14:30:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330253#M591</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-03T14:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the AIM started task going down with "CEE5230S The signal SIGXCPU was received"?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330254#M592</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;not sure if I can help, but sounds like the CPU time limit has been exceeded.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you using CyberArk AIM component &amp;gt; Credential Provider (CP)? So the agent?&lt;/P&gt;&lt;P&gt;Which application is integrated with CyberArk?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally, v9.5.5 is quite an old version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Fabian&lt;/P&gt;</description>
      <pubDate>Mon, 06 Dec 2021 16:25:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330254#M592</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-06T16:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the AIM started task going down with "CEE5230S The signal SIGXCPU was received"?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330255#M593</link>
      <description>&lt;P&gt;Yes, we're using the agent on Z/OS.  I'm a mainframe guy that was just handed the v9.5.5 agent.  I don't control what's installed on the server side.  &lt;/P&gt;</description>
      <pubDate>Tue, 07 Dec 2021 14:27:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330255#M593</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-07T14:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the AIM started task going down with "CEE5230S The signal SIGXCPU was received"?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330256#M594</link>
      <description>&lt;P&gt;got the point.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Usually I recommend to open a support case, BUT this version is already out of support.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I recommend to pushback to your team who takes care of the CyberArk environment to update it and provide you with a new agent version and test/try again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The current version of z/OS Credential Provider is: v12.1.3&lt;/P&gt;&lt;P&gt;&amp;gt; but it is not compatible with a backend older than 10.5 - so backend must be 10.5. or higher&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the team who takes care need some CyberArk contact person - feel free to contact me here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Fabian&lt;/P&gt;</description>
      <pubDate>Wed, 08 Dec 2021 16:06:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/why-is-the-aim-started-task-going-down-with-quot-cee5230s-the/m-p/1330256#M594</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-08T16:06:41Z</dc:date>
    </item>
  </channel>
</rss>

