Author: Emerson .

evweb eventviewer -L: An error occured while executing the request. Please check log file for more details.

I was having a problem with the event viewer

root@hp-ux:~ # evweb eventviewer -L

An error occured while executing the request. Please check log file for more details.

I was instructed to check the log file /var/opt/sfm/log/sfm.log

root@hp-ux:~ # cat /var/opt/sfm/log/sfm.log
09/26/13 19:03:01 EVWEB_DB_LIB 63 WARNING 1825 15 LOGDB: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket “/tmp/.s.PGSQL.10864”?

09/26/13 19:03:01 commonLog 122 ERROR 1825 15 DB Connection failed to LOGDB…

09/26/13 19:03:01 commonLog 78 CRITICAL 1825 15 DB connection failed

09/26/13 19:17:50 UTILS 348 CRITICAL 1825 1 Thread Join Failed , Errno: 3

Then some services needed to be restarted

root@hp-ux:~ # /opt/wbem/sbin/cimserver -s
PGS10019: CIM server is stopped.
root@hp-ux:~ # usermod -s /sbin/sh sfmdb
root@hp-ux:~ # /sbin/init.d/psbdb stop
root@hp-ux:~ # /sbin/init.d/psbdb start
root@hp-ux:~ # /opt/wbem/sbin/cimserver
root@hp-ux:~ #

Delete events showing in evweb eventviewer

If your event log is getting full

root@hp-ux:~ # evweb eventviewer -L

EvArchNo Severity Event # Event Category Archive Time Summary
========= ========= ============== ============== =================== ==============================
17820 Critical 187 Secondary S… 2013-09-26 14:08:51 An attempt to probe existin…
17819 Critical 187 Secondary S… 2013-09-26 14:08:48 An attempt to probe existin…
17818 Critical 187 Secondary S… 2013-09-26 14:08:46 An attempt to probe existin…
17817 Critical 187 Secondary S… 2013-09-26 14:08:44 An attempt to probe existin…
17816 Critical 187 Secondary S… 2013-09-26 13:36:04 An attempt to probe existin…
17815 Critical 187 Secondary S… 2013-09-26 13:35:58 An attempt to probe existin…
17814 Critical 187 Secondary S… 2013-09-26 13:35:56 An attempt to probe existin…
17813 Critical 187 Secondary S… 2013-09-26 13:35:54 An attempt to probe existin…
17812 Critical 187 Secondary S… 2013-09-26 13:32:44 An attempt to probe existin…
17811 Critical 187 Secondary S… 2013-09-26 13:32:38 An attempt to probe existin…
17810 Critical 187 Secondary S… 2013-09-26 13:32:36 An attempt to probe existin…
17809 Critical 187 Secondary S… 2013-09-26 13:32:34 An attempt to probe existin…
17808 Critical 187 Secondary S… 2013-09-26 13:29:14 An attempt to probe existin…
17807 Critical 187 Secondary S… 2013-09-26 13:28:23 An attempt to probe existin…
17806 Critical 187 Secondary S… 2013-09-26 13:28:21 An attempt to probe existin…
17805 Critical 187 Secondary S… 2013-09-26 13:28:19 An attempt to probe existin…

You can delete all the events running the command below. If you put -f it won’t ask you to delete the events

root@hp-ux:~ # evweb eventviewer [-f] -D
Are you sure you want to delete the event(s) (y/n)? [n]:
y

The execution of command was successful.

Run evweb eventviewer -L to list the events

root@hp-ux:~ # evweb eventviewer -L

EvArchNo Severity Event # Event Category Archive Time Summary
========= ========= ============== ============== =================== ==============================

HP Data Protector – What devices are visible to the host

To check what devices are visible to the host use devbra

root@hp-ux:~ # whereis devbra
devbra: /opt/omni/lbin/devbra

Check version

root@hp-ux:~ # /opt/omni/lbin/devbra
HP Data Protector A.06.20: DEVBRA, internal build 407, built on Fri Oct 19 07:46:26 2012

HP Data Protector Operations Guide – To verify what devices are visible to the host, use the following command line option

Sample:

