<?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: OpenVMS crash in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448803#M16905</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;For clarification, VMS CIFS being a port of OpenSource Samba, it is heavily dependent upon CRTL routines and runs only in USER mode. Thus by default, it is not a privileged application and it does NOT makes use of F11B$locks or any such.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Shilpa</description>
    <pubDate>Tue, 30 Jun 2009 07:48:21 GMT</pubDate>
    <dc:creator>Shilpa K</dc:creator>
    <dc:date>2009-06-30T07:48:21Z</dc:date>
    <item>
      <title>OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448794#M16896</link>
      <description>&lt;!--!*#--&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;I have never seen OpenVMS crash up to now when I run some multithreaded tasks using OmniORB 4.1.3 and SqLite 3.5.7 on fully patched (Update 1000) OpenVMS IA64 8.3.&lt;BR /&gt;&lt;BR /&gt;Application runs fine several hours or even day when system crash.&lt;BR /&gt;&lt;BR /&gt;In  SYS$ERRORLOG:CLUE$*.LIS is all the times:&lt;BR /&gt;&lt;BR /&gt;Bugcheck Type:     XQPERR, Error detected by file system XQP&lt;BR /&gt;&lt;BR /&gt;Failing Instruction:&lt;BR /&gt;UNHOOK_BFRL_C+00550:              break.m     100002&lt;BR /&gt;&lt;BR /&gt;I had found minimum privileges to be able to run it (NETMBX , PRMMBX, OPER, READALL) but system crash the same way.&lt;BR /&gt;&lt;BR /&gt;SqLite DB file is exposed over SAMBA V1.1-1 share but system crash when nobody read it. &lt;BR /&gt;&lt;BR /&gt;Can somebody tell me how to interpret such CLUE?&lt;BR /&gt;</description>
      <pubDate>Mon, 29 Jun 2009 05:14:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448794#M16896</guid>
      <dc:creator>Stehlik Tomas</dc:creator>
      <dc:date>2009-06-29T05:14:06Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448795#M16897</link>
      <description>Hi Stehlik,&lt;BR /&gt;&lt;BR /&gt;In the clue crash output, I see these lines:&lt;BR /&gt;&lt;BR /&gt;R8  =  00000000.00002124   %SYSTEM-F-IVLOCKID, invalid lock ID&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;R19 =  FFFFFFFF.8077DC60   SYS$DEQ_C+00060&lt;BR /&gt;&lt;BR /&gt;I wonder if some lock was being dequeued at the time of system crash and if the lockid was invalid as indicated by the status above. &lt;BR /&gt;&lt;BR /&gt;It appears to me that this problem requires a detailed analysis of the system crash to find the actual cause. You may want to log a call with HP support so that they can analyse the dump file.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Shilpa</description>
      <pubDate>Mon, 29 Jun 2009 06:09:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448795#M16897</guid>
      <dc:creator>Shilpa K</dc:creator>
      <dc:date>2009-06-29T06:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448796#M16898</link>
      <description>Stehlik,&lt;BR /&gt;&lt;BR /&gt;Concur. Call support, and be prepared to send them the dump file.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Mon, 29 Jun 2009 06:13:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448796#M16898</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2009-06-29T06:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448797#M16899</link>
      <description>&lt;!--!*#--&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;OK I will try to contact HP support.&lt;BR /&gt;&lt;BR /&gt;Just one question - can unprivileged task cause system crash?&lt;BR /&gt;&lt;BR /&gt;Tomas</description>
      <pubDate>Mon, 29 Jun 2009 06:26:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448797#M16899</guid>
      <dc:creator>Stehlik Tomas</dc:creator>
      <dc:date>2009-06-29T06:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448798#M16900</link>
      <description>&amp;gt;can unprivileged task cause system crash?&lt;BR /&gt;&lt;BR /&gt;Ideally, no.  But they can cause conditions that cause a buggy kernel to crash.</description>
      <pubDate>Mon, 29 Jun 2009 06:48:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448798#M16900</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-06-29T06:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448799#M16901</link>
      <description>Hi Stehlik,&lt;BR /&gt;&lt;BR /&gt;As you say you are running CIFS on this system, just curious to know if there were any SMBD process crash on this system in the recent past. Could you please check if there are any dump files in the directory samba$root:[var.cores...]? Also, could you please check if there is any ACCVIO trace-back information in the log files, samba$root:[var]samba$root:[var]SAMBA$SMBD_STARTUP.LOG;*?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shilpa</description>
      <pubDate>Mon, 29 Jun 2009 07:06:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448799#M16901</guid>
      <dc:creator>Shilpa K</dc:creator>
      <dc:date>2009-06-29T07:06:00Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448800#M16902</link>
      <description>I had search through &lt;BR /&gt;&lt;BR /&gt;$ sea SAMBA$ROOT:[000000...]*.log acc&lt;BR /&gt;&lt;BR /&gt;without any results.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 29 Jun 2009 07:29:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448800#M16902</guid>
      <dc:creator>Stehlik Tomas</dc:creator>
      <dc:date>2009-06-29T07:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448801#M16903</link>
      <description>Stehlik,&lt;BR /&gt;&lt;BR /&gt;As to your question: Can unprivileged task cause system crash?&lt;BR /&gt;&lt;BR /&gt;Generally, the answer is no. But no system is perfect.&lt;BR /&gt;&lt;BR /&gt;There have been almost no ways in which a non-privileged program can gain access to elevated states and subvert the system. However, if a non-privileged program (or collection of programs) makes a series of requests that expose a latent inconsistency within the system, a crash can ensue.&lt;BR /&gt;&lt;BR /&gt;The XQP is the OpenVMS component that manages disk file structures. What appears to have happened is that the XQP detected an inconsistency in its data structures and initiated a crash, rather than take the risk of a more systemic problem. This behavior is correct. &lt;BR /&gt;&lt;BR /&gt;READALL in particular should be managed with care. It effectively allows the holder to read any file on the disk, bypassing all of the protection mechanisms.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Mon, 29 Jun 2009 12:48:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448801#M16903</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2009-06-29T12:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448802#M16904</link>
      <description>Thomas,&lt;BR /&gt;&lt;BR /&gt;an XQPERR in F11BXQP.EXE is most likely an OpenVMS XQP problem. Except if some privileged application (e.g. SAMBA/CIFS ?) is playing 'dirty tricks' with F11B$ locks...&lt;BR /&gt;&lt;BR /&gt;You're already running the most recent F11BXQP.EXE available.&lt;BR /&gt;&lt;BR /&gt;What is or was running in the current process at the time of the crash: process name DEX ?&lt;BR /&gt;&lt;BR /&gt;The first attempt to analyze this crash would be to try to find the lock being DEQued. Look at the stack with SDA&amp;gt; CLUE STACK to try to find an address pointing to a LKB (Lock Block).&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 29 Jun 2009 17:26:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448802#M16904</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2009-06-29T17:26:49Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448803#M16905</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;For clarification, VMS CIFS being a port of OpenSource Samba, it is heavily dependent upon CRTL routines and runs only in USER mode. Thus by default, it is not a privileged application and it does NOT makes use of F11B$locks or any such.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Shilpa</description>
      <pubDate>Tue, 30 Jun 2009 07:48:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448803#M16905</guid>
      <dc:creator>Shilpa K</dc:creator>
      <dc:date>2009-06-30T07:48:21Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS crash</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448804#M16906</link>
      <description>Just because CIFS is running in user mode doesn't mean that everything else around it and everything that it's affecting are in User mode.&lt;BR /&gt;If the system takes out a lock that then gets corrupt due to imperfections elsewhere, that can still cause a crash.  This is  analogous to a double deallocation of memory that would still cause a crash even though the deallocators may be millions of clock cycles apart.&lt;BR /&gt;&lt;BR /&gt;Looking at the whole problem rather than the little bit of it may be necessary.</description>
      <pubDate>Tue, 30 Jun 2009 09:50:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-crash/m-p/4448804#M16906</guid>
      <dc:creator>Steve Reece_3</dc:creator>
      <dc:date>2009-06-30T09:50:15Z</dc:date>
    </item>
  </channel>
</rss>

