Posts

Shell Scripting

Script to monitor the outgoing ssh connection on a linx machine (100 is a private n/w so grepping it out) max_ssh_conn=0 while true do ssh_conn=`netstat -an|grep -v 127|grep -v "100.1.1"|grep ":22"|grep ESTABLISHED|wc -l` if [ $ssh_conn -gt $max_ssh_conn ] then  echo -n "connection increased to " max_ssh_conn=$ssh_conn echo $max_ssh_conn else echo "connection max seen is " $max_ssh_conn "and current connection level is at" $ssh_conn fi sleep 1 done List only the filenames after using find command find /opt -name '*.jar' -printf "%f\n"

some funny stuffs

Dazed and confused :)   [root@PC-020 ~]#  Message from syslogd@PC-020 at Jul 29 16:12:08 ...  kernel:Uhhuh. NMI received for unknown reason b1 on CPU 0. Message from syslogd@PC-020 at Jul 29 16:12:08 ...  kernel:You have some hardware problem, likely on the PCI bus. Message from syslogd@PC-020 at Jul 29 16:12:08 ...  kernel:Dazed and confused, but trying to continue Write failed: Broken pipe [root@ATT-Pres ams]# 

Installing Pytest on Windows Platform

Go to the Scripts Directory under Python installation C:\>cd Python34\Scripts C:\Python34\Scripts>dir  Volume in drive C is System  Volume Serial Number is C273-3B76  Directory of C:\Python34\Scripts 03/19/2015  10:00 AM    <DIR>          . 03/19/2015  10:00 AM    <DIR>          .. 03/19/2015  10:00 AM            92,008 easy_install-3.4.exe 03/19/2015  10:00 AM            92,008 easy_install.exe 03/19/2015  10:00 AM            91,980 pip.exe 03/19/2015  10:00 AM            91,980 pip3.4.exe 03/19/2015  10:00 AM          ...

vmWare - Vcenter Server Appliance 5.5 - embedded DB problem

Problem seen: The embedded DB didnt start due to which vCenter configurations like Dswitch, hosts, etc were not available. vSA-173:~ # service vmware-vpxd status vmware-vpxd is stopped tomcat is stopped vSA-173:~ # service vmware-vpxd start Waiting for the embedded database to start up: ............................failed Verifying EULA acceptance: success Executing pre-startup scripts... Updating the vCenter endpoint in the Lookup Service. Intializing registration provider... Getting SSL certificates for https://135.249.34.173:7444/lookupservice/sdk Service with name 'vpxd-vSA-173-81a29e14-9705-47e2-a165-3cacb809fd43' and ID 'local:20165866-25c5-41ac-8e5e-9fc277b7bc6b' was updated. Return code is: Success Starting ldap-server..done Starting vmware-vpxd: success Waiting for vpxd to initialize: .................... .................................^C vSA-173:~ # Traceback (most recent call last):   File "/usr/lib/vmware-vpx/py/wait_for_vpxd.py...