Monthly Archives: December 2005

On the Road

On the Road: Home Just Isn't the Same

There’s a Blues Traveler song about how when you go home it’s never the same that you remember.  This is because you change but also because places have a habit of being trapped in time in your memory while not in reality.  In my last two trips to Dahlonega, my home town, I have not seen a single person I know.  Or have I?  Would I recognize any of them?  I have a feeling I would remember them as they were, like I remember the town as it was, rather than knowing them for who they are.

Xsan

Xsan: Affinity

cvaffinity can be used to assign an affinity to a storage pool in Xsan.  An affinity maps a specified directory to a storage pool.  Therefore, if you have a dedicated capture station and you want to make sure it always has 4gbps of throughput then you can create a storage pool called capture, mark it for use with affinity only, create a folder called capture and assign the affinity for the capture storage pool to the capture folder on the volume.  Now all data written to that folder will be written through the affinity and therefore provide a certain level of Quality of Service to that affinity.

Mac OS X Server

“PWD Failed to Start Listener” Errors in CommuniGate

I originally posted this at http://www.318.com/TechJournal

PWD Service issues on Communigate Pro
When running Communigate Pro on a Mac OS X Server, many users have had issues with an error that reads:
PWD failed to start listener on [0.0.0.0:106]. Error Code=network address (port) is already in use

The PWD service in Communigate Pro is used to interface with Stalker’s custom API for programming extensions to Communigate. This can often just be ignored unless you need to use the PWD service.

This error is caused because another service is already running on port 106 for TCP traffic. Using netstat –a will tell you that it is the passwordservice that is running on port 106. In order to get the PWD service to start for CommuniGate you will need to change the port for one of these two services. The easiest one is by far the CommuniGate Pro PWD service.

To do this:
1. Open your Communigate Pro Administrative Portal (typically 127.0.0.1:8010 from the server)
2. Click on Acccess
3. Authenticate if you are asked to do so
4. Click on listener under the section for Serving PWD Clients
5. Type in a new Port (personally I use 1060, but make sure it doesn’t conflict with any other ports)
6. Click on the Update button

That’s it. Those annoying PWD errors should disappear from your logs. Most people don’t actually use any of the PWD features, but if you do and you are not already getting an error that the PWD service is not running then this could break the API based applications you are using and you may need to customize the port for the application.

Football

Tigers fall to Dawgs

34-14 isn’t a route.  But it’s a good and solid win.  Hey Pollsters, were you watching?!?!