root@hp-ux:~ # /opt/omni/lbin/devbra -dev
Exch HP:ESL E-Series Path: “/dev/rchgr/autoch8” SN: “HPE154132113”
Description: HP StorageWorks ESL E-Series
Revision: 7.60 Flags: 0x0006 Slots: 300 Drives: 8
Drive(s) SN:
“HU1214MWT0”
“HU1219NE35”
“HU1219NE2Q”
“HU1214MWRQ”
“HU1214MWT1”
“HU1219NE2U”
“HU1219NE2H”
“HU1218NA4S”

Tape HP:Ultrium 5-SCSI Path: “/dev/rtape/tape265_BESTn” SN: “HU1219NE2U”
Description: HP LTO drive
Revision: I5EW Device type: lto [13] Flags: 0x0101

Tape HP:Ultrium 5-SCSI Path: “/dev/rtape/tape266_BESTn” SN: “HU1218NA4S”
Description: HP LTO drive
Revision: I5EW Device type: lto [13] Flags: 0x0101

HP MP / ILO: Sorry, LAN Console access is currently disabled

When you try to access the Management Processor of an HP Integrity server and receive the message Sorry, LAN Console access is currently disabled

user@hostname:~ $ telnet ilo_ip_address
Trying 10.0.0.120…
Connected to 10.0.0.120.
Escape character is ‘^]’.

Sorry, LAN Console access is currently disabled.
Connection to 10.0.0.120 closed by foreign host.

You need to enable telnet and/or ssh according to the picture below. Access using a browser on the same IP address of the MP.
Integrity ILO Access Settings

Discover the IP address of ILO in a HP Integrity server

Example from an HP Integrity RX2660

root@hp-ux:~ # /opt/propplus/bin/cprop -detail -c “Management Processor”

[Component]: Management Processor
[Table]: Management Processor
——————————————————-
****************************************************
[Hash ID]: Management Processor:635bdafbx146dde57
< ClassName:HP_ManagementProcessor NameSpace:root/cimv2 >
[UniqueIdentifier]: 0.34.100.148.155.53
[ControllerType]: Unknown
[IPAddress]: 10.32.32.148
[URL]: https://10.32.32.148
[Dedicated]: Management
[CreationClassName]: HP_ManagementProcessor
[Name]: Management Processor
[EnabledState]: Enabled
[OperationalStatus]: OK
[FirmwareRevision]: F.002.026.000
[LEDColour]: 0
[LEDBlinkRate]: 0
[NICCondition]: 2
****************************************************
——————————————————-

This following example is a little different. This is to reset a GSP for HP 9000 rp5400 (L1000) Server

root@hp-ux_pa-risc:~ # ioscan -fnC tty
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
tty 0 0/0/4/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/mux0 /dev/tty0p1
/dev/diag/mux0 /dev/tty0p0 /dev/tty0p2
tty 1 0/0/5/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag2 /dev/diag/mux1 /dev/mux1 /dev/tty1p1

root@hp-ux_pa:~ # stty +queryGSP < /dev/GSPdiag1
GSP is functional.

root@hp-ux_pa:~ # stty +resetGSP < /dev/GSPdiag1
GSP reset succeeded.

Installing HP-UX SysInfo

Download the depot file from The “Official” SysInfo Page

I copied the file to /tmp

root@hp-ux:/tmp # cd /tmp
root@hp-ux:/tmp # gunzip SysInfo.7.12a.depot.gz
root@hp-ux:/tmp # swinstall -s /tmp/SysInfo.7.12a.depot SysInfo

======= 08/30/13 13:47:52 EDT BEGIN swinstall SESSION
(non-interactive) (jobid=hp-ux-0259)

* Session started for user “root@hp-ux”.

* Beginning Selection
* Target connection succeeded for “hp-ux:/”.
* Source: /tmp/SysInfo.7.12a.depot
* Targets: hp-ux:/
* Software selections:
SysInfo.SYS-INFO,r=A.07.12a,v=HP
* Selection succeeded.
* Beginning Analysis and Execution
* Session selections have been saved in the file
“/root/.sw/sessions/swinstall.last”.
* The analysis phase succeeded for “hp-ux:/”.
* The execution phase succeeded for “hp-ux:/”.
* Analysis and Execution succeeded.
NOTE: More information may be found in the agent logfile using the
command “swjob -a log hp-ux-0259 @ hp-ux:/”.

