<?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: Expedition Fusion remote exception in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/234190#M616</link>
    <description>Also, notice that we should do an apt-get update, not upgrade.&lt;BR /&gt;&lt;BR /&gt;Upgrading will upgrade all the packages in the system based on the last known versions. This may imply that you would install new version of PHP or the MariaDB that may have some backwards compatibility issues.&lt;BR /&gt;We have experienced this before with some of the packages that Expedition uses.</description>
    <pubDate>Fri, 05 Oct 2018 19:14:14 GMT</pubDate>
    <dc:creator>dgildelaig</dc:creator>
    <dc:date>2018-10-05T19:14:14Z</dc:date>
    <item>
      <title>Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/219915#M239</link>
      <description>&lt;P&gt;Does anyone have an idea as to why I get a "remote exception" error when running Expedition on Fusion?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also noticed the Jobs and Task Manager won't start.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jonathan&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 13:13:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/219915#M239</guid>
      <dc:creator>JonCrockett</dc:creator>
      <dc:date>2018-06-29T13:13:04Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/219917#M241</link>
      <description>&lt;P&gt;I fixed this issue by running "sudo apt-get dist-upgrade".&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 13:54:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/219917#M241</guid>
      <dc:creator>JonCrockett</dc:creator>
      <dc:date>2018-06-29T13:54:28Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/220844#M253</link>
      <description>&lt;P&gt;If I understand correctly, it doesn't seem to be related to VMWare Fusion version of Expedition, but some interal state of the Ubuntu virtual machine, that got fixed through the update.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, this seemed to be a OS/package corrupted filesystem issue, not that much related to Expedition of Fusion. Does it make sense?&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jul 2018 09:15:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/220844#M253</guid>
      <dc:creator>dgildelaig</dc:creator>
      <dc:date>2018-07-06T09:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/220884#M259</link>
      <description>&lt;P&gt;That makes sense. I suspected it was an issue with Fusion because there was a different solution to fixing the errors when it was loaded on ESXi. In that case we had to convert it with the OVF tool before loading it on ESXi. I haven't tried installing it on Workstation or Player yet.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jul 2018 12:47:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/220884#M259</guid>
      <dc:creator>JonCrockett</dc:creator>
      <dc:date>2018-07-06T12:47:50Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/233689#M599</link>
      <description>&lt;P&gt;I'm still having this issue after doing the&amp;nbsp;sudo apt-get dist-upgrade. I&amp;nbsp;&lt;SPAN&gt; convert it with&amp;nbsp;VMware&amp;nbsp;Workstation to an ovf before loading it on ESX.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Any tips for me on how to get his fixed?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Oct 2018 14:59:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/233689#M599</guid>
      <dc:creator>MichaelSonen</dc:creator>
      <dc:date>2018-10-03T14:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/233836#M606</link>
      <description>&lt;P&gt;Have you tried to download the OVA image straight?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2018 08:01:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/233836#M606</guid>
      <dc:creator>alestevez</dc:creator>
      <dc:date>2018-10-04T08:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/234144#M615</link>
      <description>&lt;P&gt;I fixed the issue by fixing some of the other issues the system had.&amp;nbsp;&lt;BR /&gt;The host for the&amp;nbsp;&lt;SPAN&gt;Expedition Machine Learning needed to be set and the data structure folder had to be created and set.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Oct 2018 17:04:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/234144#M615</guid>
      <dc:creator>MichaelSonen</dc:creator>
      <dc:date>2018-10-05T17:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition Fusion remote exception</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/234190#M616</link>
      <description>Also, notice that we should do an apt-get update, not upgrade.&lt;BR /&gt;&lt;BR /&gt;Upgrading will upgrade all the packages in the system based on the last known versions. This may imply that you would install new version of PHP or the MariaDB that may have some backwards compatibility issues.&lt;BR /&gt;We have experienced this before with some of the packages that Expedition uses.</description>
      <pubDate>Fri, 05 Oct 2018 19:14:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-fusion-remote-exception/m-p/234190#M616</guid>
      <dc:creator>dgildelaig</dc:creator>
      <dc:date>2018-10-05T19:14:14Z</dc:date>
    </item>
  </channel>
</rss>

