root@myhost1# vxdg deport DB_PRD
VxVM vxdg ERROR V-5-1-584 Disk group DB_PRD: Some volumes in the disk group are in use

but df doesn’t show up anything related with DG.

/dev/vx/dsk/DB_PRD/DBroot /BCV/DB vxfs noauto,_netdev 0 0
/dev/vx/dsk/DB_PRD/DB-ora /BCV/DB/ora vxfs noauto,_netdev 0 0
/dev/vx/dsk/DBarc_PRD/DB-ora-archivelog01 /BCV/DB/ora/archivelog01 vxfs noauto,_netdev 0 0

root@myhost1# mount /BCV/DB
root@myhost1# mount /BCV/DB/ora
UX:vxfs mount.vxfs: ERROR: V-3-21300: cannot open “/BCV/DB/ora” for quotactl

root@myhost1#fuser -c /BCV/DB
Cannot stat file /proc/13919/fd/4: Input/output error
Cannot stat file /proc/13946/fd/5: Input/output error
root@myhost1#ps -ef|grep “13919|13946″
root 13919 1 0 Jan28 ? 00:00:00 bpbkar -r 1209600 -ru root -dt 0 -to 0 -clnt
root 13946 1 0 Jan28 ? 00:00:00 bpbkar -r 1209600 -ru root -dt 0 -to 0 -clnt
root@myhost1# kill -9 13919 13946

# succeed deport the dg now.
root@myhost1# vxdg deport DB_PRD
root@myhost1# vxdg -C import DB_PRD
root@myhost1# vxdg list
NAME STATE ID
localnbu enabled,cds 1245484407.6.myhost1
DB_PRD enabled,cds 1286892006.172.myhost2

Crontab issue:
pam_access(crond:account): access denied
crond[9985]: CRON (someuser) ERROR: failed to open PAM security session: Success
crond[9985]: CRON (someuser) ERROR: cannot set security context

* if has /etc/cron.allow – add users to this file
* /etc/security/access.conf – comment out

# All other users should be denied to get access from all sources.
#- : ALL : ALL
# -:ALL EXCEPT root:LOCAL

You’ll need to convert VDI into another format if you want to run a VirtualBox VM on another virtualization platform, such as VMWare or KVM.

The VMDK virtual disk format is a good choice because even though it originated with VMWare it is supported by other virtualization platforms including VirtualBox and KVM.

VirtualBox enables the conversion using the low-level “VBoxManage clonehd” command:

VBoxManage list hdds # prints a list of disk image UUIDs
VBoxManage clonehd -o converted.vmdk format VMDK
cd ~/.VirtualBox/HardDisks/
ls -la converted.vmdk

Once you have converted to VMDK you can use qemu-img, a tool bundled with qemu (KVM’s virtualization backend) to further convert VMDK to other formats.

A particularly useful format to convert to is ‘raw’ which you can then mount as a loopback device:

apt-get install qemu
qemu-img convert -f vmdk converted.vmdk -O raw converted.raw
mount -o loop converted.raw /mnt

The naive attempts to automate the use of passwd will fail, so the standard advice has always been to use a tool like expect to interactively call the passwd binary.

But there is an alternative approach which is more sensible which is to use the usermod command to change a password.

Assume you have a user account called guest upon your system and you wish to set the user’s password to openaccess you can do this by running:

# hash=$(echo openaccess | openssl passwd -1 -stdin)
# usermod –pass=”$hash” guest

If you wish you could combine that into a single line:

# usermod -p $(echo openaccess | openssl passwd -1 -stdin) guest

If a local user can see the commands you’re running in the output of “ps”, “top”, or similar then this is insecure – but if you generate the hash remotely you should probably be safe enough.

A few weeks ago, I got a little problem with my solaris box, namely solaris won’t boot because the boot archive was corrupt, *sigh*. Anyway the boot archive in solaris 10 was contain kernel module and configuration file was needed for solaris to startup the system.

Error:

module /platform/i86pc/boot_archive error 3 bad or corrupt data while decompressing file

Workaround:

Boot up your solaris in “solaris failsafe mode”, next solaris image will mount with writeable mode on “/a” mount point

rm -f /a/platform/i86pc/boot_archive
bootadm update-archive -R /a
reboot

Here is option from iuscommunity.org

We are committed to providing up-to-date and regularly maintained RPM packages for the latest upstream versions of PHP, Python, MySQL and other common software specifically for Red Hat Enterprise Linux and clones.

Ref: http://iuscommunity.org/Docs/ClientUsageGuide
Try at your own risk.

1st round
# halt all the VMs from Vsphpere

# put the ESXi into “maintenance mode”, right click the host.

