Archive for category HP-UX

Glance shortcuts

To use the buttons at the bottom of the glance, you should do an "export TERM=dtterm".

After that, you will be able to use:
F1 for ProcList
F2 for CPU Rpt
F3 for Mem Rpt
F4 for Disk Rpt
F5 for NextKeys
F6 for SlctProc
F7 for Help
F8 for Exit

 

, ,

No Comments

Control agent problem (OVO)

Sometimes the OVO agent stops communicating with the OVO Server.

Control agent on nodeHOST isn't accessible. (OpC40-405) Network communication problem: Could not obtain endpoint information from node ncadg_ip_udp:10.0.0.10[]. (OpC40-399)

To reestablish the communication, you should restart it:

To stop, use the command:

/opt/OV/bin/OpC/opcagt -stop

Check if it is stopped:

/opt/OV/bin/OpC/opcagt -status
ITO Managed Node status :
-------------------------
Control Agent /opt/OV/bin/OpC/opcctla               (3818) is running
Message Agent /opt/OV/bin/OpC/opcmsga               (3819) is running
Subagent 1:
Action Agent /opt/OV/bin/OpC/opcacta                (3820) is running
Logfile Encapsulator /opt/OV/bin/OpC/opcle          (3821) is running
Monitor Agent /opt/OV/bin/OpC/opcmona               (3822) is running
Message Interceptor /opt/OV/bin/OpC/opcmsgi         (3823) is running

Attention: the "Control Agent" may not stop, you can kill it with a "kill -9 PID"

To start, use the command:

/opt/OV/bin/OpC/opcagt -start

, ,

No Comments

Check powerpath links in HP-UX

To check if the powerpath links are up in HP-UX, you can use the following command:

powermt display dev=all

, , ,

No Comments

When Glance stop working

Sometimes glance (performance monitor for HP-UX) can crash (before crash, it will return 0% of CPU, Disk and networking) working with the following error:

GlancePlus fatal error.
== Fatal Nums Error == C.04.50.57 02/10/07 ==
User: root/6pts/6(/dev/pts/6) Date: Sun Dec 6 15:52:12
File: /crm/numsVob/hp/11.0/nums.C Line: 485 Product id: Glance
System: server B.11.11 9000/800
Errno: 0 (Error 0)
Connection to midaemon lost — check midaemon process and status.mi == End of Error Msg
=============================

To solve it, you should:

Stop MWA:

mwa stop

Remove all files (including the hidden ones) from /var/opt/perf/datafiles:

