<?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: date in binary and messages differ one day in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907040#M3201</link>
    <description>The shutdown was a planned one and occurred round 6am on Jun 11th. There were no out of the ordinary messages at that time. The sequence of events, you mentioned, is the same. So I still do not have a clue!&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Michael</description>
    <pubDate>Tue, 14 Jun 2005 10:55:30 GMT</pubDate>
    <dc:creator>Michael Schulte zur Sur</dc:creator>
    <dc:date>2005-06-14T10:55:30Z</dc:date>
    <item>
      <title>date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907035#M3196</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I have noticed that the date in the binary errorlog and the messages differ excatly one day for one speficic event. How can that be?&lt;BR /&gt;The os is 5.1B pk4.&lt;BR /&gt;&lt;BR /&gt;Thanks for any idea,&lt;BR /&gt;&lt;BR /&gt;Michael</description>
      <pubDate>Mon, 13 Jun 2005 08:16:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907035#M3196</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-06-13T08:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907036#M3197</link>
      <description>What is the specific event - can you post an example?&lt;BR /&gt;&lt;BR /&gt;What error log reporting tool are you using (uerf, decevent, sea...)?&lt;BR /&gt;&lt;BR /&gt;If the specific event is regarding an external controller, like an HSZ80, the date on the external controller could be wrong.&lt;BR /&gt;&lt;BR /&gt;More date (umm, I mean, data) is needed.</description>
      <pubDate>Mon, 13 Jun 2005 10:40:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907036#M3197</guid>
      <dc:creator>Stuart Fuller_2</dc:creator>
      <dc:date>2005-06-13T10:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907037#M3198</link>
      <description>Stuart,&lt;BR /&gt;thanks for answering. I used decevent for analyzing. Both refer to a boot.&lt;BR /&gt;&lt;BR /&gt;messages:&lt;BR /&gt;Jun 11 13:45:59 pra02d vmunix: physical memory = 1024.00 megabytes.&lt;BR /&gt;Jun 11 13:45:59 pra02d vmunix: available memory = 979.62 megabytes.&lt;BR /&gt;Jun 11 13:45:59 pra02d vmunix: using 1293 buffers containing 10.10 megabytes of&lt;BR /&gt;memory&lt;BR /&gt;Jun 11 13:45:59 pra02d vmunix: Firmware revision: 6.9-1&lt;BR /&gt;&lt;BR /&gt;errorlog:&lt;BR /&gt;Logging OS                        2. Digital UNIX &lt;BR /&gt;System Architecture               2. Alpha &lt;BR /&gt;Event sequence number             1. &lt;BR /&gt;Timestamp of occurrence              10-JUN-2005 13:46:00 &lt;BR /&gt;Host name                            pra02d &lt;BR /&gt;&lt;BR /&gt;System type register      x00000022  Systype 34. (Regatta Family) &lt;BR /&gt;Number of CPUs (mpnum)    x00000001 &lt;BR /&gt;CPU logging event (mperr) x00000000 &lt;BR /&gt;&lt;BR /&gt;Event validity                    1. O/S claims event is valid &lt;BR /&gt;Event severity                    5. Low Priority &lt;BR /&gt;Entry type                      300. Start-Up ASCII Message Type &lt;BR /&gt;                                 -1.    - (minor class) &lt;BR /&gt;&lt;BR /&gt;SWI Minor class                   9. ASCII Message &lt;BR /&gt;SWI Minor sub class               3. Startup &lt;BR /&gt;&lt;BR /&gt;ASCII Message &lt;BR /&gt;    Memory trolling not supported, cpu Major id 8, Minor id 4 &lt;BR /&gt;    Alpha boot: available memory from 0x2b9e000 to 0x3ff40000 &lt;BR /&gt;    Compaq Tru64 UNIX V5.1B (Rev. 2650); Tue Mar 22 15:38:17 CET 2005 &lt;BR /&gt;    physical memory = 1024.00 megabytes. &lt;BR /&gt;    available memory = 979.62 megabytes. &lt;BR /&gt;</description>
      <pubDate>Mon, 13 Jun 2005 11:13:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907037#M3198</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-06-13T11:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907038#M3199</link>
      <description>The correct date is Jun 11th because on that Saturday I booted the machine after a planned outage of a few hours.&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Jun 2005 11:42:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907038#M3199</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-06-13T11:42:13Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907039#M3200</link>
      <description>That's a weird one, alright.&lt;BR /&gt;&lt;BR /&gt;The boot message in the error log shows 10-Jun, and this is the system date at the time of the boot.&lt;BR /&gt;&lt;BR /&gt;The syslog messages shows 11-Jun.&lt;BR /&gt;&lt;BR /&gt;Therefore, the system time changed between boot time and when syslog started logging messages.  &lt;BR /&gt;&lt;BR /&gt;The default order of startup is syslogd, binlogd, some network stuff, then the time setter and the time daemon.&lt;BR /&gt;&lt;BR /&gt;Is it possible that the order of startups have changed, such that syslog starts after the time setting/daemon?  I suppose that it's also possible that syslogd started up, and took a little while to actually "get going", and that the time setter ran during that interval.&lt;BR /&gt;&lt;BR /&gt;Of course, that doesn't explain why the system time at boot was 10-Jun.&lt;BR /&gt;&lt;BR /&gt;When was the shutdown?  Do the error log and syslog messages indicate anything out of the ordinary?</description>
      <pubDate>Tue, 14 Jun 2005 10:29:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907039#M3200</guid>
      <dc:creator>Stuart Fuller_2</dc:creator>
      <dc:date>2005-06-14T10:29:45Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907040#M3201</link>
      <description>The shutdown was a planned one and occurred round 6am on Jun 11th. There were no out of the ordinary messages at that time. The sequence of events, you mentioned, is the same. So I still do not have a clue!&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Michael</description>
      <pubDate>Tue, 14 Jun 2005 10:55:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907040#M3201</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-06-14T10:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907041#M3202</link>
      <description>Did you finally get a fix for this one ?</description>
      <pubDate>Fri, 15 Jul 2005 01:52:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907041#M3202</guid>
      <dc:creator>Ronald_35</dc:creator>
      <dc:date>2005-07-15T01:52:33Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907042#M3203</link>
      <description>Ronald,&lt;BR /&gt;&lt;BR /&gt;thanks for posting but the problem is a mystery to us.&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Jul 2005 03:25:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907042#M3203</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-07-15T03:25:15Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907043#M3204</link>
      <description>This is a known problem with DECevent. It displays dates as one day early. Any other utility will display the correct date. I would recommend using WEBES.</description>
      <pubDate>Fri, 15 Jul 2005 08:45:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907043#M3204</guid>
      <dc:creator>Han Pilmeyer</dc:creator>
      <dc:date>2005-07-15T08:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: date in binary and messages differ one day</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907044#M3205</link>
      <description>Han,&lt;BR /&gt;I can't believe this has eluded me so long.&lt;BR /&gt;&lt;BR /&gt;Ronald,&lt;BR /&gt;thanks to you this thread got once more attention.&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Jul 2005 09:24:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/date-in-binary-and-messages-differ-one-day/m-p/4907044#M3205</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2005-07-15T09:24:33Z</dc:date>
    </item>
  </channel>
</rss>

