Brightmail ControlCenter not updating properly

About a week ago I noticed that Brightmail was no longer sending me daily reports telling me how many messages came in, what percentage was spam, virus, etc. so I finally got around to looking into it. Turns out the ControlCenter within Brightmail was no longer updating so it was not showing updates for virus or spam definition files, nor was it tracking how many messages were handled. I searched their online knowledgebase, but it’s not very user friendly. After a call to their support center I got the instructions I needed to get the ControlCenter updating again. Here are the steps I took:

# cd /opt/symantec/sbas/ControlCenter/MySQL/mysql-pro-4.0.16-sun-solaris2.8-sparc/bin

NOTE: this is the default install directory. If you installed in a non-standard place you will need to replace the above path with your install directory

# ./mysqlcheck –h 127.0.0.1 --auto-repair –ubrightmailuser –ppassword brightmail

The password can be obtained by looking for the password attribute located in:

/opt/symantec/sbas/ControlCenter/Tomcat/jakarta-tomcat-4.1.27/conf/server.xml

I generally direct the output from this command to a text file, although it is of very little actual value:

# ./mysqlcheck –h 127.0.0.1 --optimize –ubrightmailuser –ppassword brightmail
# /etc/init.d/tomcat4 stop
# /etc/init.d/mysql.server stop
# /etc/init.d/mailwall stop
# /etc/init.d/mysql.server start
# /etc/init.d/mailwall start
# /etc/init.d/tomcat4 start

I was able to then restart the ControlCenter and log in, and I found all of my information was once again updating correctly and I am able to pull reports on the messages that have been scanned.

Advertisements

Veritas 4.1 encapsulation problem on V445

I installed VxVM 4.1 dozens of times and never had an issue until today. I rebooted after encapsulating the disk and see this:

VxVM vxvm-reconfig ERROR V-5-2-337 The encapsulation of the Boot Disk failed.
VxVM vxvm-reconfig NOTICE V-5-2-393 The system will now be rebooted.

The problem is a bad line in the /usr/lib/vxvm/bin/vxroot. This bug caused the my system to boot without the following lines in /etc/system:

rootdev:/pseudo/vxio@0:0
set vxio:vol_rootdev_is_volume=1

So I had to boot off the network, mount up the drive and add them to /etc/system. After that everything worked fine. I found the answers here. In the future you should be able to edit vxroot before you boot. You might want to make it part of your jumpstart finishing script.

Creating a Jumpstart server from Solaris 9 ISOs

Did you know you can just download iso images from SUN and mount them over a loopback device? I usually don’t need to do this because someone has the CD images. But today I needed the new Solaris 9 09/05 HW release for the V445 I am working on. I mounted up the iso:

# lofiadm -a /jumpstart/sol-9-905hw-ga-sparc-v1.iso
# mount -F hsfs /dev/lofi/1 /mnt

I run the jumpstart setup script out of Tools and get this:

# ./setup_install_server /jumpstart/OS/t
ERROR: Install boot image /mnt/Solaris_9/Tools/Boot does not exist
Check that boot image exists, or use [-t] to
specify a valid boot image elsewhere.

It turns out that the iso has two slices in it. There is a nice guide here, on how to do it.

I love being a Solaris Admin

I work on Solaris in some large data centers. Over the last few years I have failed to document all the little nuances that cause me problems. For example today I needed to install Solaris 9 on the new V445 which requires the Solaris 9 09/05 HW release. When I downloaded the isos and attempted to add the image to my Jumpstart server I hit a bring wall.

I decided to blog all the issues I run into. Usually the problem has been solved, but it might take some searching and a bit of your own experience to render the finally fix. I am looking for other Solaris admins will join the with me. So if you are interested please email me and I will set you up an account.