setaOffice

Acessing a console of a domain in a Sun Enterprise 10K

Emerson Takahashi — Mon, 23 Aug 2010 01:22:41 +0000

Here is the procedure to reset a domain in a Sun E10K. I don’t know if there is some detail missing but here is what was done with help of my friend at work.

To access the console of a domain hosted in a Sun E10K, first you need to know which number is this domain. I grepped the /etc/hosts to find out

root@ssp:/ # grep -i e10kdomain1 /etc/hosts
192.168.8.35 e10kdomain1 dom07 # 10.10.12.17 SB 06

Become the user ssp and enter the domain hostname

root@ssp:/ # su – ssp
Use of this network is restricted to authorized users only. User activity may be monitored and/or recorded. Anyone using this network expressly consents to such monitoring and/or recording. BE ADVISED: if possible criminal activity is detected, these records, along with certain personal information, may be provided to law enforcement officials.

Please enter SUNW_HOSTNAME: dom07

Use netcon to connect to the console

ssp:dom07% netcon
trying to connect…
connected.
Unlocked write permission is granted.

I connected to the domain’s console and the domain is locked. To reset it, you’ll need to know the system board to turn it off. Run domain_status and check the last column

ssp:dom07% domain_status
DOMAIN TYPE PLATFORM OS SYSBDS
dom07 Ultra-Enterprise-10000 OnDemand02 5.8 6
dom10 Ultra-Enterprise-10000 OnDemand02 5.8 9
dom15 Ultra-Enterprise-10000 OnDemand02 5.8 14
dom09 Ultra-Enterprise-10000 OnDemand02 5.8 8
dom01 Ultra-Enterprise-10000 OnDemand02 5.8 0
dom02 Ultra-Enterprise-10000 OnDemand02 5.8 1
dom05 Ultra-Enterprise-10000 OnDemand02 5.8 4

To power down you issue bringup -A off and the system board that the domain is running on

ssp:dom07% bringup -A off SB 6
Trying to get bringup.lock lock… OK
Checking that all other domains are down……… NO
Bringing up domain dom07
WARNING: Host is active; filesystems may be corrupted.
Do you really wish to continue (y/n)? y
Is this command executed because of a “Hung” Host (y/n)? y
Starting: hpost
Opening SNMP server library…

Significant contents of /export/home/ssp/.postrc:
#
logfile

Using blacklist file /var/opt/SUNWssp/etc/OnDemand02/blacklist
#=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
proc 12.2 12.3
Reading centerplane asics to obtain bus configuration…
Bus configuration determined to be 3F.
phase cplane_isolate: CP domain cluster mask clear…
phase init_reset: Initial system resets…
phase jtag_integ: JTAG probe and integrity test…
phase mem_probe: Memory dimm probe…
phase iom_probe: I/O module type probe…
phase jtag_bbsram: JTAG basic test of bootbus sram…
phase proc1: Initial processor module tests…
phase pc/cic_reg: PC and CIC register tests…
phase dtag: CIC DTAG tests…
phase mem: MC register and memory tests…
phase io: I/O controller tests…
phase procmem2: Processor vs. memory II tests…
phase lbexit: Centerplane connection tests…
phase npb_mem: Non-Proc Board MC and memory tests…
phase npb_iopc: Non-Proc Board IOPC register tests…
phase npb_io: Non-Proc Board I/O controller tests…
phase npb_cplane: Non-Proc Board centerplane connection tests…
phase nmb_procmem2: Non-Mem Board Proc vs. memory II tests…
phase final_config: Final configuration…
Configuring in 3F, FOM = 8192.00: 4 procs, 4 Scards, 4096 MBytes.
Creating OBP handoff structures…
Configured in 3F with 4 processors, 4 Scards, 4096 MBytes memory.
Interconnect frequency is 99.902 MHz, from SNMP MIB.
Processor external frequency is 199.805 MHz, from SNMP MIB.
Processor internal frequency is 399.610 MHz, from proc clk_mode probe.
Boot processor is 6.0 = 24
POST (level=16, verbose=20) execution time 4:03
Boot processor 24 written to /var/opt/SUNWssp/etc/OnDemand02/dom07/bootproc
Updating domain dom07 with bootproc 24 domainInstance 0 and interrupt vector MIB… OK
Starting obp_helper -m 24 -A off… OK
Starting netcon_server -p 24 … OK

