smaller reset larger        English         

Main Menu

All times are in GMT -8 (DST) :: The time is now 4:49 am.

Sub Menu

Category Details
Category Name
Category Created
Fri, 19th Oct 2007
Last Article Update
Tue, 28th Oct 2014
Category Actions


Apple OS X HFS filesystem bug 

Some of our customers had reported HFS filesystem errors or kernel panics on the Apple OS X platform, when using OS X versions 10.4.X and possibly previous. This problem would cause the system to crash, and/or put entries in the system logs like the following:

panic(cpu 3 caller 0x002F7CB9): hfs_vnop_link: error 2 updating vp @0xb8ebf78

We have received some level of notice from Apple that this bug/problem was fixed in Apple OS X 10.5 (Leopard). [Please note: 10.5.1 has been released, and we would recommend upgrading to (Leopard) 10.5.1 as some other problems were introduced in 10.5 that affected Flash Player and some other miscellaneous issues.]

Initial response from some customers appears to be positive. We are asking the community to provide any additional evidence or confirmation that Leopard indeed eliminates the HFS kernel bug. You can post this info here to mailing list, or send us a private note to my e-mail address, or to
View Full Article Add Comment

Hardware purchasing 

First, please recognize that this is a very difficult question to answer, in a general way. Clearly, you should buy the best hardware you can buy at the most affordable cost and which satisfies the peak workload requirements without wasting either system resources or money.

That said, we can suggest the following:

1. Use hardware and operating systems that your IT/administrative team is comfortable with - if you cannot administer your environment, it does not matter how good that hardware or OS might be.

2. For hardware purchasing, CommuniGate Systems often recommends “horizontal scaling” using more, smaller systems rather than fewer, larger (more expensive) systems. Using horizontal scaling generally provides the optimal cost-per-message while simultaneously building more redundancy into the system. As a general guideline, CommuniGate Systems

• 1-to-4 (dual) CPU systems or blades, 2-4GB RAM

• Dual-fans/dual-power supplies are generally recommended for system resiliency to common hardware problems.

• For highest levels of redundancy, mirrored internal disks, 36-72GB in size.

• Again, for redundancy, dual-NIC cards trunked/bonded to the network is a good idea, though not required.

• Frontend servers have e-mail (SMTP) queues - these queues can use a significant amount of disk I/O, so at times adding an additional internal disk to these systems or mounting these queues on NAS/SAN/DAS is useful for performance and redundancy, but not always required.

• Backend servers are attached to the NAS/SAN to access a Shared Logical Volume(s) with a Shared File System (NFS or Cluster File System).

• The NAS/SAN device can be sized initially for short-term growth; however, we strongly recommend that future growth is considered when purchasing storage. The NAS/SAN device should have additional disk capacity and must be capable of growing or extending the available logical volumes (or at the least, be capable of adding additional logical volumes available to all Backends). If those logical volumes can be expanded while the filesystem is mounted and the cluster is online, all the better - the Dynamic Cluster should never need to be brought down then in order to expand the storage volume of the environment.

* In general, CommuniGate also recommends for performance benefits that all volume concatenation or striping (RAID) occurs at the array hardware or array integrated-management level, and not through system or software-level volume management.

View Full Article Add Comment

Linux installation packages 

CommuniGate releases Linux builds of CommuniGate Pro in two primary formats, RPM and non-RPM:

RPM - uses Dynamic/Shared Library linking (more efficient, more tunable, will take advantage of the latest operating system builds and tuning parameters)

non-RPM - uses Static Libraries only (theoretically more stable, probably less efficient)

If your system is under significant load (over 1024 concurrent file descriptors required), you are probably better off using the RPM version of CommuniGate Pro.

The tgz version is statically compiled while the RPM version is a dynamically compiled binary. The dynamically compiled version is recommended when it can be used, as it can then be configured according to the limits of the operating system you use, and therefore will have much higher performance capacity.

For Linux distributions which do not natively support RPM, you may be able to find an optional RPM management package for that distro. Also, RPM packages can be converted into some other package types, such as "rpm-to-apt" or "alien", among others.
View Full Article Add Comment

MacOS X: Mountain Lion Installation of CGP Server, Plugins and Filters 

This is part of the new security features in the Mountain Lion OS. In order to get around this you will need to open up the System Preferences. Once there chose the Security & Privacy option. Click on the lock to make changes and enter the appropriate password. Select the Anywhere option for 'Allow applications downloaded from:'. Close the System preferences then attempt the restall again.

Once done, change the settings back to the Mac App Store.

View Full Article Add Comment

OS X - Error - There is nothing to install 

Please launch the OS X terminal application (Applications | Utilities | Terminal) and issue the following command:

rm -r /Library/Receipts/CommuniGatePro.pkg/ (You must have administrative rights to do this)

Once the CommuniGatePro.pkg directory has been removed, quit the installer application and run it again.

Thank should do the trick.
View Full Article Add Comment

Support for 'pkgng' with FreeBSD Installation 

We plan to support the new package format in packages for FreeBSD 10 (and probably 9) starting with CGPro 6.0.11/6.1.

Support for FreeBSD 7 will be dropped.

There's a test package available here:

View Full Article Add Comment

Upgrading CGP in Snow Leopard 

The problem is in how Apple has changed the behavior of installation receipts.

What you get now is a file called /Library/Receipts/InstallHistory.plist. And when CGP is installed, a section in this file with the following contents:

               <string>CommuniGate Pro</string>

In addition, you also will also get the following files:


So to upgrade you may need to text edit the InstallHistory.plist via vi and remove the two files in the receipt directory.
View Full Article Add Comment