<?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: sslvpn: exited x times waiting y seconds to retry in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/sslvpn-exited-x-times-waiting-y-seconds-to-retry/m-p/69301#M40252</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The bug#64266 might be your issue, though this bug was fixed on 6.1.7.&lt;/P&gt;
&lt;P&gt;I'm not sure you are hitting this issue or not, because you are using 6.1.7.&lt;/P&gt;
&lt;P&gt;I recommend to open a ticket and&amp;nbsp;ask TAC.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;====&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Fixed a rare issue where certain processes (l3svc and sslvpn) stopped responding when a&lt;BR /&gt;Content update and FQDN refresh occurred simultaneously.&lt;/P&gt;
&lt;P&gt;====&lt;/P&gt;</description>
    <pubDate>Thu, 10 Dec 2015 04:53:23 GMT</pubDate>
    <dc:creator>emr_1</dc:creator>
    <dc:date>2015-12-10T04:53:23Z</dc:date>
    <item>
      <title>sslvpn: exited x times waiting y seconds to retry</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sslvpn-exited-x-times-waiting-y-seconds-to-retry/m-p/69249#M40229</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Getting following error:&lt;/P&gt;
&lt;P&gt;sslvpn: exited x times waiting y seconds to retry&lt;/P&gt;
&lt;P&gt;l3svc: exited x times waiting y seconds to retry&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyone having same messages? Hardware is 2050 with 6.1.7 running.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kevin&lt;/P&gt;</description>
      <pubDate>Wed, 09 Dec 2015 08:50:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sslvpn-exited-x-times-waiting-y-seconds-to-retry/m-p/69249#M40229</guid>
      <dc:creator>kevin_thys</dc:creator>
      <dc:date>2015-12-09T08:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: sslvpn: exited x times waiting y seconds to retry</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sslvpn-exited-x-times-waiting-y-seconds-to-retry/m-p/69301#M40252</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The bug#64266 might be your issue, though this bug was fixed on 6.1.7.&lt;/P&gt;
&lt;P&gt;I'm not sure you are hitting this issue or not, because you are using 6.1.7.&lt;/P&gt;
&lt;P&gt;I recommend to open a ticket and&amp;nbsp;ask TAC.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;====&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Fixed a rare issue where certain processes (l3svc and sslvpn) stopped responding when a&lt;BR /&gt;Content update and FQDN refresh occurred simultaneously.&lt;/P&gt;
&lt;P&gt;====&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 04:53:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sslvpn-exited-x-times-waiting-y-seconds-to-retry/m-p/69301#M40252</guid>
      <dc:creator>emr_1</dc:creator>
      <dc:date>2015-12-10T04:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: sslvpn: exited x times waiting y seconds to retry</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sslvpn-exited-x-times-waiting-y-seconds-to-retry/m-p/69311#M40258</link>
      <description>&lt;P&gt;yes we upgraded to 6.1.7 to solve this issue. Was quite ok for some time longer as before but now we received it again.&lt;/P&gt;
&lt;P&gt;Case is open.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 10:51:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sslvpn-exited-x-times-waiting-y-seconds-to-retry/m-p/69311#M40258</guid>
      <dc:creator>kevin_thys</dc:creator>
      <dc:date>2015-12-10T10:51:28Z</dc:date>
    </item>
  </channel>
</rss>