Power on the domain with bringup -A on. No need to specify the system board this time

brsbssp02:dom07% bringup -A on
Trying to get bringup.lock lock… OK
Checking that all other domains are down……… NO
Bringing up domain dom07
Starting: hpost
Opening SNMP server library…

Significant contents of /export/home/ssp/.postrc:
#
logfile

Using blacklist file /var/opt/SUNWssp/etc/OnDemand02/blacklist
#=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
proc 12.2 12.3
Reading centerplane asics to obtain bus configuration…
Bus configuration determined to be 3F.
phase cplane_isolate: CP domain cluster mask clear…
phase init_reset: Initial system resets…
phase jtag_integ: JTAG probe and integrity test…
phase mem_probe: Memory dimm probe…
phase iom_probe: I/O module type probe…
phase jtag_bbsram: JTAG basic test of bootbus sram…
phase proc1: Initial processor module tests…
phase pc/cic_reg: PC and CIC register tests…
phase dtag: CIC DTAG tests…
phase mem: MC register and memory tests…
phase io: I/O controller tests…
phase procmem2: Processor vs. memory II tests…
phase lbexit: Centerplane connection tests…
phase npb_mem: Non-Proc Board MC and memory tests…
phase npb_iopc: Non-Proc Board IOPC register tests…
phase npb_io: Non-Proc Board I/O controller tests…
phase npb_cplane: Non-Proc Board centerplane connection tests…
phase nmb_procmem2: Non-Mem Board Proc vs. memory II tests…
phase final_config: Final configuration…
Configuring in 3F, FOM = 8192.00: 4 procs, 4 Scards, 4096 MBytes.
Creating OBP handoff structures…
Configured in 3F with 4 processors, 4 Scards, 4096 MBytes memory.
Interconnect frequency is 99.902 MHz, from SNMP MIB.
Processor external frequency is 199.805 MHz, from SNMP MIB.
Processor internal frequency is 399.610 MHz, from proc clk_mode probe.
Boot processor is 6.0 = 24
POST (level=16, verbose=20) execution time 4:02
Boot processor 24 written to /var/opt/SUNWssp/etc/OnDemand02/dom07/bootproc
Updating domain dom07 with bootproc 24 domainInstance 0 and interrupt vector MIB… OK
Starting obp_helper -m 24 -A on boot SB 6… OK
Starting netcon_server -p 24 … OK

Follow the console with netcon

ssp:dom07% netcon -g
trying to connect…
connected.
Unlocked write permission is granted.

Filed under: Sysadmin Tagged: e10k, sun

Running snoop to check the network traffic

Emerson Takahashi — Fri, 13 Aug 2010 12:05:19 +0000

Running snoop to check the network traffic. In this example, I’m generating an output file named /tmp/networkfile, recording everything that’s coming from 192.168.98.98 on port 80/TCP

root@solaris:~ # snoop -o /tmp/networkfile 192.168.98.98 port 80 and tcp
Using device /dev/e1000g0 (promiscuous mode)
147

Listening a specific network interface

root@solaris:~ # snoop -d e1000g0 -o /tmp/networkfile
Using device /dev/e1000g0 (promiscuous mode)
1446

Filed under: Sysadmin Tagged: snoop

Checking I/O access in a specific disk in AIX

Emerson Takahashi — Wed, 11 Aug 2010 00:51:24 +0000

Run iostat and check the column % tm_act. For seven times, it will display the statistics every two seconds

