23 Jul 15 HP-UX patch depot tutorial. This is based on doing a QPK download which requires a. Compaq c700 driver download for window xp. Finally becoming the backup Unix Admin in 1998 and the full. Problem: After being Ignited superman lost most sd-ux functionality. Note: superman (not its real name) is a vpar running on a superdome complex. Only swlist works, swreg -l depot, swinstall -i, swverify all fail with the same error. ERROR: “spuerman/”: You do not have the required permissions to select this target. Check permissions using the “swacl” command or see your system administrator for assistance. Or, to manage applications designed and packaged for nonprivileged mode, see the “run_as_superuser” option in the “sd” man page. * Target connection failed for “zrtph0v0:/”. Unix Download FileAcquiring the Bundles To obtain the bundles from the web, perform the following steps for both the QPK and HWE patch bundles. Log in to the target system. Software Depot for HP-UX Software Assistant. ![]() ERROR: More information may be found in the daemon logfile on this target (default location is superman:/var/adm/sw/swagentd.log). * Selection had errors. Standard techniques say check: /sbin/init.d/swagentd stop /sbin/init.d/swagentd start Check /etc/hosts networking is consistent. Make sure /etc/nsswitch.conf is present and makes sense. Hp Unix PatchCheck permissions on /var/tmp and all the swagent files. None of this worked. Swlist -i -s $PWD in a depot generated the following error taken from ITRC because the system is already fixed.: swacl -l host @ superman List swacl generates this: Util_Random internal error: Read of /dev/urandom failed, rv=-1, size=8, No such device (19). There were a series of other errors all pointing to /dev/urandom lsdev showed that /urandom did not load the kernel module rng (Randome Number Generator). Detail root /usr/sam/tui/kc/modulemod.sh rng Detail root /usr/sbin/kcmodule -a -P ALL This is normal output. Before the system was fixed the system did not show the module running. Lsdev| grep rng 138 -1 rng pseudo Fix was to unload the rng module in the kernel (using sam SEP cheats) Then we loaded it. In spite of being listed as dynamic a reboot was required to restore sd-ux functionality. Actual source of the problem: Ignite image of supergirl did not exclude the /dev/ “files” This cause the wrong kernel module to be loaded with the /dev/urandom “file” driver. Normally this is not a problem becuase /dev is crecreated but for some reason /dev/udandom was not loading the kernel module rng Ignite excludes have been updated to exclude these files and the system will be re-ignited to make sure nothing else bad happens. This is our first case study. The events leading up to it occur between 1998 and 2002. It is a real life case study based on my experience. For legal reasons, I can not identify the organization. It is a charity that raises now around $100 million, 92% of funds raised go to actual charitable work. 8% is overhead. IT infrastructure is overhead, even though it is critical to actually raising funds. From 1991-2005 I worked at this charity in IT, first as a programmer analyst, then as a dba, finally becoming the backup Unix Admin in 1998 and the full time Unix Admin in 2000. The organization ran its legacy fund raising systems on a pair of D class HP-UX systems. The back end database was Software AG adabas. The user fund raising community wanted to have an sql like ability to look into the database and run queries. They wanted flexible use of strategic data. An attempt was made in early 1997 to install a sql front end, but it did not provide acceptable results. An internal study was done and it was decided in late 1997 to migrate legacy systems to a web based front end, with Oracle as the back end database, Oracle Application Server using forms and reports to build applications. Initially no plan was made to migrate to stronger hardware, due to the assurance from Oracle that their software would run on the existing infrastructure. By 2000 it was obvious that this was not true. Though the database server itself ran acceptably, there was not sufficient memory or disk capacity to run the application server. So I was asked to prepare a plan to migrate legacy systems. Here were the guidelines: • To run three environments, to be described below, each with a database server, an application server and forms and reports development tools on them. • Sandbox was to be used to test OS patches, Oracle patches, and tools upgrades.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2018
Categories |