The error you are getting indicates that the collector is trying to store data in its local file but is unable to as the queue is full. The collector should only try and store data locally when it is unable to contact the listener process on the DPA server.
This would suggest that the collector is unable to communicate with the DPA server on port 4001. Please can you check if this port is open? A good test would be to do a telnet on the collector server to the DPA server using port 4001:
telnet dpa_server_name 4001
If the flashing prompt comes back then it means it has connected ok. If it doesn't connect then please investigate if there are any firewalls blocking communication on that port. If it does connect then please try restarting the collector process/service to see if that resolves the issue.
If you are unable to resolve the issue using the above then please raise a support ticket via EMC Powerlink, so that a member of the DPA support team can investigate further.
Yes, the error message in dpaagent logs ‘Store and forward queue is full - requeueing request’ indicates that the agent cannot send the data to the App server. It could be due port connectivity and/or agent configuration:
1. The agent should be able to communicate to the App server on port 9002 and the App server should connect to the agent on port 3741
2. In the dpaagent_config.xml file under \agent\etc folder you may want to update the new IP address of the App server. See example from lab system:
600
6.3.0.100918
10.20.30.10 >
9002
true
/opt/emc/dpa/agent/logs/dpaagent.log
Info
99614720
/opt/emc/dpa/agent/_jre
All of the local agents and the DS server agent should show the new IP address of the App server. For the App server agent that line should be like:
127.0.0.1
Note – Agent services restart is required for the changes to take effect
DavidRussell1
141 Posts
0
February 11th, 2013 01:00
Hi,
The error you are getting indicates that the collector is trying to store data in its local file but is unable to as the queue is full. The collector should only try and store data locally when it is unable to contact the listener process on the DPA server.
This would suggest that the collector is unable to communicate with the DPA server on port 4001. Please can you check if this port is open? A good test would be to do a telnet on the collector server to the DPA server using port 4001:
telnet dpa_server_name 4001
If the flashing prompt comes back then it means it has connected ok. If it doesn't connect then please investigate if there are any firewalls blocking communication on that port. If it does connect then please try restarting the collector process/service to see if that resolves the issue.
If you are unable to resolve the issue using the above then please raise a support ticket via EMC Powerlink, so that a member of the DPA support team can investigate further.
HTH
David
David Russell
EMC
SCM5OL1l2b12580
2 Posts
0
February 11th, 2013 01:00
Many Thanks David for your prompt reply. I will go ahead and check . I will update this forum with the results soon.
Satadru Roy
Valentin88
10 Posts
0
January 2nd, 2014 02:00
Hello,
I have the same errors in the dpaagent.log - Store and forward queue is full .
Was this problem solved after opening the port 4001 on the dpa collectors ?
Telnet on port 4001 from the collectors to the dpa server is now working for me at this moment.
Many thanks,
CatalinM.
Caly1_4997e3
4 Posts
1
April 5th, 2017 09:00
Yes, the error message in dpaagent logs ‘Store and forward queue is full - requeueing request’ indicates that the agent cannot send the data to the App server. It could be due port connectivity and/or agent configuration:
1. The agent should be able to communicate to the App server on port 9002 and the App server should connect to the agent on port 3741
2. In the dpaagent_config.xml file under \agent\etc folder you may want to update the new IP address of the App server. See example from lab system:
600
6.3.0.100918
10.20.30.10 >
9002
true
/opt/emc/dpa/agent/logs/dpaagent.log
Info
99614720
/opt/emc/dpa/agent/_jre
All of the local agents and the DS server agent should show the new IP address of the App server. For the App server agent that line should be like:
127.0.0.1
Note – Agent services restart is required for the changes to take effect