root@aix5:/ # iostat -d hdisk2 2 7
System configuration: lcpu=6 disk=4
Disks: % tm_act Kbps tps Kb_read Kb_wrtn
hdisk2 85.2 3453.1 303.8 37734456 8731944
hdisk2 51.0 610.0 84.5 796 424
hdisk2 34.5 288.0 45.5 436 140
hdisk2 39.5 452.0 63.5 692 212
hdisk2 61.5 380.0 66.0 480 280
hdisk2 48.5 542.0 66.5 596 488
hdisk2 47.0 590.0 80.0 1020 160

Filed under: Sysadmin Tagged: aix, iostat

Stopping and starting an AIX Subsystem

Emerson Takahashi — Mon, 09 Aug 2010 20:10:34 +0000

Lists all the subsystems on AIX’s System Resource Controller and then look for the subsystem that you want. In this example, I’ll restart sshd

root@aix:/ # lssrc -a | grep ssh
sshd ssh 340158 active

Issue the command to stop sshd

root@aix:/ # stopsrc -s sshd
0513-044 The sshd Subsystem was requested to stop.

Then start it

root@aix:/ # startsrc -s sshd
0513-059 The sshd Subsystem has been started. Subsystem PID is 340162.

Filed under: Sysadmin Tagged: aix

Increasing a JFS2 filesystem on AIX

Emerson Takahashi — Mon, 09 Aug 2010 20:07:32 +0000

First you need to know which filesystem that you’ll resize. Get the logical volume

root@aix:/ # df -m /u04
Filesystem MB blocks Free %Used Iused %Iused Mounted on
/dev/lvcrnstore 34816.00 1892.34 95% 103 1% /u04

With this information you type lslv lvcrnstore to find out about the volume group that this logical group is part of. Check if there are FREE PPs to extend the filesystem

root@aix:/ # lsvg oraclevg
VOLUME GROUP: oraclevg VG IDENTIFIER: 000d400c00004c00000000fd81379ca3
VG STATE: active PP SIZE: 256 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 531 (135936 megabytes)
MAX LVs: 256 FREE PPs: 17 (4352 megabytes)
LVs: 15 USED PPs: 514 (131584 megabytes)
OPEN LVs: 14 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable

Resize the filesystem and check the new size

root@aix:/ # chfs -a size=+4G /u04
Filesystem size changed to 79691776

root@aix:/ # df -m /u04
Filesystem MB blocks Free %Used Iused %Iused Mounted on
/dev/lvcrnstore 38912.00 5987.71 85% 103 1% /u04

Notice that the number of free PPs decreased since you used to increase the filesystem

root@aix:/ # lsvg oraclevg
VOLUME GROUP: oraclevg VG IDENTIFIER: 000d400c00004c00000000fd81379ca3
VG STATE: active PP SIZE: 256 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 531 (135936 megabytes)
MAX LVs: 256 FREE PPs: 1 (256 megabytes)
LVs: 15 USED PPs: 530 (135680 megabytes)
OPEN LVs: 14 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable

Filed under: Sysadmin Tagged: aix, chfs, lsvg

Creating a SVM metadevice and an UFS filesystem

Emerson Takahashi — Mon, 09 Aug 2010 01:57:56 +0000

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

Filed under: Sysadmin Tagged: metainit, metattach, newfs, solaris, svm

How to connect to a Cyclades console server

Emerson Takahashi — Sat, 07 Aug 2010 15:14:59 +0000

Here I have a Cyclades AlterPath ACS16 Console Server. To connect to a serial port, first I need to login to the Cyclades

emerson@shellcore:~ $ ssh root@192.85.176.210
Password:

[root@cyclades011 root]#

To connect to a serial port, type the corresponding port on the ts_menu utility

[root@cyclades011 root]# ts_menu
Serial Console Server Connection Menu for your Master Terminal Server

1 0C-21-EFP01 2 0C-21-EFP02 3 0C-21-EFP03 4 0C-21-EFP04
5 0C-21-EFP05 6 0C-21-EFP06 7 0C-21-EFP07 8 0C-21-EFP08
9 0C-21-EFP09 10 0C-21-EFP10 11 0C-21-EFP11 12 0C-21-EFP12
13 0C-21-EFP13 14 0C-21-EFP14 15 0C-21-EFP15 16 0C-21-EFP16

Type ‘q’ to quit, a valid option[1-16], or anything else to refresh : 12

s_evt@cyclades011 2010-6-3T22:35:43Z 192.85.176.210 EVT[5]: Serial session started. User: root. Port name: 0C-21-EFP12. Port Number: 12. Session Type: 1.
solaris06 console login:

Please login:

I logged out of the ALOM and I didn’t have the password for it. Happily it timed out and I was back on the ALOM.

Serial line login timeout, returns to console stream.

Enter #. to return to ALOM.

To quit, press CTRL + \

solaris06 console login: (CTRL + \) Quit
[root@usplgmcylts011 root]# s_evt@usplgmcylts011 2010-6-3T22:51:50Z 192.85.176.210 EVT[6]: Serial session stopped. User: root. Port name: 0C-21-EFP12. Port Number: 12. Session type: 1.
s_evt@usplgmcylts011 2010-6-3T22:51:50Z 192.85.176.210 EVT[6]: Serial session stopped. User: root. Port name: 0C-21-EFP12. Port Number: 12. Session type: 1.

[root@cyclades011 root]#

Filed under: Sysadmin Tagged: console, cyclades

A Cluster with Solaris and Oracle RAC – Avoid panic when rebooting

Emerson Takahashi — Fri, 06 Aug 2010 15:05:43 +0000

You just rebooted a server that you know that runs Oracle RAC and the other node rebooted. This happened because CRS was active and you first need to disable to reboot the other node. You’ll see this message on /var/adm/messages

Jun 5 14:15:19 solaris_rac2 root: Oracle clsomon failed with fatal status 12.
Jun 5 14:15:20 solaris_rac2 root: Oracle CRS failure. Rebooting for cluster integrity.
rebooting…

Run this command to stop CRS. Your path may vary according to where you installed the binary.

root@solaris_rac1:~ # /u01/app/oracle/product/11.1.0/bin/crsctl stop crs
Stopping resources.
This could take several minutes.
Successfully stopped Oracle Clusterware resources
Stopping Cluster Synchronization Services.
Shutting down the Cluster Synchronization Services daemon.
Shutdown request successfully issued.

Check the status with crsctl check crs. It should display the message below

root@solaris_rac1:~ # /u01/app/oracle/product/11.1.0/bin/crsctl check crs
Failure 1 contacting Cluster Synchronization Services daemon
Cannot communicate with Cluster Ready Services
Cannot communicate with Event Manager

After you reestablish the machine, CRS should start automatically

root@solaris_rac1:~ # /u01/app/oracle/product/11.1.0/bin/crsctl check crs
Cluster Synchronization Services appears healthy
Cluster Ready Services appears healthy
Event Manager appears healthy

Filed under: Sysadmin Tagged: oracle, rac

Installing HP Server Automation client for Solaris

Emerson Takahashi — Fri, 06 Aug 2010 14:25:31 +0000

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.

Filed under: Sysadmin Tagged: hp server automation, opsware, solaris

Linux – Password has been used already. Choose another

Emerson Takahashi — Wed, 04 Aug 2010 12:04:11 +0000

root@linux:~ # passwd emerson
Changing password for emerson.
New Password:
Reenter New Password:
Password has been used already. Choose another.
Password changed

Linux is keeping the old password stored on /etc/security/opasswd. Delete the line containing the user that you’re trying to change the password

Filed under: Sysadmin Tagged: linux, passwd