solaris console login: root
Password:
No utmpx entry. You must exec “login” from the lowest level “shell”.

If you encounter this error, login with a regular user, become root and clear the file /var/adm/wtmpx

root@solaris:/var/adm # ls -l wtmpx
-rw-r–r– 1 adm adm 84505380 Jul 4 08:52 wtmpx

root@solaris:/var/adm # > wtmpx

To stop eTrust Access Control, use secons -s

root@solaris:/ # /usr/seos/bin/secons -s
eTrust secons v5.30 (5.30) – Console Utility
Copyright 2003 Computer Associates International, Inc.
eTrust is now DOWN !!!

To start it, use seload

root@solaris:/ # /usr/seos/bin/seload
eTrust seload v5.30 (5.30) – Loader Utility
Copyright 2003 Computer Associates International, Inc.
eTrust kernel extension is already loaded.
Starting eTrust daemon. (/usr/seos/bin/seosd)
18 Jul 2010 11:59:48> WAKE_UP : Server going up
18 Jul 2010 11:59:48> INFO : Filter Mask: ‘WATCHDOG*’ is registered
18 Jul 2010 11:59:48> INFO : Filter Mask: ‘INFO : Setting PV*’ is registered
18 Jul 2010 11:59:48> INFO : Filter Mask: ‘INFO : DB*’ is registered
18 Jul 2010 11:59:48> INFO : Filter Mask: ‘*seosd.trace*’ is registered
18 Jul 2010 11:59:48> INFO : Filter Mask: ‘*FILE*secons*(*/log/*)*’ is registered
Starting seosd. PID = 8115.
Starting seagent. PID = 8117
Starting seoswd. PID = 8137
seagent: Loading database image…
Executing [daemons] command: /usr/seos/bin/serevu
seagent: Initialization phase completed
Starting serevu. PID = 8141
serevu: Multiple instances of serevu are not allowed.

I was having some I/O errors in filesystems below /var

root@solaris:~ # df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 7.7G 4.9G 2.7G 64% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 39G 1.2M 39G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
/platform/SUNW,Sun-Fire-T200/lib/libc_psr/libc_psr_hwcap1.so.1
7.7G 4.9G 2.7G 64% /platform/sun4v/lib/libc_psr.so.1
/platform/SUNW,Sun-Fire-T200/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
7.7G 4.9G 2.7G 64% /platform/sun4v/lib/sparcv9/libc_psr.so.1
fd 0K 0K 0K 0% /dev/fd
/dev/md/dsk/d50 15G 2.2G 13G 15% /var
swap 2.0G 2.2M 2.0G 1% /tmp
df: cannot statvfs /var/run: I/O error
/dev/md/dsk/d140 11G 8.9G 2.0G 82% /sites
/dev/md/dsk/d60 7.7G 2.7G 4.9G 37% /opt
/dev/md/dsk/d90 963M 1.0M 904M 1% /logs
/dev/md/dsk/d85 963M 3.3M 902M 1% /home
/dev/md/dsk/d110 963M 730M 175M 81% /u01
df: cannot statvfs /var/mqm: I/O error
df: cannot statvfs /var/crash: I/O error

I was able to enter the directory /var but I was not able to list anything.

root@solaris:~ # cd /var
cd: error retrieving current directory: getcwd: cannot access parent directories: I/O error

root@solaris:/var # ls -al
.: I/O error

On the console I was seeing the error from makeutx

Jul 22 21:53:41 svc.startd[9669]: makeutx failed, retrying: I/O error
Jul 22 21:53:42 svc.startd[9669]: makeutx failed, retrying: No such file or directory

I decided to umount the filesystem and mount it again and my error disappeared

root@solaris:/root # umount /var
root@solaris:/root # df -h /var
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 7.7G 4.9G 2.7G 64% /

root@solaris:/root # mount /var
root@solaris:/root # df -h /var
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d50 15G 2.2G 13G 15% /var

root@solaris:/ # luxadm probe
No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):
(Removed to show only the tape devices)
Node WWN:500104f0009429c3 Device Type:Tape device
Logical Path:/dev/rmt/0n
Node WWN:500104f0009429c6 Device Type:Tape device
Logical Path:/dev/rmt/7n
Node WWN:500104f0009429c9 Device Type:Tape device
Logical Path:/dev/rmt/9n
Node WWN:500104f0009429cc Device Type:Tape device
Logical Path:/dev/rmt/11n

This drive showed the status of the tape drive

root@solaris:/ # mt -f /dev/rmt/7n status
HP Ultrium LTO 3 tape drive:
sense key(0×0)= No Additional Sense residual= 0 retries= 0
file no= 0 block no= 0

This drive shows that no tape is loaded or the drive is offline.

root@solaris:/ # mt -f /dev/rmt/9n status
/dev/rmt/9n: no tape loaded or drive offline

root@solaris:/ # passwd emerson
New Password:
Re-enter new Password:
passwd: System error: no files password for emerson.
Permission denied

In this case there was a problem in the /etc/passwd file. There was a blank line between two users.

If you need to know the if a release of an Unix operating system is still supported by the vendor, check these links for information

End of life information about HP-UX (PDF)

End of life information about Solaris

End of life information about AIX

End of life information about Red Hat Enterprise Linux

End of life information about Suse Linux Enterprise

Installing HP Server Automation client for Solaris. For Solaris I included the flag –withrpm to have installation of software from Opsware enabled

root@solaris:/tmp # ./opsware-agent-34c.0.0.135-solaris-5.10 -s -o -c –loglevel info –logfile /var/tmp/log.txt –withrpm –opsw_gw_addr_list 148.95.133.132:3001 –force_new_device

[INFO] Log started.

[WARN] The command-line parameter –clean has been deprecated.
Will check the gateway list for connectivity
[INFO] Opsware Gateway (148.95.133.132:3001) available at ’148.95.133.132:3001′.

[INFO] legacy config file ‘/var/lc/cogbot/etc/cogbot.args’ not found – skipping force –withrpm check.

UnZipSFX 5.42 of 14 January 2001, by Info-ZIP (Zip-Bugs@lists.wku.edu).
inflating: /tmp/~7119-1.WRK/opsware-agent
inflating: /tmp/~7119-1.WRK/opsware-agent-installer.py
creating: /tmp/~7119-1.WRK/crypto/agent/
inflating: /tmp/~7119-1.WRK/crypto/agent/agent.srv
inflating: /tmp/~7119-1.WRK/README
inflating: /tmp/~7119-1.WRK/install_opswagentrpm.sh
inflating: /tmp/~7119-1.WRK/install_rpm.sh
inflating: /tmp/~7119-1.WRK/install_syncbot.sh
inflating: /tmp/~7119-1.WRK/ISMsyncb0.pkg
inflating: /tmp/~7119-1.WRK/OPSWrpm-32h.0.0.2-1.pkg
inflating: /tmp/~7119-1.WRK/opswagentrpm.rpm
inflating: /tmp/~7119-1.WRK/opswagentrpm.sun4us.rpm

[INFO] Installing Opsware agent into ‘/opt/opsware/agent’.

[INFO] Agent uninstaller script copied successfully.

[INFO] Installation completed successfully.

[INFO] Checking for restorations at ‘/tmp/~7119-1.WRK/cog_extension’

[INFO] Registering server with the Opsware core.

[INFO] Writing no_full_hw_reg_requested file: /var/opt/opsware/agent/no_full_hw_reg_requested

[INFO] Successfully created no_full_hw_reg_requested file: /var/opt/opsware/agent/no_full_hw_reg_requested
INFO: Startup of initial hardware registration at ’05/26/10 11:09:59′
INFO: No crypto found, using bootstrap crypto.
TRACE: bootstrap crypto path: /var/opt/opsware/crypto/agent/bootstrap
TRACE: copy /var/opt/opsware/crypto/agent/bootstrap/agent.srv to /var/opt/opsware/crypto/agent/agent.srv
TRACE: flushing the certmaster cache
INFO: Checking with spin to see about clearing mid and/or crypto…
TRACE: check that ‘/etc/opt/opsware/agent/mid’ exists: 0
INFO: no mid file was found at: ‘/etc/opt/opsware/agent/mid’ assuming new install.
TRACE: bootstrap crypto path: /var/opt/opsware/crypto/agent/bootstrap
TRACE: remove: /var/opt/opsware/crypto/agent/agent.srv
TRACE: copy /var/opt/opsware/crypto/agent/bootstrap/agent.srv to /var/opt/opsware/crypto/agent/agent.srv
TRACE: flushing the certmaster cache
INFO: Initially registering hardware and operating system information…
Retrieved Machine ID is null.
Chassis ID: 847e3198
TRACE: Connecting to ‘https://spin:1004/spinrpc.py’…
Opsware machine ID : ’415820499′
Received ‘agent-ca.crt’.
Received ‘opsware-ca.crt’.
Received ‘cogbot.srv’.
Storing ‘cogbot.srv’ contents as ‘agent.srv’
Received ‘admin-ca.crt’.

[INFO] Minimal server registration completed successfully.

[INFO] Registering Opsware agent with the Opsware core.

[INFO] Writing no_sw_reg_requested file: /var/opt/opsware/agent/no_sw_reg_requested

[INFO] Successfully created no_sw_reg_requested file: /var/opt/opsware/agent/no_sw_reg_requested

[INFO] Writing do_check_reachability file: /var/opt/opsware/agent/do_check_reachability

[INFO] Successfully created do_check_reachability file: /var/opt/opsware/agent/do_check_reachability

[INFO] Starting Opsware agent.
Starting agent
Daemonbot: Wed May 26 11:10:01 2010: Looks like nothing is listening on :1002
Daemonbot: Wed May 26 11:10:01 2010: Daemonbot confirms that nothing is listening on :1002
Daemonbot: Wed May 26 11:10:01 2010: Daemonbot will try and start a new shadowbot…
Daemonbot: Wed May 26 11:10:01 2010: Starting /opt/opsware/agent/pylibs/shadowbot/daemonbot.pyc…
Daemonbot: Wed May 26 11:10:01 2010: pidpath /var/opt/opsware/agent
Daemonbot: Wed May 26 11:10:01 2010: logpath /var/log/opsware/agent
Daemonbot: Wed May 26 11:10:01 2010: ports ['1002']
Daemonbot: Wed May 26 11:10:01 2010: Started process group 7160

[INFO] Opsware agent started.

[INFO] Log ended.

The storage team created new LUNs and presented them to the server. I need to check which disks doesn’t have a label yet

root@solaris:~ # echo | format | more
Searching for disks…done

c3t5006048449AFD297d167: configured with capacity of 11.24GB
c3t5006048449AFD297d168: configured with capacity of 11.24GB
c3t5006048449AFD297d169: configured with capacity of 11.24GB
c3t5006048449AFD297d170: configured with capacity of 11.24GB
c3t5006048449AFD297d171: configured with capacity of 11.24GB
c4t5006048449AFD298d167: configured with capacity of 11.24GB
c4t5006048449AFD298d168: configured with capacity of 11.24GB
c4t5006048449AFD298d169: configured with capacity of 11.24GB
c4t5006048449AFD298d170: configured with capacity of 11.24GB
c4t5006048449AFD298d171: configured with capacity of 11.24GB
emcpower68a: configured with capacity of 11.24GB
emcpower69a: configured with capacity of 11.24GB
emcpower70a: configured with capacity of 11.24GB
emcpower71a: configured with capacity of 11.24GB
emcpower72a: configured with capacity of 11.24GB

These disks are PowerPath devices and the only thing diferenciating them are the controllers. One path comes from c3 and the other one comes from c4. After I apply a label on the PowerPath devices, I create a new Solaris Volume Manager metadevice with metainit

root@solaris:/ # metainit d74 1 1 /dev/dsk/emcpower68c
d74: Concat/Stripe is setup

I could specify the metadevice with the options 4 1 disk 1 disk 1 disk 1 disk but I find that if I attach one by one there is less chance of error

root@solaris:/ # metattach d74 /dev/dsk/emcpower69c
d74: component is attached
root@solaris:/ # metattach d74 /dev/dsk/emcpower70c
d74: component is attached
root@solaris:/ # metattach d74 /dev/dsk/emcpower71c
d74: component is attached

Checking the metadevice and which physical disks are being used

root@solaris:~ # metastat -p d74
d74 4 1 /dev/dsk/emcpower68c \
1 /dev/dsk/emcpower69c \
1 /dev/dsk/emcpower70c \
1 /dev/dsk/emcpower71c

Creating an UFS filesystem on this metadevice

root@solaris:/ # newfs /dev/md/rdsk/d74
/dev/md/rdsk/d74: Unable to find Media type. Proceeding with system determined parameters.
newfs: construct a new file system /dev/md/rdsk/d74: (y/n)? y
/dev/md/rdsk/d74: Unable to find Media type. Proceeding with system determined parameters.
Warning: 5952 sector(s) in last cylinder unallocated
/dev/md/rdsk/d74: 94261440 sectors in 15343 cylinders of 48 tracks, 128 sectors
46026,1MB in 959 cyl groups (16 c/g, 48,00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
………………
super-block backups for last 10 cylinder groups at:
93297312, 93395744, 93494176, 93592608, 93691040, 93789472, 93887904,
93986336, 94084768, 94183200

Creating the mount point for the filesystem

root@solaris:/ # mkdir /mountpoint

Here I’m setting the read and browse properties for the directory to avoid problems if the umask is different than 022

root@solaris:/ # chmod 755 /mountpoint

I mount the filesystem and specify the metadevice

root@solaris:/ # mount /dev/md/dsk/d74 /mountpoint

root@solaris:/ # df -h /mountpoint
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d74 44G 45M 44G 1% /mountpoint

If needed, now with the filesystem mounted you can change the owner and group of this filesystem

root@solaris:/ # ls -ld /mountpoint
drwxr-xr-x 3 root root 512 jul 22 16:19 /nfein

I made this new filesystem for the DBA to hold some files. So I’m changing the owner to oracle and group to dba

root@solaris:/ # chown oracle:dba /mountpoint

root@solaris:/ # ls -ld /mountpoint
drwxr-xr-x 3 oracle dba 512 jul 22 16:19 /nfein

Check if the group xcomadm exists

root@solaris:~ # grep xcom /etc/group
xcomadm::60019:

Install XCOM by using pkgadd

root@solaris:/ # pkgadd -d /cdrom/CAXCOM.INS

The following packages are available:
1 XCOM Unicenter CA-XCOM Data Transport
(sparc) r11 0505

Select package(s) you wish to process (or ‘all’ to process
all packages). (default: all) [?,??,q]: 1

Processing package instance from

Unicenter CA-XCOM Data Transport(sparc) r11 0505

This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.

The installation of this package was previously terminated and
installation was never successfully completed.

Do you want to continue with the installation of [y,n,?] y

Unicenter CA-XCOM (TM) Data Transport (Version r11.0505 for BRIXTON)
Copyright(C) 1992, 1993, 1994, 1996 Computer Associates International, Inc.
Compatible with the SunOS 5.x release

Using as the package base directory.
## Processing package information.
## Processing system information.
6 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.

The following files are already installed on the system and are being
used by another package:
* /usr/man/man1
* /usr/man/man3
* /usr/man/man5
* /usr/man/man8

* – conflict with a file which does not belong to any package.

Do you want to install these conflicting files [y,n,?,q] n

Do you want to continue with the installation of [y,n,?] y
## Checking for setuid/setgid programs.

The following files are being installed with setuid and/or setgid
permissions:
/etc/xcomd
/usr/bin/xcom62
/usr/bin/xcomqm
/usr/bin/xcomtcp
/usr/bin/xcomtool

Do you want to install these as setuid/setgid files [y,n,?,q] y
## Processing package information.
## Processing system information.

Installing Unicenter CA-XCOM Data Transport as

## Installing part 1 of 1.
/etc/xcomd
/usr/bin/cleanlog
/usr/bin/xcom62
/usr/bin/xcomencr
/usr/bin/xcomqm
/usr/bin/xcomtcp
/usr/bin/xcomtool
/usr/include/xcom/startst.h
/usr/include/xcom/xcomapi.h
/usr/include/xcom/xcomerr.h
/usr/lib/libxcom.a
/usr/lib/libxcomcomp.a
/usr/lib/libxcomtcp.a
/usr/lib/libxcomtxpi.a
/usr/lib/xcom/libcrypto.a
/usr/lib/xcom/libssl.a
/usr/lib/xcom/openssl
/usr/lib/xcom/xcomend
/usr/lib/xcom/xcomlp
/usr/lib/xcom/xcomntfy
/usr/lib/xcom/xcompp
/usr/lib/xcom/xcompre
/usr/man/man1
/usr/man/man1/cleanlog.1
/usr/man/man1/xcom62.1
/usr/man/man1/xcomencr.1
/usr/man/man1/xcomqm.1
/usr/man/man1/xcomtcp.1
/usr/man/man1/xcomtool.1
/usr/man/man3
/usr/man/man3/xcomapi.3
/usr/man/man3/xcomqapi.3
/usr/man/man5
/usr/man/man5/xcom.cnf.5
/usr/man/man5/xcom.glb.5
/usr/man/man5/xcom.ses.5
/usr/man/man5/xcom.trusted.5
/usr/man/man8
/usr/man/man8/xcomd.8
/usr/man/man8/xcomend.8
/usr/man/man8/xcomlp.8
/usr/man/man8/xcomntfy.8
/usr/man/man8/xcompp.8
/usr/man/man8/xcompre.8
/usr/man/man8/xcomtp.8
/usr/openwin/lib/app-defaults/Xcomtool
/usr/spool/xcom/config/README
/usr/spool/xcom/config/appc.prof
/usr/spool/xcom/config/configssl.cnf
/usr/spool/xcom/config/dh1024.pem
/usr/spool/xcom/config/dh2048.pem
/usr/spool/xcom/config/dh4096.pem
/usr/spool/xcom/config/dh512.pem
/usr/spool/xcom/config/readme.html
/usr/spool/xcom/config/xcom.cnf
/usr/spool/xcom/config/xcom.glb
/usr/spool/xcom/config/xcom.ses
/usr/spool/xcom/config/xcom.tid
/usr/spool/xcom/convtab/atoe.tab
/usr/spool/xcom/convtab/etoa.tab
/usr/spool/xcom/src/apitest.c
/usr/spool/xcom/src/makefile
/usr/spool/xcom/src/qapimake
/usr/spool/xcom/src/qapitest.c
/usr/spool/xcom/ssl/cassl.conf
/usr/spool/xcom/ssl/clientssl.conf
/usr/spool/xcom/ssl/listca
/usr/spool/xcom/ssl/listclient
/usr/spool/xcom/ssl/listserver
/usr/spool/xcom/ssl/makeca
/usr/spool/xcom/ssl/makeclient
/usr/spool/xcom/ssl/makeserver
/usr/spool/xcom/ssl/serverssl.conf
/usr/spool/xcom/trusted/xcom.trusted
/usr/spool/xcom/xcom.log
[ verifying class ]

Installation of was successful.

Checking if the package was installed

root@solaris # pkginfo -l XCOM
PKGINST: XCOM
NAME: Unicenter CA-XCOM Data Transport
CATEGORY: system
ARCH: sparc
VERSION: r11 0505
BASEDIR: /
PSTAMP: usprsu1i20050520102557
INSTDATE: Nov 27 2009 12:47
STATUS: completely installed
FILES: 88 installed pathnames
6 linked files
11 directories
21 executables
5 setuid/setgid executables
27343 blocks used (approx)

To start XCOM at the startup, add the following line to /etc/inittab

xcom:3:once:/etc/xcomd

Add the ports to the /etc/services file

txpi 8044/tcp # xcom
txpis 8045/tcp # xcom (r11 only)

Add the line to /etc/inetd.conf file to make inetd listen for those XCOM request

txpi stream tcp nowait root /usr/lib/xcom/xcomtcp xcomtcp REMOTE 0
txpis stream tcp nowait root /usr/lib/xcom/xcomtcp xcomtcp REMOTE 0 SSL

On Solaris 10, run inetconv to convert the lines you just inserted into SMF service manifests

root@solaris # inetconv

If you tried to start sshd on Solaris and appeared an error message saying it couldn’t connect to PRNGD socket, you need to start this daemon first.

root@solaris6:/ # /etc/init.d/sshd start
Couldn’t connect to PRNGD socket “/var/spool/prngd/pool”: Connection refused
couldn’t read entropy commands file /usr/local/etc/ssh_prng_cmds: No such file or directory
ssh-rand-helper child produced insufficient data

Run /etc/init.d/prngd start and then start ssh again

root@solaris6:/ # /etc/init.d/prngd start

root@solaris6:/# /etc/init.d/sshd start

The daemon should be running now

root@solaris6:/ # ps -ef | grep ssh
root 19359 1 0 10:00:08 ? 0:00 /usr/local/sbin/sshd
root 19376 18089 0 10:00:13 pts/1 0:00 grep ssh