Data Aggregator Service Fails After 25.4.4 Upgrade
search cancel

Data Aggregator Service Fails After 25.4.4 Upgrade

book

Article ID: 429386

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

After upgrading the Data Aggregator from 25.4.3 to 25.4.4 it fails to start and stay running.

The upgrade logs are clean with no errors or failures.

After the upgrade the dadaemon service shows failure to stay running according to "systemctl status dadaemon" output.

Feb 11 21:52:02 <DA_HostName> systemd[1]: Started Data Aggregator.
Feb 11 21:52:07 <DA_HostName> systemd[1]: dadaemon.service: Main process exited, code=exited, status=1/FAILURE
Feb 11 21:52:07 <DA_HostName> systemd[1]: dadaemon.service: Failed with result 'exit-code'.

We see the following error in the $DA_HOME/data/logs/netops-data-aggregator.log file. The specific failure point is bolded.

2026-02-11T21:52:07,386 | ERROR | main             | SpringApplication                | framework.boot.SpringApplication  857 |  -  -  |  | Application run failed
org.springframework.context.ApplicationContextException: Unable to start web server
...
Caused by: org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat
...
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'debugFilterRegistrationBean' defined in class path resource [com/ca/im/dm/aggregator/config/IMDebugConfiguration.class]: Unsati
sfied dependency expressed through method 'debugFilterRegistrationBean' parameter 0: Error creating bean with name 'shutdownManager' defined in class path resource [com/ca/im/dm/aggregator/config/DACoreServicesConfiguration.class]: Uns
atisfied dependency expressed through method 'shutdownManager' parameter 0: Error creating bean with name 'dbStateManager': Invocation of init method failed
...
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'shutdownManager' defined in class path resource [com/ca/im/dm/aggregator/config/DACoreServicesConfiguration.class]: Unsatisfied
 dependency expressed through method 'shutdownManager' parameter 0: Error creating bean with name 'dbStateManager': Invocation of init method failed
...
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dbStateManager': Invocation of init method failed
...
Caused by: java.lang.UnsatisfiedLinkError: /tmp/bc-fips-jni_812111996725359/libbc-probe.so: /tmp/bc-fips-jni_812111996725359/libbc-probe.so: failed to map segment from shared object

Environment

Application: DX NetOps Data Aggregator (DA)

Version: Upgrading from 25.4.3.8 to 25.4.4.3

Cause

The /tmp directory is configured with NOEXEC and the server has FIPS enabled at the OS level.

Resolution

Complete the following steps.

  1. In the $DA_HOME/custom.d directory create a file named fipsErrorFix.
    • Set it's permissions with "chmod +x fipsErrorFix".
    • Ensure it's owned by the install owner.
  2. In the file add this single line, setting the target alternative tmp dir at the end.
    • export CUSTOM_JAVA_OPTS=-Djava.io.tmpdir=<Alternative_tmp_dirLocation>
  3. Save the change to the file after adding that line.
  4. Run "systemctl stop dadaemon" then "systemctl start dadaemon" to cycle the dadaemon service and read the new file.

Once done the DA should remain running once started.

If resolved we should no longer see the error about /tmp/bc-fips* in the /opt/IMDataAggregator/data/logs/netops-data-aggregator.log file.

Additional Information

This is targeted for resolution in the 25.4.6 release.

Powered by Wolken Software