DOCSLIB.ORG

HPSS Error Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HPSS Error Manual HPSS Error Manual High Performance Storage System, version 7.5.3.0.0, 10 December 2018 HPSS Error Manual High Performance Storage System, version 7.5.3.0.0, 10 December 2018 Table of Contents .............................................................................................................................................................. vii 1. Problem diagnosis and resolution ..................................................................................................... 1 1.1. HPSS infrastructure problems ................................................................................................ 1 1.1.1. RPC problems .............................................................................................................. 1 1.1.1.1. One HPSS server cannot communicate with another ....................................... 1 1.1.1.2. A server cannot obtain its credentials .............................................................. 2 1.1.1.3. A server cannot register its RPC info .............................................................. 2 1.1.1.4. The connection table may have overflowed ..................................................... 2 1.1.2. DB2 problems .............................................................................................................. 2 1.1.2.1. HPSS servers cannot communicate with DB2 ................................................. 2 1.1.2.2. One or more HPSS servers are receiving metadata or DB2 errors ................... 3 1.1.2.3. Cannot start DB2 instance ................................................................................ 4 1.1.2.4. Certain HPSS operations hang or fail under a heavy load ............................... 4 1.1.3. Security problems ........................................................................................................ 5 1.1.3.1. HPSS servers are unable to connect to other HPSS servers ............................. 5 1.1.3.2. Client API users get "credentials expired" errors ............................................. 5 1.2. HPSS server problems ............................................................................................................ 6 1.2.1. General problems ......................................................................................................... 6 1.2.1.1. Servers cannot be started .................................................................................. 6 1.2.1.2. Servers cannot talk to one another ................................................................... 7 1.2.2. Core Server problems .................................................................................................. 7 1.2.2.1. Core Server cannot connect to SSM ................................................................ 7 1.2.2.2. The Core Server takes a long time starting ...................................................... 7 1.2.2.3. Service parameters have been changed and a Core Server does not recognize them ............................................................................................................... 7 1.2.2.4. Receiving messages from Core Server indicating inconsistencies in account summary records .............................................................................................. 8 1.2.2.5. Core Server cannot connect to Gatekeeper ...................................................... 8 1.2.2.6. Errors reading, writing, creating, or deleting metadata .................................... 8 1.2.2.7. Core Server reports "no space" ........................................................................ 8 1.2.2.8. Core Server cannot be started .......................................................................... 9 1.2.2.9. Core Server marks tape volumes full too soon ................................................ 9 1.2.3. Migration/Purge Server (MPS) problems .................................................................. 10 1.2.3.1. No storage class information reported on Storage Class List window ........... 10 1.2.3.2. A storage class does not show up in the Storage Class List window ............. 10 1.2.3.3. MPS is not migrating or purging data ............................................................ 11 1.2.3.4. Purges occur more frequently or less frequently than desired ........................ 11 1.2.3.5. Migrations occur more frequently or less frequently than desired ................. 11 1.2.3.6. Tape storage class cannot be purged .............................................................. 12 1.2.4. Physical Volume Library (PVL) problems ............................................................... 12 1.2.4.1. Tape mount requests are not being satisfied .................................................. 12 1.2.4.2. A PVL job cannot be canceled ...................................................................... 12 1.2.4.3. Core Server mount requests are not appearing in PVL job queues ................ 13 1.2.4.4. A tape cartridge is physically mounted in a drive but is not recognized by the system as being mounted ...................................................................................... 13 1.2.4.5. A drive has been added to the PVL but is not being used by the system ........ 14 1.2.4.6. Cannot delete a drive ...................................................................................... 14 iii HPSS Error Manual 1.2.4.7. Cannot add a drive ......................................................................................... 14 1.2.4.8. Imports of cartridges fail due to improper labeling ....................................... 15 1.2.4.9. PVL cannot connect to the Core Server ......................................................... 15 1.2.4.10. PVL cannot connect to a Mover .................................................................. 16 1.2.4.11. PVL cannot connect to the PVR .................................................................. 16 1.2.4.12. PVL cannot connect to SSM ........................................................................ 16 1.2.5. Physical Volume Repository (PVR) problems .......................................................... 16 1.2.5.1. PVR is unable to communicate with a robot ................................................. 16 1.2.5.2. PVR operational state is "Major" ................................................................... 17 1.2.6. Gatekeeper (GK) Problems ....................................................................................... 17 1.2.6.1. The Core Server is not calling the Gatekeeper .............................................. 17 1.2.6.2. The wrong request types are being monitored ............................................... 18 1.2.6.3. The Gatekeeper is not doing any gatekeeping ............................................... 18 1.2.6.4. The SSM cannot contact the Gatekeeper ....................................................... 18 1.2.6.5. The Gatekeeper won’t start or load ................................................................ 18 1.2.6.6. Account validation fails to initialize .............................................................. 19 1.2.7. Mover problems ......................................................................................................... 19 1.2.7.1. Mover performs poorly .................................................................................. 19 1.2.7.2. Mover cannot be started ................................................................................. 20 1.2.7.3. Mover cannot write a label to a tape ............................................................. 21 1.2.7.4. Mover cannot read the label from a previously labeled tape .......................... 21 1.2.7.5. Tape positioning operations are performing poorly ....................................... 21 1.2.7.6. Network transfers are performing poorly ....................................................... 22 1.2.7.7. Mover cannot perform a LFT data transfer .................................................... 22 1.2.8. Logging services problems ........................................................................................ 22 1.2.8.1. Logging performance is sluggish ................................................................... 22 1.2.8.2. TABs and newlines in HPSS log messages converted to #011, #012 in syslog ............................................................................................................................ 23 1.2.9. Startup Daemon problems ......................................................................................... 23 1.2.9.1. Cannot start a server ....................................................................................... 23 1.2.9.2. Cannot force halt a server .............................................................................. 24 1.2.9.3. A problem exists with a Startup Daemon lock file ........................................ 24 1.2.10. SSM problems ......................................................................................................... 25 1.2.10.1. The System Manager won’t start ................................................................. 26 1.2.10.2. The hpssgui or hpssadm program won’t start .............................................. 27 1.2.10.3. The hpssgui or hpssadm cannot connect to the System Manager ................. 31 1.2.10.4. Performance of the hpssgui is sluggish ........................................................ 35 1.2.10.5. The hpssgui user windows aren’t getting filled
Load more

