A.0 Troubleshooting Post-Migration Problems

Messages are not flowing between the migrated POA and the MTA for the domain

Problem: The migrated POA and the MTA for the domain are not able to communicate with each other.
Possible Cause: The source POA was stopped before the configuration changes replicated to the POA.
Action: Manually configure the MTP link between the source POA and the MTA for the domain.

  1. Display the POA console.

    http://source_server_address:port_number

  2. Click MTP Status.

    The status in the Receive column shows Closed.

  3. Click the Closed link,

  4. In the Address field, specify the new IP address of the POA, then select Start MTP Receive.

  5. Click Submit to execute the actions.

The POA cannot start

Problem: The POA tries to start, but exits.
Possible Cause: The POA log file path information has not yet been reconfigured.
Action: Properly configure the log file path.

  1. Start the POA with the /noconfig switch so that the POA ignores the troublesome configuration settings and starts successfully.

  2. Because of the /noconfig switch, manually configure the link between the POA and the MTA for the domain. See Messages are not flowing between the migrated POA and the MTA for the domain

  3. Allow time for the configuration information to replicate from ConsoleOne to the post office database (wphost.db) so that the POA has the correct configuration settings.

  4. Start the POA again.

    It should start successfully this time.

The POA cannot start because of incorrect permissions

Problem: The POA cannot start and displays the following message: 
Error: Running the agent with conflicting effective users
Possible Cause: You are trying to set the POA up to run as a non-root user, but you have already run the POA as root.
Action: Remove the file that is preventing the POA from running as a non-root user.

  1. On the Linux server, change to the post office folder.

  2. Delete the uid.run file.

  3. Start the POA again.

    It should start successfully this time.

The POA cannot start because of a C06B error

Problem: The POA tries to start, but displays a C06B error and exits.
Possible Cause: The post office owns a library that has one or more remote document storage areas and they have not been configured with Linux paths.
Action: Properly configure the remote document storage area.

  1. Start the POA with the /noconfig switch so that the POA ignores the troublesome configuration settings and starts successfully.

  2. Because of the /noconfig switch, manually configure the link between the POA and the MTA for the domain. See Messages are not flowing between the migrated POA and the MTA for the domain

  3. Allow time for the configuration information to replicate from ConsoleOne to the post office database (wphost.db) so that the POA has the correct configuration settings.

  4. Start the POA again.

    It should start successfully this time.

The POA starts with SSL errors

Problem: The POA starts, but messages indicate that SSL is not available.
Possible Cause: The POA SSL certificate and key file paths have not yet been reconfigured.
Action: Properly configure the SSL certificate and key files for the POA

  1. In ConsoleOne, browse to and right-click the POA object, then click Properties.

  2. Click GroupWise > SSL Settings.

  3. Remove the path information from the Certificate File and Key File fields.

    The information pertains to the source NetWare or Windows server, not the Linux server, and is therefore not needed.

    The Server Migration Utility places certificate files and key files in their default location on Linux (/opt/novell/groupwise/agents/bin).

  4. Click OK to save the settings.

  5. Allow time for the configuration information to replicate from ConsoleOne to the post office database (wphost.db).

    When the POA has the correct configuration settings, SSL is enabled as usual.

The POA starts with TCP/IP errors

Problem: The POA starts with the error: 
TCP/IP services on your system may not be configured or installed
Possible Cause: The /ip startup switch in the POA startup file (/opt/novell/agents/share/post_office.poa) still has the IP address of the source NetWare or Windows server.

This would happen only if you manually copied the startup file to the Linux server, because the Server Migration Utility comments out the /ip switch in order to avoid this problem.

Action: Edit the POA startup file and update the IP address to match the Linux server.