Troubleshooting Error Return Code 2325

Summary

This article provides suggestions for troubleshooting error return code 2325.

Symptoms

When nodes are configured by IP address or logical host name, an error similar to the following can appear in your job log:

71.100.100.31 2/11/2004 2:53:43pm SNBJH_3038E *** ssdatmgr returned error 2325 (reqid=31, function ID=1103) ***

 

Resolution

You can find more information about this problem by looking in the DMM log (ssdatmgr.<pid>.log in the SSPRODIR\logs directory. When the DMM encounters an error, it will log the context for that error (for example, what function call from which module produced it.) For example, consider the following contents of a DMM log:

Time(Feb 11 14:53:43):TID(2292): | Error: Caught bex exception: ERR_DMM_NODE_NONE_FOUND

Time(Feb 11 14:53:43):TID(2292): | - Could not find a node matching the specified pattern (ipddrs(127.0.0.1)).

Time(Feb 11 14:53:43):TID(2292): | - While processing (dmm_node_find_via_ip_addrs)

Time(Feb 11 14:53:43):TID(2292): | - with req = ((ip_addrs=std::vector("127.0.0.1"),node_name_guess="lux-as3"))

Time(Feb 11 14:53:43):TID(2292): | - from user(ssjobhnd) via ssjobhnd@71.100.100.31

 

In this case, the problem may have been caused by the configuration of the lux-as3 node mentioned. Adding a domain entry to the /etc/resolv.conf file, similar to the following, resolves the error:

domain bex.catalogicsoftware.com

 

Also, the /etc/hosts file would require modification to remove a reference to lux-as3 on the line naming 127.0.0.1 nodes.