Domino Thoughts

Installing Domino on Linux - Resolving missing requirements

Ted Hardenburgh — Thu, 17 Jan 2013 07:15:00 -0700

Recently, I was installing the Domino 9.0 Social Edition on a new CentOS 6 Linux install. It started very smoothly, the CentOS install went very well and the system updates worked flawlessly. I prepped the notes user and group and was ready to install the Domino code.

Then it came to a screeching stop.

The installer stopped with the message below:

To run this installer you need 32bit (i686) packages installed on your 64 bit Linux Redhat.

They are not installed by default, but are mandatory. The installer will exit after this message.
glibc-2.12-1.17.el6.i686
libgcc-4.4.4-13.el6.i686
libXtst-1.0.99.2-3.el6.i686
libXmu-1.0.5-1.el6.i686
libXp-1.0.0-15.1.el6.i686
libXft-2.1.13-4.1.el6.i686
libXi-1.3-3.el6.i686
libstdc++-4.4.4-13.el6.i686

Notice, I'm installing 64bit Domino on 64bit CentOS and the installer is still a 32bit application. Also, the version numbers mentioned are old and not the latest. Trying to run the yum install for these exact versions failed. After some searching, I had two options. First, download the RPM from a site and run the rpm installer. Second, I could try to install the most recent version and try that.

I ended up going for the second option after I backed into an install option for the latest version. Basically, leave the version info out and just use the package name and architecture version to find the current version available and install it. For example, below is the command to get te glibc package installed.

yum install -y glibc.i686

Lather, rinse, and repeat for the other packages and I was ready to go. The installer worked fine and Domino is up and running on a test VM.

BTW - For a very good walk through of the process, check out Devin Olson's YouTube videos on installing CentOS 6, Domino and Traveler. Here's the first one on installing CentOS They're well done - and that's not just cuz I would like a beer!

Location document MailServer field - what not to use

Ted Hardenburgh — Tue, 15 Jan 2013 08:11:25 -0700

Working with a client recently on some policy setting updates and we ran into an issue where the new policy wasn't taking effect on his client. We made the change to the policy (in this case an Archive policy) and could see that it had been processed and applied to the mail file. Checking the user's Notes client, the link to the Archive was not showing up.

I opened up the ($Policies) view in the user's local names.nsf to check the policy documents there and noticed that it had been a couple of months since the last update. Something was not right. We cleared the policy docs out of the view and restarted Notes. No policy documents at all were getting pulled down to the client.

This is a remote client and he had emailed me this update. I couldn't work with him immediately, so I asked him to send me the output from Help - Support - Collect Support Data in his Notes client. This is a very useful tool for pulling out all configuration and diagnostic data from the Notes client (Standard client only, I believe). This grabs the notes.ini, Eclipse related config files, etc and dumps them into a ZIP file in the same folder structure as the client. Very easy for a person to use and then send the resulting ZIP file.

Looking through the ZIP file I received, I went to the notes.ini to see what might be there. Scrolling through I find the MailServer= entry and an IP address listed instead of the Notes name of the server. I contact the user and have him open his location document and behold, the IP address. We change it to the correct name and restart the client. Now the policies are downloading and the link to the archive is present in his mail file.

Apparently, he had changed the setting during a problem with network routing. This was a good time to show him how to setup a connection document in case the routing issue ever comes back.

To recap, we discovered:
1 - The Collect Support Data tool in the Notes client is very helpful
2 - IP addresses in certain Location doc fields are not very helpful

Giving Tuesday - Help cure Cystic Fibrosis

Ted Hardenburgh — Tue, 27 Nov 2012 09:08:41 -0700

Last week, my son Andrew turned 18. Andrew was diagnosed with Cystic Fibrosis when he was 4. CF primarily affects the lungs and pancreas, allowing lung infections to occur and inhibiting weight gain due to lack of enzymes. When he was diagnosed, the average life expectancy for someone with CF was around 21 years of age. Shortly before he was diagnosed, researchers discovered the gene that CF affects and since then have been working to finding a cure. With the advances and discoveries since that time, currently the average life expectancy is about 37 years, with many CF adults well past that age.

Today, we are closer than ever to finding a cure. A drug released earlier this year resolves the cell defect in about 4% of the CF population. Another drug that will work for about 80% of CF patients (including Andrew) is slated for Phase III trials early next year. With these drugs, CF patient lung function and weight gains have been incredible. While not a "cure" it is a significant step in improving the lives of those with CF.

Today was designated "Giving Tuesday" after the Black Friday and Monday shopping days. I invite you to consider a donation to the CF Foundation, the organization that provides the majority of financial backing to drug manufacturers for CF related drugs. All amounts are welcome and very much appreciated.

