PMDF System Manager's Guide

An "Error in mm_init" error generally indicates a PMDF configuration problem. Thus the PMDF TEST/REWRITE utility, which is often used to test the health of a PMDF configuration, can return such an error, as can other utilities such as PMDF CNBUILD. PMDF channels or servers can also return such errors, as can user agents attempting to submit messages to PMDF.

In particular, one of the more commonly encountered sorts of mm_init errors is a "No room in table" error or similar "No room in ..." sort of error. Generally, "no room in" errors are an indication that your current PMDF configuration has not set internal table sizes sufficient for the size of your PMDF configuration, and that it is time to have PMDF resize its internal tables, as described in Section 8.1.4.² However, some particular such "no room in ..." error messages can have alternate causes, and such cases are called out below. Any other "no room in" errors not explicitly mentioned are most likely simply an indication of a need to resize internal tables.

Rather than manually calculating and setting table sizes, you should use the PMDF CNBUILD utility to automatically resize the tables for you. See Section 8.1.4 for exact instructions on doing this.

If you use a compiled configuration, then be sure to recompile your configuration and reinstall it after resizing the tables.

If you're using the PMDF multithreaded SMTP server, the PMDF-LAN Lotus Notes channel, or any other services running under the Dispatcher that need to be made aware of the change, be sure to restart such services using the PMDF RESTART utility.

Following are some of the more commonly encountered mm_init errors.

bad equivalence for alias ...

The right hand side of an alias file entry is improperly formatted.

cannot open alias include file...

A file included into the alias file cannot be opened. This typically indicates a protection problem with a file referenced by the file include operator, <. Note that such included files (like the alias file itself) must be world readable.

duplicate alias(es) found ...

Two alias file entries have the same left hand side; you will need to find and eliminate the duplication.

duplicate host in channel table ...

In its literal meaning, this error says that you have two channel definitions in the PMDF configuration that both have the same official host name (line two of the channel definition); see Section 2.3.2. But note that an extraneous blank line in the rewrite rules (upper portion) of your PMDF configuration file causes PMDF to interpret the remainder of the configuration file as channel definitions, and as there are often multiple rewrite rules with the same pattern (left hand side), this then causes PMDF to think it is seeing channel definitions with non-unique official host names. So check your PMDF configuration both for any channel definitions with duplicate official host names, and for any improper blank lines in the upper (rewrite rules) portion of the file.

duplicate mapping name found ...

This error literally means that two mapping tables have the same name, and one of the "duplicates" needs to be removed. However, note that formatting errors in the mapping file can cause PMDF to interpret something not intended as a mapping table name as a mapping table name; for instance, failure to properly indent a mapping table entry will cause PMDF to think that the left hand side of the entry is actually a mapping table name. So check your mapping file for general format, as well as checking the mapping table names.

error initializing ch_ facility: ...

Note that such errors should not occur in normal operation; only sites that have customized PMDF character set material, or have had installation problems, are likely to encounter such errors. The next two items describe sorts of ch_ facility errors that are simple to resolve; other sorts of ch_ errors, however, often indicate that required PMDF files have not been properly installed or have been unintentionally deleted or otherwise corrupted, and a re-installation of PMDF can be necessary to get the required files properly installed. Contact Process Software if you have questions regarding such an error.

error initializing ch_ facility: compiled character set version mismatch

Such an error generally means that you need to recompile and reinstall your compiled character set tables via the commands:

$ PMDF CHBUILD $ INSTALL REPLACE PMDF_CHARSET_DATA

See the documentation for PMDF CHBUILD for additional details.

error initializing ch_ facility: no room in ...

Such an error likely means that you need to resize your PMDF character set internal tables and then rebuild the compiled character set tables via the commands

$ PMDF CHBUILD/NOIMAGE/MAXIMUM/OPTION $ PMDF CHBUILD $ INSTALL REPLACE PMDF_CHARSET_DATA

See the documentation for PMDF CHBUILD for additional details.

