Paste following contents in new file, change variables according to the domain and execute it
@echo off
SETLOCAL
set WL_HOME=C:\bea\weblogic91
set PROD_NAME=BEA Products
set BAR_WL_HOME=C_bea_weblogic91
set SERVER_NAME=SERVER_NAME
set DOMAIN_NAME=DOMAIN_NAME
rem *** Uninstall the service
"%WL_HOME%\server\bin\beasvc" -remove -svcname:"beasvc %DOMAIN_NAME%_%SERVER_NAME%"
ENDLOCAL
Friday, July 9, 2010
Tuesday, June 29, 2010
NFS Setup on Solaris
NFS Setup on Solaris
NFS Server Setup
----------------
1) /etc/rc.d or /etc/init.d
/usr/sbin/portmap or rpc.portmap
2) /etc/dfs/dfstab
share -F nfs -o rw=nfsclient: /export/nfs
3) /etc/dfs/sharetab
/export/nfs - nfs rw=nfsclient
4) /etc/dfs/fstypes
nfs NFS Utilities
5) /etc/rmtab lists filesystems that are remotely mounted by clients.
6) mountd rpc.mountd
nfsd rpc.nfsd
7) /usr/sbin/share (and chomod a+rx)
#!/bin/sh
killall -HUP /usr/sbin/rpc.mountd
killall -HUP /usr/sbin/rpc.nfsd
echo re-exported file systems
(Run script after modifying /etc/exports)
8) rpcinfo -p (to check mountd and nfsd running)
NFS Client Setup
----------------
1) To make the system mount a nfs file system upon boot
/etc/vfstab
nfsserver:/export/nfs - /mnt/nfs nfs - yes -
2) /etc/mnttab lists filesystems which are currently mounted on
onto that client.
3) To mount:
NFS Server Setup
----------------
1) /etc/rc.d or /etc/init.d
/usr/sbin/portmap or rpc.portmap
2) /etc/dfs/dfstab
share -F nfs -o rw=nfsclient: /export/nfs
3) /etc/dfs/sharetab
/export/nfs - nfs rw=nfsclient
4) /etc/dfs/fstypes
nfs NFS Utilities
5) /etc/rmtab lists filesystems that are remotely mounted by clients.
6) mountd rpc.mountd
nfsd rpc.nfsd
7) /usr/sbin/share (and chomod a+rx)
#!/bin/sh
killall -HUP /usr/sbin/rpc.mountd
killall -HUP /usr/sbin/rpc.nfsd
echo re-exported file systems
(Run script after modifying /etc/exports)
8) rpcinfo -p (to check mountd and nfsd running)
NFS Client Setup
----------------
1) To make the system mount a nfs file system upon boot
/etc/vfstab
nfsserver:/export/nfs - /mnt/nfs nfs - yes -
2) /etc/mnttab lists filesystems which are currently mounted on
onto that client.
3) To mount:
Friday, June 25, 2010
ESX Server becomes disconnect and attempt to reconnect fail.
ESX Server becomes disconnect and attempt to reconnect fail.
One reason is the ESX services become hung.
Run the following to fix the issue:
service mgmt-vmware restart
service vmware-vpxa restart
If these don't correct the problem then run
service mgmt-vmware stop
service vmware-vpxa stop
ps -ef | grep hostd
kill -9
Further research required.
One reason is the ESX services become hung.
Run the following to fix the issue:
service mgmt-vmware restart
service vmware-vpxa restart
If these don't correct the problem then run
service mgmt-vmware stop
service vmware-vpxa stop
ps -ef | grep hostd
kill -9
Further research required.
Thursday, April 22, 2010
Friday, April 9, 2010
ulimit Error - ulimit: open files: cannot modify limit
-> Login to the server and check parameters by using plimit command
bash-3.00# plimit $$
25169: bash -l
resource current maximum
time(seconds) unlimited unlimited
file(blocks) unlimited unlimited
data(kbytes) unlimited unlimited
stack(kbytes) 8192 unlimited
coredump(blocks) unlimited unlimited
nofiles(descriptors) 1024 1024
vmemory(kbytes) unlimited unlimited
It means you can not change value more than 1024. You can change max value by using
bash-3.00# plimit -n 10000 $$
Now it is set to 10000
bash-3.00# plimit $$
25505: bash -l
resource current maximum
time(seconds) unlimited unlimited
file(blocks) unlimited unlimited
data(kbytes) unlimited unlimited
stack(kbytes) 8192 unlimited
coredump(blocks) unlimited unlimited
nofiles(descriptors) 10000 10000
vmemory(kbytes) unlimited unlimited
Now you can ulimit to set 10000
# ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
open files (-n) 10000
pipe size (512 bytes, -p) 10
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 29995
virtual memory (kbytes, -v) unlimited
bash-3.00# plimit $$
25169: bash -l
resource current maximum
time(seconds) unlimited unlimited
file(blocks) unlimited unlimited
data(kbytes) unlimited unlimited
stack(kbytes) 8192 unlimited
coredump(blocks) unlimited unlimited
nofiles(descriptors) 1024 1024
vmemory(kbytes) unlimited unlimited
It means you can not change value more than 1024. You can change max value by using
bash-3.00# plimit -n 10000 $$
Now it is set to 10000
bash-3.00# plimit $$
25505: bash -l
resource current maximum
time(seconds) unlimited unlimited
file(blocks) unlimited unlimited
data(kbytes) unlimited unlimited
stack(kbytes) 8192 unlimited
coredump(blocks) unlimited unlimited
nofiles(descriptors) 10000 10000
vmemory(kbytes) unlimited unlimited
Now you can ulimit to set 10000
# ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
open files (-n) 10000
pipe size (512 bytes, -p) 10
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 29995
virtual memory (kbytes, -v) unlimited
Tuesday, February 9, 2010
Friday, January 15, 2010
Clearing faults
2) #fmadm repair
# fmadm repair 03351534-e325-cf5d-81ae-e3fc8be83e5b
3) # cd /var/fm/fmd
# cd /var/fm/fmd && rm errlog fltlog ckpt/eft/* rsrc/*
(rm errlog fltlog ckpt/eft/* rsrc/*)
4) # fmadm reset cpumem-diagnosis
5) # fmadm reset cpumem-retire
6) # fmadm reset eft
7) # fmadm reset io-retire
# init 6
After these steps check to see if problem still exit.
# fmadm faulty
# fmadm repair 03351534-e325-cf5d-81ae-e3fc8be83e5b
3) # cd /var/fm/fmd
# cd /var/fm/fmd && rm errlog fltlog ckpt/eft/* rsrc/*
(rm errlog fltlog ckpt/eft/* rsrc/*)
4) # fmadm reset cpumem-diagnosis
5) # fmadm reset cpumem-retire
6) # fmadm reset eft
7) # fmadm reset io-retire
# init 6
After these steps check to see if problem still exit.
# fmadm faulty
Subscribe to:
Posts (Atom)
Welcome to the UNIX world