# backup the firmware configuration
C:\Program Files\VMware\VMware vSphere CLI\bin>vicfg-cfgbackup.pl –server beivm
srv01 -s beivmsrv01_20110320.bak
Enter username: root
Enter password:
Saving firmware configuration to beivmsrv01_20110320.bak …

# update from 4.0 to 4.1
C:\Program Files\VMware\VMware vSphere CLI\bin>vihostupdate.pl –server beivmsrv
01 -i -b F:\ISO\upgrade-from-ESXi4.0-to-4.1.0-0.0.260247-release.zip
Enter username: root
Enter password:
Please wait patch installation is in progress …
The update completed successfully, but the system needs to be rebooted for the c
hanges to be effective.

# check the patch
C:\Program Files\VMware\VMware vSphere CLI\bin>vihostupdate.pl –server beivmsrv
01 –query
Enter username: root
Enter password:
———Bulletin ID——— —–Installed—– —————-Summary——-
———-
ESXi410-GA 2010-10-03T07:10:52 ESXi upgrade Bulletin

ESXi410-GA-esxupdate 2010-10-03T07:10:52 ESXi pre-upgrade Bulletin

# use vsphere to reboot

2nd round
# put the ESXi into “maintenance mode”, if the host is not in that mode, right click the host.

# update from 4.1 to 4.1 update 1
C:\Program Files\VMware\VMware vSphere CLI\bin>vihostupdate.pl –server beivmsrv
01 -i -b F:\ISO\update-from-esxi4.1-4.1_update01.zip
Enter username: root
Enter password:
Please wait patch installation is in progress …
The update completed successfully, but the system needs to be rebooted for the c
hanges to be effective.

# use vsphere to reboot

Quick Step
Cut and paste the following into a linux shell with root privleges:
sysctl -w net.core.rmem_max=8388608
sysctl -w net.core.wmem_max=8388608
sysctl -w net.core.rmem_default=65536
sysctl -w net.core.wmem_default=65536
sysctl -w net.ipv4.tcp_rmem=’4096 87380 8388608′
sysctl -w net.ipv4.tcp_wmem=’4096 65536 8388608′
sysctl -w net.ipv4.tcp_mem=’8388608 8388608 8388608′
sysctl -w net.ipv4.route.flush=1

Details:

Assumptions
This howto assumes that the machine being tuned is involved in supporting high-bandwidth applications. Making these modifications on a machine that supports multiple users and/or multiple connections is not recommended – it may cause the machine to deny connections because of a lack of memory allocation.
The Steps

1. Make sure that you have root privleges.

2. Type: sysctl -p | grep mem
This will display your current buffer settings. Save These! You may want to roll-back these changes

3. Type: sysctl -w net.core.rmem_max=8388608
This sets the max OS receive buffer size for all types of connections.

4. Type: sysctl -w net.core.wmem_max=8388608
This sets the max OS send buffer size for all types of connections.

5. Type: sysctl -w net.core.rmem_default=65536
This sets the default OS receive buffer size for all types of connections.

6. Type: sysctl -w net.core.wmem_default=65536
This sets the default OS send buffer size for all types of connections.

7. Type: sysctl -w net.ipv4.tcp_mem=’8388608 8388608 8388608′
TCP Autotuning setting. “The tcp_mem variable defines how the TCP stack should behave when it comes to memory usage. … The first value specified in the tcp_mem variable tells the kernel the low threshold. Below this point, the TCP stack do not bother at all about putting any pressure on the memory usage by different TCP sockets. … The second value tells the kernel at which point to start pressuring memory usage down. … The final value tells the kernel how many memory pages it may use maximally. If this value is reached, TCP streams and packets start getting dropped until we reach a lower memory usage again. This value includes all TCP sockets currently in use.”

8. Type: sysctl -w net.ipv4.tcp_rmem=’4096 87380 8388608′
TCP Autotuning setting. “The first value tells the kernel the minimum receive buffer for each TCP connection, and this buffer is always allocated to a TCP socket, even under high pressure on the system. … The second value specified tells the kernel the default receive buffer allocated for each TCP socket. This value overrides the /proc/sys/net/core/rmem_default value used by other protocols. … The third and last value specified in this variable specifies the maximum receive buffer that can be allocated for a TCP socket.”

9. Type: sysctl -w net.ipv4.tcp_wmem=’4096 65536 8388608′
TCP Autotuning setting. “This variable takes 3 different values which holds information on how much TCP sendbuffer memory space each TCP socket has to use. Every TCP socket has this much buffer space to use before the buffer is filled up. Each of the three values are used under different conditions. … The first value in this variable tells the minimum TCP send buffer space available for a single TCP socket. … The second value in the variable tells us the default buffer space allowed for a single TCP socket to use. … The third value tells the kernel the maximum TCP send buffer space.”

10. Type:sysctl -w net.ipv4.route.flush=1
This will enusre that immediatly subsequent connections use these values.

Ref: