A Distributed Processing Appliance (DPA) is successfully enrolled, however it does not test successfully immediately after enrolling. Both the "Test DPA" button from the TPAM "HA Config" GUI, and the DPA console using the "Check TPAM Connectivity" option fail.
In some instances, this may present perl errors during the testing process. Examples of the errors:
Errors seen running "Check TPAM Connectivity" from the DPA:
Check TPAM connectivity....
Can't locate XML/XPath.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.10.0/i386-linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.10.0/i386-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl .) at /home/edmzdpa/script/chkPAREGP line 4.
BEGIN failed--compilation aborted at /home/edmzdpa/script/chkPAREGP line 4.
Errors returned Testing the DPA using the "Test DPA" button from the TPAM appliance:
The results from the Testof DPA at 192.168.0.1 follow (all times are Server Time):
Active SCP processes: 1
Active SSH processes: 1
Active Putty processes: 0
Active SSHd processes: 1
Use of tied on a handle without * is deprecated at C:/Perl/lib/XML/Parser/Expat.pm line 447.
Testing DPA ID 18 at 192.168.0.10:22
sh: /opt/glassfishv3/bin/asadmin: No such file or directory
The connection attempt was successful!
Application Server:Not Running
DPA DateTime:11/29/2013 12:11:57
TPAM DateTime: 11/29/2013 12:11:57
The DPA may not have completed the initialization activities.
If the "Test DPA" button from the TPAM "HA Config" GUI is run and fails, or the DPA console "Check TPAM Connectivity" fails immediately after successfully enrolling a DPA, it is possible that the DPA has not completed its initialization steps. These tests will often fail if they are run immediately after a successful enrollment. The initialization of the DPA will take a minute or more to fully complete.
To verify DPA initialization is complete, view the DPA console:
Select "6: Logs Menu | 3: Display DPA Initialization Log"
After scrolling to the bottom of the log, verify the line "Initialization end" exists.
If the DPA is being updated to a new version, this could take several minutes. In most cases this should be just a few minutes.
After verifying the line "Initialization end" exists, the above tests should complete successfully.
From the TPAM 2.5.917, when a new DPA 3.3.8 is first enrolled into the cluster, the DPA will be updated to 3.3.12. This process could take as much as 60 minutes. Do not try to access the DPA or reboot the DPA during this time.
Run the Test DPA after 60 minutes to verify the this is not successful.