rm -rf /var/opt/perf/datafiles/* rm -rf /var/opt/perf/datafiles/.*

Check if midaemon and ttd are stopped:

mwa status

If midaemon and ttd didn’t stop, force stops them with the command kill (the PID was returned by the command ‘mwa status’).

Now, start MWA again:

mwa start

,

No Comments

Lock an user account in HP-UX

To lock an user account in HP-UX, you can use the following command:

/usr/lbin/modprpw -m alock=YES USER

, ,

No Comments

Merge many depots

When you have many depot files, you can create a single big depot and install it instead of install one by one.

Let’s assume that you need install the following depots, and they are all located in the directory /tmp/install/depots:

autoconf-2.64-hppa-11.11.depot
bison-2.4.1-hppa-11.11.depot
gawk-3.1.7-hppa-11.11.depot
sed-4.2.1-hppa-11.11.depot
tcltk-8.5.7-hppa-11.11.depot
texinfo-4.13-hppa-11.11.depot
zip-3.0-hppa-11.11.depot

To create a single depot, run the follow commands:

cd /tmp/install/
for i in `ls depots/*.depot` ;do swcopy -s /tmp/install/$i \* @/tmp/install/big;done

Now, to install it, you can use:

swinstall -s /tmp/install/big

, , ,

No Comments

HP-UX password maintenance

Follow a few utilities to maintain the user’s passwords:

/usr/lbin/getprpw <username>- display protected password database
/usr/lbin/modprpw –x <username> – change password
/usr/lbin/modprpw –k <username> – unlock the user

No Comments

Hardware specification in HP-UX

You can use the following command to check the HP-UP hardware (like CPU and memory):

hpuxhost@root:/root # print_manifest |more

System Information

Your Hewlett-Packard computer has software installed and

configured as follows.

The system was created July 04, 2007, 11:53:28 EDT.

It was created with Ignite-UX revision C.6.10.97.

————————————————————-

NOTE: You should retain this information for future reference.

————————————————————-

System Hardware

Model: 9000/800/SD32A

Main Memory: 65005 MB

Processors: 32

Proccesor(0) Speed: 1000 MHz

Proccesor(1) Speed: 1000 MHz

Proccesor(2) Speed: 1000 MHz

Proccesor(3) Speed: 1000 MHz

Proccesor(4) Speed: 1000 MHz

Proccesor(5) Speed: 1000 MHz

Proccesor(6) Speed: 1000 MHz

Proccesor(7) Speed: 1000 MHz

Proccesor(8) Speed: 1000 MHz

Proccesor(9) Speed: 1000 MHz

Proccesor(10) Speed: 1000 MHz

Proccesor(11) Speed: 1000 MHz

Proccesor(12) Speed: 1000 MHz

Proccesor(13) Speed: 1000 MHz

Proccesor(14) Speed: 1000 MHz

Proccesor(15) Speed: 1000 MHz

Proccesor(16) Speed: 1000 MHz

Proccesor(17) Speed: 1000 MHz

Proccesor(18) Speed: 1000 MHz

Proccesor(19) Speed: 1000 MHz

Proccesor(20) Speed: 1000 MHz

Proccesor(21) Speed: 1000 MHz

Proccesor(22) Speed: 1000 MHz

Proccesor(23) Speed: 1000 MHz

Proccesor(24) Speed: 1000 MHz

Proccesor(25) Speed: 1000 MHz

Proccesor(26) Speed: 1000 MHz

Proccesor(27) Speed: 1000 MHz

Proccesor(28) Speed: 1000 MHz

Proccesor(29) Speed: 1000 MHz

Proccesor(30) Speed: 1000 MHz

Proccesor(31) Speed: 1000 MHz

(…) Many other HW information above

No Comments

Recovering corrupted lvol on HP-UX

Sometimes you can get the following error while try to access a directory in HP-UX:

hpuxbox@root:/root # cd /DATA

sh: /DATA: The specified directory is not valid.


This error is caused because the file system is corrupted and you need run fsck on it.

First of all, umount the FS:

hpuxbox@root:/root # umount /DATA


And them, run the fsck:

hpuxbox @root:/root # fsck -y -o full /dev/vgLOG/lvol1on clear? (ynq)y

UX:vxfs fsck: WARNING: V-3-20836: file system had I/O error(s) on meta-data.

log replay in progress

pass0 – checking structural files

pass1 – checking inode sanity and blocks

fileset 999 primary-ilist inode 177502 marked bad, allocation flags (0×0001)

fileset 999 primary-ilist inode 177502 has invalid number of blocks (7309)

fileset 999 primary-ilist inode 177502 has invalid block map

fileset 999 primary-ilist inode 177502 failed validation clear? (ynq)y

fileset 999 primary-ilist inode 177859 marked bad, allocation flags (0×0001)

fileset 999 primary-ilist inode 177859 has invalid number of blocks (24850)

fileset 999 primary-ilist inode 177859 has invalid block map

fileset 999 primary-ilist inode 177859 failed validation clear? (ynq)y

fileset 999 primary-ilist inode 178243 marked bad, allocation flags (0×0001)

fileset 999 primary-ilist inode 178243 has invalid number of blocks (6417)

fileset 999 primary-ilist inode 178243 has invalid block map

fileset 999 primary-ilist inode 178243 failed validation clear? (ynq)y

fileset 999 primary-ilist inode 178793 marked bad, allocation flags (0×0001)

fileset 999 primary-ilist inode 178793 failed validation clear? (ynq)y

pass2 – checking directory linkage

pass3 – checking reference counts

pass4 – checking resource maps

fileset 999 au 2 imap incorrect – fix (ynq)y

fileset 999 au 2 iemap incorrect – fix (ynq)y

au 42 emap incorrect – fix? (ynq)y

au 42 summary incorrect – fix? (ynq)y

au 59 emap incorrect – fix? (ynq)y

au 59 summary incorrect – fix? (ynq)y

au 60 emap incorrect – fix? (ynq)y

au 60 summary incorrect – fix? (ynq)y

au 61 emap incorrect – fix? (ynq)y

au 61 summary incorrect – fix? (ynq)y

au 62 emap incorrect – fix? (ynq)y

au 62 summary incorrect – fix? (ynq)y

au 63 emap incorrect – fix? (ynq)y

au 63 summary incorrect – fix? (ynq)y

fileset 999 iau 2 summary incorrect – fix? (ynq)y

free block count incorrect 2153192 expected 2202289 fix? (ynq)y

free extent vector incorrect fix? (ynq)y

OK to clear log? (ynq)y

set state to CLEAN? (ynq)y


After that, you can mount the FS again.

hpuxbox@root:/root # umount /DATA

,

No Comments

Listing installed packages in HP-UX

To list all installed packages on HP-UX, you can use the following command:

swlist -l

,

No Comments

SSH Memory fault(coredump) in HP-UX

If you try to access from a HP-UX another machine that has a newer version of SSH running, you may get a “SSH Memory fault(coredump)” message like the following one:

root@serverHPUX01:/ > ssh -v serverDebian
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0×0090609f
16153: debug1: Reading configuration data /opt/ssh/etc/ssh_config16153: debug1: Rhosts Authentication disabled, originating port will not be trusted.16153: debug1: ssh_connect: needpriv 0
16153: debug1: Connecting to serverDebian [10.0.0.1] port 22.16153: debug1: Connection established.16153: debug1: identity file /.ssh/id_rsa type -116153: debug1: identity file /.ssh/id_dsa type -116153: debug1: Remote protocol version 1.99, remote software version OpenSSH_4.2-chrootssh16153: debug1: match: OpenSSH_4.2-chrootssh pat OpenSSH*
16153: debug1: Enabling compatibility mode for protocol 2.0
16153: debug1: Local version string SSH-2.0-OpenSSH_3.5p1
Memory fault(coredump)

To solve it, you should create a empty file named /etc/krb5.conf in HP-UX. After that, you will be able to use SSH

No Comments