01/06/2010

My experience sofar with Ubuntu Karmic 64 bit (Desktop & Server)

Tags: Lotus Domino Notes 8.5.1 VMWare Server 2.0.2 64 bit Linux Ubuntu Karmic
Sofar my ride with Karmic hasn't been all smooth.

I've upgraded my server from Ubuntu Server 8.04 (Hardy Heron) to 8.10 (Intrepid Ibex) and recently to 9.10 Server (Karmic) on 64 bit and encountered a few issues, and not just with Domino 8.5.1 - and yes I know this is not an IBM supported configuration

After the upgrade my Domino server came up without a problem but I noticed an error message from the full text indexer about not being able to find libstdc++.so.5
This library was replaced by the upgrade by libstdc++.so.6 - so I ended up pulling a copy from a previous release and adding that to /usr/lib32

Other than that sofar I haven't found any problems with Domino.

Daniel Nashed's SpamGeek also just continues to do it's job

I also have 64 bit VMWare Server 2.0.2 running on this server and after the upgrade the vmware modules refused to build, fortunately I found a fix here:

http://www.ubuntugeek.com/how-to-install-vmware-server-2-0-x-in-ubuntu-9-10-karmic.html

I have a Windows 2003 Server VMWare guest that started life as a physical box that I converted to a VM sometime last year that never had any problems but ever since the upgrade (and subsequent patch) has a tendency to die under high I/O loads. VMWare kills it (Worker#18| Caught signal 6).

After that, it was time for my laptop ...

11/13/2008

32 bit Domino on 64 bit Windows performance issue

Tags: Lotus Domino 7.0.3 FP1 8.0 Performance 64 bit SPR #FMEG6W3G25

Recently at one of our customers the domino servers exhibited severe performance issues,

This particular customer was running Domino 7.0.3 FP1 on 64 bit Windows 2003 Server and looking at the task manager on one of their servers showed that on a box with 4GB of memory, almost 3GB was in use as System Cache,

A picture named M2

Taking a look at perfmon showed that the disk queues for the volume holding the swap file were actually higher than those for the data volume, indicating that the system was primarily busy swapping data in and out of  memory.

Logging on to the system console was a painful exercise, where something as simple as clicking on the start button in the taskbar took 10+ seconds before the system responded.