DPA stopped collecting data

Question

Hi, Hope I can get this question answered here, I won't need to raise a call with support then. Our DPA stopped providing any data in the reports last week. I think I've traced the problem but not the answer. In the collector log it's continually sending out WARN     2284.4892     20110510:095229       fwk.ctrlr.auth - cProcessAuthenticationData(): Process authentication failed with out of date password by deduction I'm assuming that a password has expired or been changed, that was hard! The question is which password for which account and where is it stored? It's not the one I thought it would be i.e. the account the services start with as I've stopped and started DPA and it fires up just fine. In case it helps we are using Version: 5.7.1 build 5794 on Windows 2003 R2 SP2 Thanks in advance Martin.

DavidRussell1 · Accepted Answer

Hi Martin,

What this message actually means is that the timestamp on the host where the collector is running and the timestamp on the DPA Server are not within the allowed time of each other. By default the allowed time is 900 seconds, which equates to 15 minutes.

When the Collector starts up and contacts the Controller it passes in its timestamp and if it is within 15 minutes of the time on the DPA Server then the authentication succeeds. However if it is not, then the authentication process fails and you get the message in the collector log that process authentication failed with out of date password.

To enable the collector to start up you should time synch the 2 servers so that they are within the 15 minute tolerance of each other. If it is not possible to do this then you can modify the time difference tolerance which DPA uses. To do this you would need to:

- stop the DPA Services on the DPA Server

- navigate to

- edit the controller.xml file and modify the line that says:
900

- you will need to change this to whatever value you require e.g. to set this to 30 minutes you would change this to:
1800

- save the changes to controller.xml

- restart the DPA Services

Kind Regards

David

David Russell

DPA Subject Matter Expert

bainmc2 · Answer

David, Thanks for the swift response. I'll check it out. Thanks Martin.

bainmc2 · Answer

David, Thanks I'll do just that. Martin.

bainmc2 · Answer

David,

Times look Ok

From Netbackup Master host where collector is

bash-3.2# date

Tue May 10 11:07:43 BST 2011

bash-3.2#

From DPA host

C:\Documents and Settings\bainma01a>time

The current time is: 11:07:24.22

Enter the new time:

C:\Documents and Settings\bainma01a>

Regards

Martin.

DavidRussell1 · Answer

Hi Martin,

Ok that looks fine. At this stage it is probably best that it gets investigated as an SR by support as the next step will be to provide Debug low logs of the collector and controller as the collector starts up. Therefore please can you:

- set the Collector log level to Debug low via the DPA GUI

- set the Controller log level to Debug low via the DPA GUI

- stop the Collector process on the NBU Master

- start the Collector process on the NBU Master

- set the Collector and Controller log levels back to Info via the DPA GUI

- open an SR and provide the collector and controller logs

Using these logs they should be able to trace the collector communication with the controller and see at what point the authentication fails.

Kind Regards

David

David Russell

DPA Subject Matter Expert

bainmc2 · Answer

David, bash-3.2# date Tue May 10 11:38:25 BST 2011 bash-3.2# bash-3.2# date -u Tue May 10 10:38:29 GMT 2011 bash-3.2# Regards Martin

DavidRussell1 · Answer

Hi Martin, On the NBU Collector host can you try running 'date -u' and see what it returns? Kind Regards David David Russell DPA Subject Matter Expert

Data Protection Advisor

Was this post helpful?