A New Day

Ted Hardenburgh — Mon, 8 Oct 2012 08:08:16 -0700

After 4 1/2 great years, I have left GBS to start a new chapter in my professional life. My time at GBS (Lotus911 included) was a great time for me professionally and personally, getting to work with an incredible group of talented professionals and making some great friends. However, as someone said, change is good. Now is that time for me.

I have joined the team at Best Methods as of today and will be helping to expand and extend the Collaboration Solutions reach with the team there.

I hope you'll continue to follow me on this new chapter in my life.

Missing Rules tab in server document?

Ted Hardenburgh — Tue, 14 Feb 2012 13:12:04 -0700

Admittedly, this is an issue that is a fringe, but thought I'd post it just in case.

Yesterday, I was working to configure a client's server to use mail journaling. Everything was going smooth until I went to edit a server configuration document to add the mail rule for a couple of servers. The Rules tab was missing. I was on the Admin client, so I tried it from the Notes client and the tab showed up. So I finished the configuration and went searching for the cause. I mean, wouldn't you want to administrator the server configurations from the Admin client??

Looking around, I quickly found a technote on this issue that appears to be a throwback to the "old" days of 6.5.4/7.0. Something in the design of the Domino directory changed and a field got left behind that causes this issue. This explains why I only saw this issue on some of the older servers and not the newer ones.