local host alias or proper name too long for system ...

This error literally means that a local host alias or proper name (the optional right hand side in the second or subsequent names in a channel block) is too long. However, note that certain syntax errors earlier in the PMDF configuration file (an extraneous blank line in the rewrite rules, for instance) can cause PMDF to interpret something not intended as a channel definition as a channel definition. So besides checking the indicated line of the configuration file, also check above that line for other syntax errors and in particular, if the line on which PMDF issues this error is intended as a rewrite rule, then be sure to check for extraneous blank lines above it.

mapping name is too long ...

This error literally means that a mapping table name is too long and needs to be shortened. However, note that formatting errors in the mapping file can cause PMDF to interpret something not intended as a mapping table name as a mapping table name; for instance, failure to properly indent a mapping table entry will cause PMDF to think that the left hand side of the entry is actually a mapping table name. So check your mapping file for general format, as well as checking the mapping table names.

no equivalence addresses for alias ...

An entry in the alias file is missing a right hand side (translation value).

no official host name for channel ...

This error indicates that a channel definition block is missing the required second line (the official host name line). See Section 2.3.2 for a discussion of the format of channel definition blocks. In particular, note that a blank line is required before and after each channel definition block, but a blank line must not be present between the channel name and official host name lines of the channel definition; also note that blank lines are not permitted in the rewrite rules portion of the PMDF configuration file.

no room in ...

Generally, "no room in" errors are an indication that your current PMDF configuration has not set internal table sizes sufficient for the size of your PMDF configuration, and that it is time to have PMDF resize its internal tables, as described in Section 8.1.4. However, some particular such "no room in ..." error messages can have alternate causes, and such cases are called out below. Any other "no room in" errors not explicitly mentioned are most likely simply an indication of a need to resize internal tables.

no room in channel host table for ...

This error indicates that your configuration's current PMDF internal table sizes are not large enough for the number of host names listed in your channel definitions. However, note that an extraneous blank line in the rewrite rules (upper portion) of your PMDF configuration file causes PMDF to interpret the remainder of the configuration file as channel definitions; with just one such extraneous blank line, PMDF sees just one extra channel but with a lot (all the rest of the rewrite rules) as host names on that channel. So check the line of the file that the error is complaining about---if it is not truly intended as a host name on a channel definition but rather is a line in the rewrite rules section of your configuration file, then check for an extraneous blank line above it.

no room in channel table for ...

This error indicates that your configuration's current PMDF internal table sizes are not large enough for the number of channels defined in your PMDF configuration. See Section 8.1.4.

no room in table for alias ...

This error says that the current PMDF internal table sizes are too small for the number of aliases in the aliases file. This can be resolved either by resizing PMDF's internal table sizes---see Section 8.1.4---or in some cases can be an indication that it would be wise to begin using the PMDF alias database to store some of the aliases currently in the aliases file---see Section 3.1.2.

no room in table for mapping named ...

In its literal meaning, this error says that your configuration's current PMDF internal table sizes are not large enough for your current number of mapping tables. Internal PMDF table sizes can be increased to match your current configuration side---see Section 8.1.4. However, also note that formatting errors in the PMDF mapping file can cause PMDF to think that you have more mapping tables than you really have; for instance, check that mapping table entries are all properly indented.

official host is too long

The official host name for a channel (second line of the channel definition block) is limited to forty characters in length. So if you were trying to use a longer official host name on a channel, shorten it to a "placeholder" name and then use a rewrite rule to match the longer name to the short official host name. Note, however, that certain syntax errors earlier in the PMDF configuration file (an extraneous blank line in the rewrite rules, for instance) can cause PMDF to interpret something not intended as a channel definition as a channel definition; that could result in an intended rewrite rule being interpreted as an official host name. So besides checking the indicated line of the configuration file, also check above that line for other syntax errors and in particular, if the line on which PMDF issues this error is intended as a rewrite rule, then be sure to check for extraneous blank lines above it.