Recommended publications
  • Mac OS 8 Update
    K Service Source Mac OS 8 Update Known problems, Internet Access, and Installation Mac OS 8 Update Document Contents - 1 Document Contents • Introduction • About Mac OS 8 • About Internet Access What To Do First Additional Software Auto-Dial and Auto-Disconnect Settings TCP/IP Connection Options and Internet Access Length of Configuration Names Modem Scripts & Password Length Proxies and Other Internet Config Settings Web Browser Issues Troubleshooting • About Mac OS Runtime for Java Version 1.0.2 • About Mac OS Personal Web Sharing • Installing Mac OS 8 • Upgrading Workgroup Server 9650 & 7350 Software Mac OS 8 Update Introduction - 2 Introduction Mac OS 8 is the most significant update to the Macintosh operating system since 1984. The updated system gives users PowerPC-native multitasking, an efficient desktop with new pop-up windows and spring-loaded folders, and a fully integrated suite of Internet services. This document provides information about Mac OS 8 that supplements the information in the Mac OS installation manual. For a detailed description of Mac OS 8, useful tips for using the system, troubleshooting, late-breaking news, and links for online technical support, visit the Mac OS Info Center at http://ip.apple.com/infocenter. Or browse the Mac OS 8 topic in the Apple Technical Library at http:// tilsp1.info.apple.com. Mac OS 8 Update About Mac OS 8 - 3 About Mac OS 8 Read this section for information about known problems with the Mac OS 8 update and possible solutions. Known Problems and Compatibility Issues Apple Language Kits and Mac OS 8 Apple's Language Kits require an updater for full functionality with this version of the Mac OS.
    [Show full text]
  • Linux Tutorial Last Updated: September 29 2021 for Windows Users
    VLAAMS SUPERCOMPUTER Innovative Computing CENTRUM for A Smarter Flanders Linux Tutorial Last updated: September 29 2021 For Windows Users Authors: Jasper Devreker (UGent), Ewan Higgs (UGent), Kenneth Hoste (UGent) Acknowledgement: VSCentrum.be Audience: This document is a hands-on guide for using the Linux command line in the context of the UGent HPC infrastructure. The command line (sometimes called ’shell’) can seems daunting at first, but with a little understanding can be very easy to use. Everything you do startsatthe prompt. Here you have the liberty to type in any commands you want. Soon, you will be able to move past the limited point and click interface and express interesting ideas to the computer using the shell. Gaining an understanding of the fundamentals of Linux will help accelerate your research using the HPC infrastructure. You will learn about commands, managing files, and some scripting basics. Notification: In$ commands this tutorial specific commands are separated from the accompanying text: These should be entered by the reader at a command line in a terminal on the UGent-HPC. They appear in all exercises preceded by a $ and printed in bold. You’ll find those actions ina grey frame. Button are menus, buttons or drop down boxes to be pressed or selected. “Directory” is the notation for directories (called “folders” in Windows terminology) or specific files. (e.g., “/user/home/gent/vsc400/vsc40000”) “Text” Is the notation for text to be entered. Tip: A “Tip” paragraph is used for remarks or tips. They can also be downloaded from the VSC website at https://www.vscentrum.be.
    [Show full text]
  • Xerox 4050/4090/4450/4650 Laser Printing Systems Message Guide
    XEROX Xerox 4050/4090/4450/4650 Laser Printing Systems Message Guide April 1995 720P93980 Xerox Corporation 701 S. Aviation Boulevard El Segundo, CA 90245 © 1991, 1992, 1993, 1994, 1995 by Xerox Corporation. All rights reserved. Copyright protection claimed includes all forms and matters of copyrightable material and information now allowed by statutory or judicial law or hereinafter granted, including without limitation, material generated from the software programs which are displayed on the screen, such as icons, screen displays, looks, etc. Printed in the United States of America Publication number: 720P93980 Xerox® and all Xerox products mentioned in this publication are trademarks of Xerox Corporation. Products and trademarks of other companies are also acknowledged. Changes are periodically made to this document. Changes, technical inaccuracies, and typographic errors will be corrected in subsequent editions. This document was created on the Xerox 6085 Professional Computer System using GobalView software. The typeface is Optima. Table of contents Introduction vii Document conventions vii Related publications viii 1. Compress command messages 1-1 2. Data Capture Utility messages 2-1 System failure or reload messages 2-6 3. Disk Save and Restore command messages 3-1 4. File Conversion Utility messages 4-1 5. General Floppy Utility messages 5-1 FLF messages 5-15 6. Forms Description Language compilation messages 6-1 7. Host Interface Processor messages 7-1 8. Interpress Font Utility messages 8-1 9. Operating System Software messages 9-1 OS level 0: Confirmation messages 9-1 OS level 1: Informational messages 9-7 OS level 2: Routine maintenance messages 9-37 OS level 3: Printer problem messages 9-59 OS level 4: System or tape problem messages 9-64 OS level 6: Job integrity problem messages 9-68 OS level 7: System problem messages 9-88 OS level 8: Probable severe software errors 9-93 OS level 9: Probable severe hardware errors 9-99 10.
    [Show full text]
  • UNIX X Command Tips and Tricks David B
    SESUG Paper 122-2019 UNIX X Command Tips and Tricks David B. Horvath, MS, CCP ABSTRACT SAS® provides the ability to execute operating system level commands from within your SAS code – generically known as the “X Command”. This session explores the various commands, the advantages and disadvantages of each, and their alternatives. The focus is on UNIX/Linux but much of the same applies to Windows as well. Under SAS EG, any issued commands execute on the SAS engine, not necessarily on the PC. X %sysexec Call system Systask command Filename pipe &SYSRC Waitfor Alternatives will also be addressed – how to handle when NOXCMD is the default for your installation, saving results, and error checking. INTRODUCTION In this paper I will be covering some of the basics of the functionality within SAS that allows you to execute operating system commands from within your program. There are multiple ways you can do so – external to data steps, within data steps, and within macros. All of these, along with error checking, will be covered. RELEVANT OPTIONS Execution of any of the SAS System command execution commands depends on one option's setting: XCMD Enables the X command in SAS. Which can only be set at startup: options xcmd; ____ 30 WARNING 30-12: SAS option XCMD is valid only at startup of the SAS System. The SAS option is ignored. Unfortunately, ff NOXCMD is set at startup time, you're out of luck. Sorry! You might want to have a conversation with your system administrators to determine why and if you can get it changed.
    [Show full text]
  • Blank Screen Xbox One
    Blank Screen Xbox One Typhous and Torricellian Waiter lows, but Ernest emptily coquette her countermark. Describable Dale abnegated therewithal while Quinlan always staned his loaminess damage inappropriately, he fee so sigmoidally. Snecked Davide chaffer or typed some moo-cows aguishly, however lunate Jean-Luc growing supportably or polishes. Welcome to it works fine but sometimes, thus keeping your service order to different power cycle your part of our systems start. Obs and more updates, and we will flicker black? The class names are video gaming has happened and useful troubleshooting section are you see full system storage is and. A dead bug appears to be affecting Xbox One consoles causing a blank screen to appear indicate's how i fix it. Fix the Black Screen Starting Games On XBox One TeckLyfe. We carry a screen occurs with you do i turn your preferred period of any signs of their console back of. Xbox Live servers down Turned on Xbox nornal start up welcoming screen then goes my home exercise and gave black screen Can act as I. Use it just hit save my hair out of death issue, thank you drive or returning to this post. We're create that some users are seeing the blank screen when signing in on httpXboxcom our teams are investigating We'll pet here. We go back in order to go to color so where a blank screen design. It can do you have a blank loading menu in our own. Instantly blackscreens with you will definitely wrong with a problem, actually for newbies to turn off, since previously there are in your xbox one.
    [Show full text]
  • IBM PC (5150) the BIOS (Basic Input/Output August 12Th Aug
    The only proprietary part was IBM PC (5150) the BIOS (Basic Input/Output August 12th Aug. 12, 1981 System), but IBM published enough of its technical details At the NYC Waldorf-Astoria, and that other manufacturers could Dorothy Elizabeth in Boca Raton, Florida, IBM eventually create PC released the IBM PC (aka the compatibles; the so-called Denning IBM 5150). It had been “clones”. developed in under a year by the In 1982, the MPC 1600-1 [June Born: Aug. 12, 1945; “Project Chess” [Oct 20] team 00] and the Compaq Portable Michigan ??, USA led by Don Estridge [June 23]. [Nov 4] were announced, and in In the mid 1980s, Denning and It featured an Intel 8088 CPU 1984, Phoenix Technology’s Peter G. Neumann developed the [July 1], 16 KB of RAM, and a released a legal copy of the BIOS Intrusion Detection Expert mono display. It used a tape [July 10]. The clone market System (IDES) that went on to cassette drive for external helped solved the PC's price become the basis for many memory, but this was later problem, through competition. cyber-security applications. It replaced by (a rather costly) The PC's popularity did have one employed a rule-based system to 5.25-inch floppy disk drive. detect problems, along with a major drawback – any non- statistical anomaly component clones aimed at the home or based on profiles of users and small business markets quickly systems. dropped from favor, and disappeared. Denning was one of several academics asked to review the The IBM PC could run several Skipjack encryption algorithm different OSes, but Microsoft’s for the Clipper chip [April 16].
    [Show full text]
  • Troubleshooting and Recovering from Problems
    Microsoft Windows 7 Unleashed, Paul McFedries, Sams Publishing, 0672330695, July, 201 CHAPTER 21 IN THIS CHAPTER . Troubleshooting Strategies: Troubleshooting and Determining the Source of a Problem Recovering from . General Troubleshooting Tips Problems . More Troubleshooting Tools . Troubleshooting Using Online Resources If it was so, it might be; and if it were so, it would be; but as it isn’t, it ain’t. That’s logic. Recovering from a Problem —Lewis Carroll A long time ago, somebody proved mathematically that it was impossible to make any reasonably complex software program problem-free. As the number of variables increase, as the interactions of subroutines and objects become more complex, and as the underlying logic of a program grows beyond the ability of a single person to grasp all at once, errors inevitably creep into the code. Given Windows 7’s status as possibly the most complex software ever created, the bad news is that there are certainly problems lurking in the weeds. However, the good news is that the overwhelm- ing majority of these problems are extremely obscure and appear only under the rarest circumstances. This doesn’t mean that you’re guaranteed a glitch-free computing experience—far from it. Third-party programs and devices cause the majority of computer woes, either because they have inherent problems themselves or because they don’t get along well with Windows 7. Using software, devices, and device drivers designed for Windows 7 can help tremendously, as can the maintenance program I outlined in Chapter 7, “Maintaining Your Windows 7 System.” But computer problems, like the proverbial death and taxes, are certainties in life, so you need to know how to troubleshoot and resolve the problems that will inevitably come your way.
    [Show full text]
  • How Do I Use Windbg Debugger to Troubleshoot a Blue Screen of Death?
    How do I use WinDBG Debugger to troubleshoot a Blue Screen of Death? Have you ever wondered how to obtain extra information from the infamous Blue Screen of Death (BSOD) that will sometimes show up and give you a cryptic, Stop: 0x00000000 error message, before flashing off the screen. The error message is trying to point you to a fatal operating system error that could be caused by a number of problems. Microsoft's WinDBG will help you to debug and diagnose the problem and then lead you to the root cause so you can fix it. Steps in a nutshell The first step is to create and capture the memory dump, associated with the BSOD you are trying to troubleshoot. The second step is to install and configure WinDBG and the Symbols path to the correct Symbols folder. We can then use WinDBG to Debug and analyze the screen dump, and then get to the root cause of the problem. Create memory dump Keep in mind that if you are not experiencing a blue screen fatal system error, there will be not memory dump to capture. 1. Press the WinKey + Pause 2. Click Advanced and under Start up and Recovery select Settings. 3. Uncheck Automatically restart. 4. Click on the dropdown arrow under Write debugging information. 5. Select Small memory dump (64 KB) and make sure the output is %SystemRoot%\Minidump. 6. Restart the PC normally as this will allow the System to error and Blue Screen and then create the Minidump. The location of the Minidump Files can be found here: C:\WINDOWS\Minidump\Mini000000-01.dmp To download and install the Windows debugging tools for your version of Windows, visit the Microsoft Debugging Tools Web.
    [Show full text]
  • Troubleshooting
    Chapter 33 Troubleshooting IN THIS CHAPTER: I The SECRETS Rule of Three I Error messages explained I Oddities on the screen I Startup troubles I Disk troubles I File, desktop, and icon ailments I Keyboard snafus PRINCIPLES OF TROUBLESHOOTING The Macintosh has an infinite number of cooks. There are the programmers at Apple who wrote the system software. There are the programmers who wrote the software you use, including the extensions and control panels that modify the system software. And then there’s the hardware, complete with a number of additional software elements (in the ROM chips, for example), both from Apple and other companies. With so many instructions being shouted at it, no wonder the Mac can get flustered and throw up its hands in frustration. The problems you may encounter vary: 1047 1048 Part IV: Attachments I Mysterious system crashes or freezes I Error messages I Startup problems (the blinking question mark icon or the Sad Mac icon) I Application problems, when the Mac simply doesn’t do what it’s sup- posed to I Printing troubles I Disk problems (their icons don’t show up on the desktop or the Mac reports that they’re “not a Macintosh disk”) A word about troubleshooting There’s a certain emotional element to a Mac going wrong. The Mac, after all, is betraying you, usually at a moment when you can least afford it. We don’t know about you, but when our Macs go goofy, we feel a rising well of frustra- tion and loss of control. Our heart rate doesn’t go back to normal until some semblance of normal operation has returned.
    [Show full text]
  • Error Messages
    Error Messages TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... Misc ................................................................................................................................................ Error Messages .......................................................................................................................... 1 General Error Messages ......................................................................................................... 2 General Command Parameter Parser .................................................................................... 18 Debugger and In-Circuit Emulator ......................................................................................... 48 Error Messages Related to the Peripheral View (PER) 48 Error Messages Related to FLASH Programming 50 Error Messages Related to Co-Processor Debugging 54 Error Messages Related to HiPerLoad 55 Error Messages Related to FDX 56 Error Messages Related to Terminal Function 57 Error Messages Related to RTOS Support 58 Error Messages Related to Differential Download 60 Error Messages Related to Breakpoints 61 Error Messages Related to Debugging 71 Error Messages Related to Debug Hardware and Software 81 Error Messages Related to Analyzer/Trace 84 Error Messages Related to MCDS 86 Error Messages Related to Trace Testfocus/Autofocus 87 Error Messages Related to APU API 90 HLL Expression
    [Show full text]
  • IBM Security Directory Server: Troubleshooting Guide Operation Times out
    IBM Security Directory Server Version 6.3.1 Troubleshooting Guide GC27-2752-01 IBM Security Directory Server Version 6.3.1 Troubleshooting Guide GC27-2752-01 Note Before using this information and the product it supports, read the general information under “Notices” on page 147. Edition notice Note: This edition applies to version 6.3.1 of IBM Security Directory Server licensed program (product number 5724-J39 ) and to all subsequent releases and modifications until otherwise indicated in new editions. Contents Figures ..............vii Installation with the installation wizard ....28 Uninstallation with the installation wizard . 32 Tables ...............ix Chapter 5. Migration issues ......33 About this publication ........xi Migration log files ............33 Kerberos service name...........33 Access to publications and terminology .....xi Database instance or database in configuration file Accessibility ..............xii but no longer on system ..........33 Technical training ............xiii Format of backed-up schema files is incorrect . 34 Support information ...........xiii ibm-slapdPlugin entry in configuration file changed 34 Statement of Good Security Practices .....xiii Considerations for migration ........34 Chapter 1. Introduction to problem Chapter 6. Instance creation and determination and troubleshooting . 1 configuration issues .........37 Directory server overview ..........1 Instance creation overview and common errors . 37 Built-in troubleshooting features ........1 Instance creation overview ........37 Tools for troubleshooting a directory server instance 1 Cannot create another instance because of invalid Error Message Reference ..........2 IP address ..............38 Information about troubleshooting .......2 idssethost command does not recognize second IP address ..............38 Chapter 2. Utilities for logging .....5 Two directory instances use the same port number...............39 Chapter 3. Other diagnostic tools .
    [Show full text]
  • Blue Screen of Death (BSOD)
    Blue Screen Of Death (BSOD) The Blue Screen of Death (also known as BSoD or Blue Screen), known officially as a Stop Error or a bug check, is the error screen displayed by the Microsoft Windows family of operating systems upon encountering a critical error, of a non-recoverable nature, that causes the system to crash. The term is named after the color of the screen generated by the error. In Unix-based operating systems, a similar term is kernel panic. Stop errors are hardware or driver related, causing the computer to stop responding in order to prevent damage to the hardware or data. In the later versions of Windows (Windows NT and later) the screen presents information for diagnostic purposes that was collected as the operating system performed a bug check. Blue Screen Of Death (BSOD) – Explained, Causes & Solution 1.(stop code 0X000000BE) Attempted Write To Readonly Memory Possible causes and solutions: This symptom is caused by a driver or program, or a service, such as some files corrupted file error drivers in different versions. To uninstall the program to fix that before this problem occurs. If a driver went to roll back drivers for older drivers or applied to the last (if later). If they service the us open before a problem occurs, turn off or disable it! 2.(stop code 0X000000C2) Bad Pool Caller Possible causes and solutions: This is similar to the above but focus their hardware is caused by the different countries, such as South grade Hardware ram, the card is not compatible with XP harddisk solution, remove the device that South grade.
    [Show full text]