Big Brother client installation on UNIX/Linux
Following procedure explains the steps for installing Big Brother client on UNIX/Linux servers and information about all the supported files. I could not really find this anywhere easily broke down, I hope this helps a few...
Installation Steps
Create user bb on the server to be monitored.Assign 1984 uid to the Big Brother user.
useradd -u 1984 -c "Big Brother monitoring" bb
Copy the latest BB client tar file from your repository to bb home directory of the monitored server.
su - bb
scp root@yourrepo:/home/bb/software/BBCLT-aix6.1-bbc4.30-bbpe.tar .
Decompress the tar file in the bb home directory
In the bb home directory
tar -xvf BBCLT-aix6.1-bbc4.30-bbpe.tar
Exit from bb home directory as the BB client should be installed using root account.
From root user go to /home/bb/bbc4.30-bbpe/install and execute bbconfig file.After executing bbconfig file, it will ask to accept the License agreement.
After accepting the License agreement, the installation process will ask to enter a few details.
OS [aix] is the default so you can hit enter directly
It will ask for the userid for Big Brother which will be "bb".
The installation process will add a service in /etc/init.d which will start at boot.
At this point the BB client is not started as bb-hosts file is missing or empty.
Information about bb-hosts file
The bb-hosts file in present in /home/bb/bbc4.30-bbpe/etc.This file holds the information about the host and the BBDisplay,BBPAGER and BBNET.
BBDISPLAY is the server which will display all the monitored servers.
BBPAGER is the server which sends email alerts.
BBNET is the server which performa all Network tests.
Sample bb-hosts file.If the first line or name of the monitored host does not match the entry in the bb-hosts file then the bb client will not start.
0.0.0.0 monitoredsrv #must name uname -n
0.0.0.0 displaysrv # BBNET BBDISPLAY BBPAGER
Once all the changes are done then we are good to start the BB client.
The entry of the monitored server in bb-hosts file should also match with the entry in BB server's bb-hosts file.
I forgot to mention that to start and stop BB you can use the following:
su - bb -c "cd /home/bb/bbc4.30-bbpe;./runbb.sh start"
su - bb -c "cd /home/bb/bbc4.30-bbpe;./runbb.sh stop"
My WebLogic 10.3 does not start
I was coming back from a pretty good weekend doing renovation when I am called as one of the application resting on a WebLogic Server (WLS) was inaccessible to users.
A quick round up at the WLS console showed that one of the server doesn't want to start nor restart.
Having a look at the logs for that specific server - you know under logs directory of that server - showed that amount other errors caused by this there was a problem with the diagnostic file.
.../domain/servers/WebLogicAdmin (or managed server)/data/store/default/XXXXX.dat (WLS_DIAGNOSTICS000000.DAT).
the diagnostic file? I never remembered setting any diag mode up and apparently the diag option is off. Anyhow quickly reading of the OTN, some people mentioned deleting the file as it could be corrupted.
That trick never worked for my case. I indeed deleted the WLS_DIAG*.WLS and any .lok under ../Oracle/Middleware/user_projects/domains/canp8/servers files around but nothing.
I eventually had to delete the following directories under each server for which that error occurred. I stopped WLS and for each server I deleted the /data, /tmp and /logs. then starting WLS, it seemed to like not finding them and created a new clean structure. However that was not the end of the troubleshooting as it would complain about the port for one of the server to be already taken by something else.
Indeed, the port seems to be taken by some WLS ghost process of the same name with a different UID. I did not want to look further and decided to shutdown the whole WLS box clean and restart it.
It did the trick for me... perhaps it will do it for you. I still wonder what those files are for and why they would get corrupted and prevent a server from starting up.
Robocopy and EMC Celerra
I came across a problem when using Robocopy command scripts when copying files from NTFS to EMC Celerra file system. The problem was that every time Robocopy was told to copy files to the EMC Celerra over the WAN, the files were always detected as “newer” on from the originating source. This caused Robocopy to copy every single file from our network to the remote network each and every time.
I came across a command line switch for Robocopy: /FFT : Assume FAT File Times (2-second date/time granularity). The NTFS date and time stamp is a 64-bit variable, which DART doesn’t deal with. So what this does is force Robocopy to use FAT style time stamps which are 2-second granularity. It allows enough flexibility to account for the way the time is recorded when doing a file copy from NTFS to another file system. This is needed when going between and NTFS and Linux/Unix/FAT or emulated file system.
update 20110601: I now use fastcopy instead of robocopy. It is a great fast(er) and friendly tool! And it doesn't have any of the security or date issues I have seem with the msft tool.
ESX4 HA error
I only played with ESX4 regular flavor so far and I wanted to try mixing them with ESX4i. However trying to put that host in my cluster would give me HA error.
Enabling HA gave the error:
"Cannot complete the configuration of HA agent on the host. See the task for details for addional information. "
Without much details I was almost ready to blame it on ESX4i. However after checking everything I found out that my DNS servers settings were wrong.
Changing my DNS to the right IPs and HA configuration worked like a charm.
Obviously my sticky keys did not help but of course stressed out the reminder that HA relies on DNS heavily.
Install your atheros wifi card on fedora 7
Yes, atheros cards are great but sometime not supported by default by some OS.
To install the madwifi drivers for your atheros on Fedora 7 do the following:
gedit /etc/yum.repos.d/atrpms.repo
and type
[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/f$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1
and click on SAVE , also root import the gpg key from the terminal:
rpm --import http://atrpms.net/RPM-GPG-KEY.atrpms
then just use YUM to install everything you need!
yum install madwifi
You will get something like this:
[root@localhost ~]# yum install madwifi
Loading "installonlyn" plugin
Setting up Install Process
Parsing package install arguments
atrpms 100% |=========================| 951 B 00:00
primary.xml.gz 100% |=========================| 224 kB 00:00
atrpms : ################################################## 1240/1240
Resolving Dependencies
--> Running transaction check
---> Package madwifi.i386 1:0.9.4-38_r2512.fc7 set to be updated
--> Processing Dependency: madwifi-kmdl-1:0.9.4-38_r2512.fc7 for package: madwifi
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package madwifi.i386 1:0.9.4-38_r2512.fc7 set to be updated...
KitKatNeko