A quick agent to delete the field from the document (it's in the technote) and I can now manage the server configurations from the Admin client.

Lotusphere: GBS Admins Roundtable

Ted Hardenburgh — Tue, 10 Jan 2012 10:24:04 -0700

Next week at Lotusphere, GBS will be hosting a gathering of a few of our admin experts to give some quick tips and also have time to ask questions and discuss your issues. David Brown, Chris Whisonant and myself will be leading the discussions. The session will take place on Monday, January 16 at 1pm. Please use the link below to register.

This is a "private" event in our hospitality suite, so we need to know how many will be attending.

Ask the Experts
Admins of the Round Table
Monday 1pm - 2pm
We've gathered a collection of Expert Administrators to talk about Implementing Managed Replicas, User Communication, and Using HAProxy as well as tips and tricks for administering Domino, Sametime, Connections and more.

Space for this session is limited so register today to reserve your seat.

I hope to see you there or stop by the pedestals and say "Hi!"

Join me next week for a GROUP Talk webcast

Ted Hardenburgh — Thu, 1 Sep 2011 09:07:50 -0700

Please join me next week for a GROUP Talk webcast on "Two Minute Drills for Administrators" where I'll reprise my presentation from this year's PACLUG event. The event will be at 11am EDT on September 7.

This webcast will give you some tools to manage and maintain servers and users by teaching you easy, two-minute drills to implement in your office! Discussions will focus on Notes/Domino, Quickr, Sametime, and even Connections! By taking these "two-minute drills" back to your office, you will experience easier management and increased efficiency.

Hope to "see" you there!

PACLUG Session Info now available

Ted Hardenburgh — Tue, 21 Jun 2011 16:50:33 -0700

Thanks to all who came to the session. As promised, here's the take-home stuff from the session.

Blackberry SRP changes May 28

Ted Hardenburgh — Fri, 27 May 2011 08:48:02 -0700

If you have a BES in the US, you're going to want to check your SRP configuration on the BES to make sure it will still work properly after May 28. RIM is changing some IP addresses that will affect your users.

First off, check the BES configuration and make sure that the Blackberry Router configuration is pointing to us.srp.blackberry.com and not another host name. Next, run the SRP test and make sure that you see that a successful connection is made to the following new IP addresses: 216.9.242.33 and 68.171.,242.33. You will likely see two other addresses tested - those are being retired.

Depending on your firewall configuration, you may need to update it to allow traffic over port 3101 to those addresses. A better configuration would be to allow traffic based on these recommendations from RIM. That way you'll be ahead of the curve if a change is made in the future.

Enjoy!

Join me at PACLUG June 21-22 in Las Vegas

Ted Hardenburgh — Tue, 12 Apr 2011 09:04:21 -0700

I'll be presenting at the inaugural PACLUG meeting held this June 21-22 at the Planet Hollywood Hotel/Casino in Las Vegas. It is a free event that will be featuring a number of well-known speakers from the Pacific region of the US. If you're attending THE VIEW conferences that week, why not come in a couple days early and get some additional goodness before these meetings start.

And if you're a member of one of the LUGs in the Western US, you'll get a very nice discount to attend THE VIEW Admin and Developer conferences.

To register for the free PACLUG conference to to http://paclug.org.

Android, AT&T, Traveler - Get it working with Mac/Linux

Ted Hardenburgh — Mon, 7 Mar 2011 15:53:37 -0700

Here's the second part of working with an Android device from AT&T and Lotus Traveler. This installment will talk about installing the Traveler app on your device using Sideload Wonder Machine from a Mac or Linux computer. The screenshots will be from my Mac, but the principal is the same either way.

To start, download the Lotus Traveler app from your Traveler server. This isn't the installer app that is downloaded initially from the Traveler web page, this is the actual Traveler app that will run on your phone. You'll need to point your browser to it directly and download it yourself. The URL you'll use is http(s)://"your traveler server"/traveler/LotusTraveler/android/LotusTraveler.apk. Make sure you download the file named LotusTraveler.apk and not LotusInstaller.apk.

Now go download the Sideload Wonder Machine app (registration required) and install it according to the instructions. After SWM is installed, copy the LotusTraveler.apk file into the folder called "2-Place-App-Here" in the location where SWM is installed.

On your Android device, enable USB Debugging in Settings > Applications > Development.

Connect your phone to the Mac or Linux computer and allow the USB drivers to be installed if they aren't already.

Open a Terminal session on your Mac and navigate to the installed location of SWM. In my case, it is in my home folder in the swm-mac folder. You can see the listing of files and folders after I copied the LotusTraveler.apk file to the appropriate location.

Execute the menu.sh script and you'll see the menu below. Choose "1. Push app to phone" to begin the install process.

After choosing the install option, you'll see a prompt reminding you to have the apk file in the correct location. Press Enter to continue and you'll next see the listing of apps available to be installed. Press Enter again and it will push the app to the phone. The password that the app is requesting is your Mac account password.

Once the install is done, you'll see the option to restart your phone. Traveler doesn't require the restart. You can go in and configure your Traveler server connection and begin receiving email, calendar and contact data from Domino on your phone.

Android, AT&T, Traveler - Getting them to play nice

Ted Hardenburgh — Mon, 7 Mar 2011 09:11:01 -0700

So, if you're a Lotus Notes user who bought an Android device on the AT&T network, you probably want to try out Lotus Traveler. Unfortunately, when you try to install Traveler on your device, you'll get a rude awakening. AT&T doesn't like apps that aren't in the market and they block you from installing it.

That's where a nice app called Sideload Wonder Machine comes in. This post will cover using it on Windows to install Lotus Traveler, and another post will cover Mac (and Linux).

First off, you'll need to download the Lotus Traveler app from your Traveler server. This isn't the installer app that is downloaded initially from the Traveler web page. You'll need to point your browser to it directly and download it yourself. The URL you'll use is http(s)://"your traveler server"/traveler/LotusTraveler/android/LotusTraveler.apk. Make sure you download the file named LotusTraveler.apk and not LotusInstaller.apk.

Now go download the Sideload Wonder Machine app (registration required) and install it according to the instructions. Once you're done, you'll be ready to go.

On your Android device, enable USB Debugging in Settings > Applications > Development.

Connect your phone to the PC and allow the USB drivers to be installed if they aren't already.

Launch SWM and click the Choose APK file. Navigate to the download location and choose the APK file.

Click the Install button and you'll see a command prompt with the progress. (You may also get a prompt from Windows asking permission for the app to run.)

Close out of SWM and unplug your device and you'll be ready to login to Traveler and start syncing.

GROUP Talk this Wednesday - Sametime 8.5 installs and Domino 8.5.2 administration

Ted Hardenburgh — Mon, 8 Nov 2010 10:29:55 -0700

So you can't make it to the ILUG conference in Belfast, what to do? Join GROUP online for a webinar with Chris Whisonant, Phil Witton and me, the "Admins of the Round Table" to talk about Sametime 8.5 installs and Domino 8.5.2 Administration. Bring your questions for our round table discussion and also we'll cover the Sametime 8.5.x install process and what's new in the Domino 8.5.1 and 8.5.2 releases that administrators should be checking out.

Join us this Wednesday, November 10 from 11am - 12pm ET (8-9am PT). Go to http://gbs.com/events for more info or click here to register for the webcast.

"See" you this Wednesday!

Domino won’t let that user on to the server? Try this...

Ted Hardenburgh — Thu, 26 Aug 2010 08:43:13 -0700

Have you ever deleted a user from Domino and added them to the Deny Access group only to have HR come back and say, "We've rehired John Doe and he needs back into Notes right now." Of course you have, and if you've ever done this, you may have come across an issue trying to get the user connected back in after removing their name from the Deny Access group and trying to get the user setup in Notes again. This is because the NameLookup cache hasn't expired.

To get the user on to the server, you can issue the command "show nlcache reset" on each server they need access to. So if you've got a mail server, directory server, catalog server, Sametime server, app server that they need to get on to, you'll need to go to each server's console and issue the command. Or, you can use the Send Command to Selected Servers dialog in the admin client to send the command once to all the servers you want.

Another use for this command is if a user changes their Internet password and it "isn't working" - submit the command and they'll be able to get in.

Directory Assistance - watch for design changes

Ted Hardenburgh — Tue, 27 Apr 2010 10:10:07 -0700

Working on an issue with directory assistance this morning - an admin had created a new directory database to support external users and added it to the existing DA.nsf. While testing the database, the test external users couldn't login - got an invalid password error everytime. Reviewing the configurations, everything looked fine.

I got involved and enabled debug_directory_assistance=1 and debug_namelookup=1 and started testing. The debug output revealed that the search wasn't hitting the new directory database, even though a "show xdir" showed it was there and further checking revealed it was configured as expected.

Then I went to look at the design and found out something interesting. There were duplicate views and forms in the database, and the database was using a "newer" design than the server. After replacing the design of the database and rebuilding the views, the users were able to login successfully.

There is a technote that describes this situation as well, though it refers to Domino 7, guess it isn't just that release ;). The important thing to look for is two "Directory Assistance" views visible in the view navigator. If you see this, you'll want to replace the design.

Help us find a cure for cystic fibrosis

Ted Hardenburgh — Wed, 14 Apr 2010 16:30:28 -0700

As many of you that know me are aware, my son Andrew has cystic fibrosis. He's 15 now, a freshman in high school and on the freshman baseball team and also participates in Model United Nations. He's pretty healthy for someone with the disease and we're very grateful.

Great Strides is the biggest fund raiser for the Cystic Fibrosis Foundation and I'm asking for your help. Please make a donation by clicking the link here, or use the button on the right side of the website. The CF Foundation is the biggest supporter of research to find a cure and development of new therapies for CF patients.

Please watch the video by comedian and long-time CF Foundation supporter Lewis Black ("The Daily Show") for more information. Thanks!

You can find more info at his site - http://andrewsangels.com

How to max out a Notes database

Ted Hardenburgh — Fri, 26 Feb 2010 07:43:00 -0700

Working with a client recently, we came across some unusual behavior with one mail file. The user reported that his database had gotten to be 64GB and he wasn't sure how. Looking at the database properties, it did show up as 64GB, but there were only around 10K documents and the percent used in the database was around 3%. Something wasn't quite right.

Running a compact -c managed to get the database back down to around 2 GB, but over a few days, the database grew again to where it was 7 GB with no document growth as the user was archiving documents as well. I created a new replica of the database and monitored the size for a few days and it remained steady, nothing like the original. Looking at the database properties on the original database, I found that the Advanced Database property to "Optimize Document Table Map" was checked for some reason. This isn't the normal setting for a mail file, and apparently there's a reason for it.

While this setting is supposed to improve performance of databases, in this case it didn't. This may be due in part to the use of views that are Form specific can cause too many documents to be eligible for inclusion in a view - I'm not a developer so I can't be definitive about it.

To fix this issue, a compact -f was executed to disable the setting and correct the database size. After that was done, the database has seen "normal" growth since.

So the lesson here is - just because you read that something is good for you, doesn't always make it so.

Lotus Notes Diagnostic Failure Reports - How Not to Use Them

Ted Hardenburgh — Wed, 24 Feb 2010 09:30:18 -0700

I came across a Twitter post that referenced a Facebook photo gallery (Facebook login required) that a user posted regarding all the crashes and fault reports he was filling out, and evidently not getting any response. Reading the comments the user adds, he isn't getting a response from the recipient of the comments.

The fault report can be a valuable tool in resolving issues - or it can send your users further over the edge if not used wisely. Here are my suggestions if you're going to enable comment collection on the fault reports:

If you're going to ask your users for comments after a crash, you better read them and act on them. They are already "unhappy" about whatever lost documents/data they were working on, don't make it worse by not doing anything with the information they give you.

Respond to the comments. Acknowledge the user's comment so they at least think you're doing something about it. That way the user gets that "warm fuzzy" feeling that you care. This alone can help win a user over.

If you don't want the comments, configure the ADC to just submit the crash files in the background so the user isn't involved. This way you'll get the information you want, and not make your user any more upset than they currently might be.

Actually look at the diagnostic reports and see what's going on!! I can't tell you how many times I take a look at a customer environment where they have diagnostic collection configured and just ignore it - it's a black hole that apparently no one cares about. Well, my friends, that's the first step to user/management anger and enough reason to find something else that "works" better.

One more thing, if you collect the crash info, run the analyzer task on the database so you can see if there are some issues occurring more often than others and then find the fix. Many times there's a Hot Fix or update to a new maintenance release that resolves the issue. Things you can push out easily with SmartUpgrade - this is where it really proves useful.

IBM Tech Note - What is Automated Diagnostic Collection?

N/D 8.5 Admin Help - Setting up automatic diagnostic data collection on clients

Deploying Blackberry Custom Apps and device.xml

Ted Hardenburgh — Wed, 23 Sep 2009 11:17:41 -0700

We're working with a customer on deploying a custom app to some users' Blackberry devices and everything so far has gone well. One user called to say that they haven't seen the icon on their device yet. Going through the BES policy logs (thankfully, one of the smaller logs), I found that the user was causing the following error to be written to the log:

[20000] (09/15 13:47:13.750):{0xB70} {username@domain.com, PIN=XXXXXXXX, UserId=419}PollForMissingApps: GetHHCodePackages reported: HHCM_DEVICE_NOT_SUPPORTED. Upgrade your copy of device.xml

Device.xml is the "master" list of Blackberry devices. It includes model numbers, networks, and other information. It is something that is copied into software packages by the apploader. If the device isn't listed in the device.xml file, the software doesn't get deployed. Checking the BES, the user had a model 8830m and our device.xml on the server didn't know what that was. So there you go... any devices put out since this client's BES software was installed - and it's not that old, would be excluded from installing software.

To resolve the issue, you need an updated device.xml. Where does one obtain a new version if they aren't ready to install BES 5.0? Why, update your Blackberry Desktop Software, of course. There's a RIM technote that tells the reader to just install the desktop software on the server, but why install Desktop software on a Server, especially when all you need is one file? How about this - update the Desktop software on your Desktop and copy the file you need to the server? The device.xml file is kept in c:\Program Files\Common Files\Research in Motion\AppLoader. You need to replace it in the similar location on the BES server.

Next, on the BES server, go to the :\Program Files\Common Files\Research in Motion\shared\applications folder and in each application you've deployed, delete the PkgDbCache.xml and the specification.pkg file. Also, go to the :\Program Files\Research in Motion\Blackberry Enterprise Server\PackageCace folder and delete all the subfolders in it.

Now you can open up a command prompt and go to :\Program Files\Common Files\Research in Motion\AppLoader and enter the command "loader /reindex" to rebuild all the packages and include the updated device.xml.

If you need to resend the software to the users, you can go into the Blackberry Manager, right-click on the user's name and choose the "Deploy Applications" action to force the policy to be checked. Once this was done, the user's device picked up the software deployment policy and downloaded the application.

So, if your users get new devices quicker than you update the BES software, you'll want to check the device.xml file and update it before you deploy a custom app to them via the BES.

And one other item - what's with the using "you" and "your" for errors that reference the server. Why not make the error "Upgrade the copy of device.xml on the server" - that's much plainer and easily understood. By no means is this the only instance I've seen that type of error, but just thought I'd throw that out there.

SMTP Mail tries to route to A record instead of MX

Ted Hardenburgh — Wed, 10 Jun 2009 08:33:23 -0700

We've seen this at a couple of clients recently running Domino 8.0.x. A user sends an email to a known, valid email address and it gets rejected. The user receives a Delivery Failure Report with a generic "SMTP Permanent Error" message. We get involved and look at the log and notice that the server which the message was sent to was "domain.com". Looking up the MX records, we find that the MX record should be mail.domain.com or sometimes mail.hostingprovider.com. Domino is using the domain's A record to send mail to for some reason. Evidently the cache used by Domino is incorrect. Stopping and starting the router resolves the issue for the near term, but we have seen this come back periodically.

There's a technote that talks about this issue. The workaround is to create a program document that periodically calls the "tell router update config" command which forces the router to clear the cache and try all pending messages again. We normally will set the program to run once an hour to reduce the possibility of a user reporting an issue. There also may be a hotfix for this if you contact IBM Support. The technote refers to Domino 7, 8 and 8.5 as possible releases where this can occur.

For those that may not know how to create a program doc that calls a server console command:

Create a new program document in the Domino directory.

On the Basics tab, the Program field should have "nserver" entered.

In the command field, enter "-c "tell router update config"".

Change the schedule to whatever you're comfortable with.

Save and close the document.