======= 08/30/13 13:48:08 EDT END swinstall SESSION (non-interactive)
(jobid=hp-ux-0259)

You generate a text file with the -b flag or you can use -H to generate an HTML file

root@hp-ux:/tmp # /usr/bin/SysInfo -b

root@hp-ux:/tmp # /usr/bin/SysInfo -H

Maybe you wish to know about HP BSC getsysinfo.sh for HP-UX

/stand/bootconf is INCORRECT

You ran Sysinfo but received the message /stand/bootconf is INCORRECT, you need to edit the file /stand/bootconf to add the missing disk according to your configuration

=== START /stand/bootconf contents ===

l /dev/disk/disk2_p2

=== END /stand/bootconf contents ===

/stand/bootconf is missing an entry for /dev/disk/disk3_p2
– /stand/bootconf is INCORRECT and should contain the lines:

l /dev/disk/disk2_p2
l /dev/disk/disk3_p2

=== END Bootconf Data ===

The file /stand/bootconf must have both boot disks if your system is mirrored

root@hp-ux:~ # cat /stand/bootconf
l /dev/disk/disk2_p2

To verify which disk/partition is missing, type lvlnboot -v

root@hp-ux:~ # lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk2_p2 — Boot Disk
/dev/disk/disk3_p2 — Boot Disk
Boot: lvol1 on: /dev/disk/disk2_p2
/dev/disk/disk3_p2
Root: lvol3 on: /dev/disk/disk2_p2
/dev/disk/disk3_p2
Swap: lvol2 on: /dev/disk/disk2_p2
/dev/disk/disk3_p2
Dump: lvol2 on: /dev/disk/disk2_p2, 0

To update this file, you can simply edit the file

root@hp-ux:~ # vi /stand/bootconf
l /dev/disk/disk2_p2
l /dev/disk/disk3_p2

Linux server with “vpath” disks

I recently saw a Linux server connected to an IBM storage with a “vpath” disk. It is because the server uses IBM Subsystem Device Driver.

Reading the IBM System Storage Multipath Subsystem Device Driver (SDD) User’s Guide, I figured how to check the disks

root@linux:~ # datapath query device

Total Devices : 47

DEV#: 0 DEVICE NAME: vpathb TYPE: 2145 POLICY: Optimized Sequential
SERIAL: 600507680191818c1000000000000304
============================================================================
Path# Adapter/Hard Disk State Mode Select Errors
0 Host0Channel0/sda OPEN NORMAL 2059 0
1 Host0Channel0/sday OPEN NORMAL 3761 0
2 Host0Channel0/sdcw OPEN NORMAL 0 0
3 Host0Channel0/sdeu OPEN NORMAL 0 0
4 Host1Channel0/sdgs OPEN NORMAL 3122 0
5 Host1Channel0/sdiq OPEN NORMAL 2949 0
6 Host1Channel0/sdko OPEN NORMAL 0 0
7 Host1Channel0/sdmm OPEN NORMAL 0 0

Solaris 10: passwd: Password in history list

root@solaris:~ # passwd emerson
New Password:
passwd: Password in history list.

Please try again
New Password:

According to this blog post Solaris 10 Password History, Solaris 10 implemented a new parameter (HISTORY) in /etc/default/passwd. This parameter keeps all the used password to prevent password recycling.

You can set to a smaller number if you wish

root@solaris:~ # vi /etc/default/passwd
HISTORY=1

Error: pvcreate: Device /dev/mapper/software01p1 not found

When trying to run pvcreate on a partition that exists on the system, it says that device is not found.

root@linux:/ # pvcreate /dev/mapper/software01p1
Device /dev/mapper/software01p1 not found.

The device exists on the system

root@linux:/ # ls -l /dev/mapper/software01*
brw——- 1 root root 253, 7 Jul 27 10:23 /dev/mapper/software01
brw——- 1 root root 253, 8 Jul 27 10:27 /dev/mapper/software01p1

The problem was that the LVM filter is not configured to consider it as a valid device.

Edit the file /etc/lvm/lvm.conf and edit the parameter filter accordingly. I used the filter below:

root@linux:/ # vi /etc/lvm/lvm.conf
filter = [ “a|cciss/.*|” “a|/dev/mapper/.*|”, “r|/dev/sd.*|”, “r|/dev/dm-.*|” ]