<?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 Upgrading to EP80.89 requires log schema update, which breaks all clients communication in Endpoint</title>
    <link>https://community.checkpoint.com/t5/Endpoint/Upgrading-to-EP80-89-requires-log-schema-update-which-breaks-all/m-p/20259#M443</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings, almost a new year...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After upgrading a test client to E80.89 and then realizing I needed to update log schema (sk106662) and then upgrading my console (990003403) for management (R77.30.03), now no clients can communicate with management - all versions show disconnected.&amp;nbsp; We have mostly E80.82 but some E80.70 and one E80.89.&amp;nbsp; After 6 hours of troubleshooting with TAC (Ottowa) it has been determined that the problem is with apache httpd:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;running this in expert mode: $UEPMDIR/apache22/bin/httpd -d $UEPMDIR/apache22 -k start&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; background-color: #ffffff; font-size: 13px;"&gt;Segmentation fault (core dumped)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; background-color: #ffffff; font-size: 13px;"&gt;I have been told this problem has never before been observed.&amp;nbsp; Endpoint client cpinfo has been evaluated and EPCPinfoSRV has been inspected with no problems found.&amp;nbsp; Please help.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; background-color: #ffffff; font-size: 13px;"&gt;Best regards to the New Year - and to my first problem of 2019.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Jan 2019 13:06:30 GMT</pubDate>
    <dc:creator>Dan_Roddy</dc:creator>
    <dc:date>2019-01-02T13:06:30Z</dc:date>
    <item>
      <title>Upgrading to EP80.89 requires log schema update, which breaks all clients communication</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Upgrading-to-EP80-89-requires-log-schema-update-which-breaks-all/m-p/20259#M443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings, almost a new year...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After upgrading a test client to E80.89 and then realizing I needed to update log schema (sk106662) and then upgrading my console (990003403) for management (R77.30.03), now no clients can communicate with management - all versions show disconnected.&amp;nbsp; We have mostly E80.82 but some E80.70 and one E80.89.&amp;nbsp; After 6 hours of troubleshooting with TAC (Ottowa) it has been determined that the problem is with apache httpd:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;running this in expert mode: $UEPMDIR/apache22/bin/httpd -d $UEPMDIR/apache22 -k start&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; background-color: #ffffff; font-size: 13px;"&gt;Segmentation fault (core dumped)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; background-color: #ffffff; font-size: 13px;"&gt;I have been told this problem has never before been observed.&amp;nbsp; Endpoint client cpinfo has been evaluated and EPCPinfoSRV has been inspected with no problems found.&amp;nbsp; Please help.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; background-color: #ffffff; font-size: 13px;"&gt;Best regards to the New Year - and to my first problem of 2019.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jan 2019 13:06:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Upgrading-to-EP80-89-requires-log-schema-update-which-breaks-all/m-p/20259#M443</guid>
      <dc:creator>Dan_Roddy</dc:creator>
      <dc:date>2019-01-02T13:06:30Z</dc:date>
    </item>
  </channel>
</rss>

