<?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 Cannot login:  Please wait...checking for disk quotas in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989508#M421841</link>
    <description>HPUX 10.20 is running on:&lt;BR /&gt;&lt;BR /&gt;  $ model&lt;BR /&gt;  9000/777/C110&lt;BR /&gt;&lt;BR /&gt;  # uname -a&lt;BR /&gt;  HP-UX hostname B.10.20 A 9000/777 2010505180 two-user license&lt;BR /&gt;&lt;BR /&gt;I cannot login to this system.  I do not know HP-UX / CDE to speak of - this is an inherited system.&lt;BR /&gt;&lt;BR /&gt;Console (CDE user session) is locked up at "Logout Confirmation" dialog with the "Continue Logout" button pressed.    Scroll/Num Lock lamps are stuck off, but Caps Lock is not frozen.  I have tried console keys normally useful with XFree86/XOrg to try to restart the X server or to shutdown/reboot, but these do not appear to work with CDE.  The last thing that was done was to have the user unlock the console.  He typed logout at a terminal session that was already open.  Nothing happened, so then I right-clicked on the desktop select Logout that way.  The "Continue Logout" button was pressed, and now we are here.  I cannot say for sure the system was not already messed up before that as no one has actively used the system for a number of days, but cron e-mails were sent to me this morning, and the system is still pingable.&lt;BR /&gt;&lt;BR /&gt;How may I regain access to the console?&lt;BR /&gt;&lt;BR /&gt;Serial 1 configured for a mouse (9600 8N1 on terminal shows %Spaceware messages periodically.)&lt;BR /&gt;&lt;BR /&gt;Serial 2 appears to not be configured.&lt;BR /&gt;&lt;BR /&gt;Telnet to LAN address gives:&lt;BR /&gt;&lt;BR /&gt;  login: root&lt;BR /&gt;  Password:&lt;BR /&gt;  Please wait...checking for disk quotas&lt;BR /&gt;&lt;BR /&gt;At this point, the telnet session is locked up even after waiting a half hour or more.  The heartbeat indicator is blinking.   Other indicators blink infrequently.&lt;BR /&gt;&lt;BR /&gt;Is it possible this is a file system space issue - like /var being full?  Surely root would be able to login to at least shutdown and or correct the problem.&lt;BR /&gt;&lt;BR /&gt;What is an unlucky system admin to do in this situation?  Pull the plug?  Is there a way to be sure the disks are synced first?&lt;BR /&gt;&lt;BR /&gt;Are there techniques to get in and find out what to do to resurrect the system.  Some other UNIX systems I have used in the past would let a root user in even if non-permissioned users were locked out.&lt;BR /&gt;</description>
    <pubDate>Fri, 07 Jul 2006 14:08:58 GMT</pubDate>
    <dc:creator>Kevin R. Bulgrien</dc:creator>
    <dc:date>2006-07-07T14:08:58Z</dc:date>
    <item>
      <title>Cannot login:  Please wait...checking for disk quotas</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989508#M421841</link>
      <description>HPUX 10.20 is running on:&lt;BR /&gt;&lt;BR /&gt;  $ model&lt;BR /&gt;  9000/777/C110&lt;BR /&gt;&lt;BR /&gt;  # uname -a&lt;BR /&gt;  HP-UX hostname B.10.20 A 9000/777 2010505180 two-user license&lt;BR /&gt;&lt;BR /&gt;I cannot login to this system.  I do not know HP-UX / CDE to speak of - this is an inherited system.&lt;BR /&gt;&lt;BR /&gt;Console (CDE user session) is locked up at "Logout Confirmation" dialog with the "Continue Logout" button pressed.    Scroll/Num Lock lamps are stuck off, but Caps Lock is not frozen.  I have tried console keys normally useful with XFree86/XOrg to try to restart the X server or to shutdown/reboot, but these do not appear to work with CDE.  The last thing that was done was to have the user unlock the console.  He typed logout at a terminal session that was already open.  Nothing happened, so then I right-clicked on the desktop select Logout that way.  The "Continue Logout" button was pressed, and now we are here.  I cannot say for sure the system was not already messed up before that as no one has actively used the system for a number of days, but cron e-mails were sent to me this morning, and the system is still pingable.&lt;BR /&gt;&lt;BR /&gt;How may I regain access to the console?&lt;BR /&gt;&lt;BR /&gt;Serial 1 configured for a mouse (9600 8N1 on terminal shows %Spaceware messages periodically.)&lt;BR /&gt;&lt;BR /&gt;Serial 2 appears to not be configured.&lt;BR /&gt;&lt;BR /&gt;Telnet to LAN address gives:&lt;BR /&gt;&lt;BR /&gt;  login: root&lt;BR /&gt;  Password:&lt;BR /&gt;  Please wait...checking for disk quotas&lt;BR /&gt;&lt;BR /&gt;At this point, the telnet session is locked up even after waiting a half hour or more.  The heartbeat indicator is blinking.   Other indicators blink infrequently.&lt;BR /&gt;&lt;BR /&gt;Is it possible this is a file system space issue - like /var being full?  Surely root would be able to login to at least shutdown and or correct the problem.&lt;BR /&gt;&lt;BR /&gt;What is an unlucky system admin to do in this situation?  Pull the plug?  Is there a way to be sure the disks are synced first?&lt;BR /&gt;&lt;BR /&gt;Are there techniques to get in and find out what to do to resurrect the system.  Some other UNIX systems I have used in the past would let a root user in even if non-permissioned users were locked out.&lt;BR /&gt;</description>
      <pubDate>Fri, 07 Jul 2006 14:08:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989508#M421841</guid>
      <dc:creator>Kevin R. Bulgrien</dc:creator>
      <dc:date>2006-07-07T14:08:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot login:  Please wait...checking for disk quotas</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989509#M421842</link>
      <description>Last time I ran across this, there were NFS hard mounts, and the link to the other server was down.  Don't know if this applies in your case.  It *eventually* timed-out.&lt;BR /&gt;</description>
      <pubDate>Fri, 07 Jul 2006 15:32:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989509#M421842</guid>
      <dc:creator>OldSchool</dc:creator>
      <dc:date>2006-07-07T15:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot login:  Please wait...checking for disk quotas</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989510#M421843</link>
      <description>How did you know there is an NFS mount to another system.  Wink.  The host for that share is a SparcStation is powered down.  All of this came about because a new UPS is being installed for both systems.  I needed to try to shutdown the HPUX system to transfer power to the new UPS.  The Sparcstation was shutdown first.  Crossing fingers and turning all the power switches on now...&lt;BR /&gt;&lt;BR /&gt;BINGO!&lt;BR /&gt;&lt;BR /&gt;It's aaaallliiiiiiiiiiiiiiiiiive!&lt;BR /&gt;&lt;BR /&gt;Oh my!  Was there a patch that should have been installed to prevent this awful, awful behavior?&lt;BR /&gt;</description>
      <pubDate>Fri, 07 Jul 2006 15:51:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989510#M421843</guid>
      <dc:creator>Kevin R. Bulgrien</dc:creator>
      <dc:date>2006-07-07T15:51:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot login:  Please wait...checking for disk quotas</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989511#M421844</link>
      <description>Welcome to the world of NFS. Unlike PCs which do not treat network filesystems the same way, all NFS disks in /etc/fstab must exist in order  to bootup. The awful behavior is how it is. 10.20 went out of support several years ago so there are no patches. If I were you, I would remove the NFS entries from /eetc/fstab and manually mount the remote filesystems only when you know the server is working. NFS servers can never be taken down because they take all their clients with them.&lt;BR /&gt; &lt;BR /&gt;The alternative is to use automounter but unless you are up to date on patches, the automounter may have some stability problems too.&lt;BR /&gt;</description>
      <pubDate>Fri, 07 Jul 2006 19:17:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989511#M421844</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2006-07-07T19:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot login:  Please wait...checking for disk quotas</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989512#M421845</link>
      <description>An NFS server was down.  When the NFS server came back online, the problems disappeared.  The first reply was the response I needed.</description>
      <pubDate>Mon, 10 Jul 2006 08:57:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-login-please-wait-checking-for-disk-quotas/m-p/4989512#M421845</guid>
      <dc:creator>Kevin R. Bulgrien</dc:creator>
      <dc:date>2006-07-10T08:57:13Z</dc:date>
    </item>
  </channel>
</rss>

