Reporting Node: Resolve Data Collector Name Case Sensitivity After ServerDR

Observed Issues After Reporting Node Redeployment and ServerDR.

The following symptoms were identified:

• New data collected after performing ServerDR does not appear in any reports.
• Only historic data remains visible in the Report Browser.
• The data‑collector service logs contain a connection failure.
• A database query shows the data‑collector name stored in lower‑case/upper-case (e.g., data-collector@report ).
• The current hostname of the reporting node is in a different case (upper‑case vs. lower‑case) than the name recorded in the database.

Relevant log entries from /var/log/reporting/logs/data-collector/data-collector.log :

2026-02-10T06:45:00.006Z INFO [] [DataCollectionQuartzScheduler_Worker-1] [c.e.b.d.c.s.DataCollectionJob.execute(17)] - Start to perform data collection.
2026-02-10T06:45:00.007Z INFO [] [DataCollectionQuartzScheduler_Worker-1] [c.e.b.d.c.s.d.c.DataCollectionService.doCollect(93)] - Query systems by data collector data-collector@REPORT.
2026-02-10T06:45:00.113Z ERROR [] [DataCollectionQuartzScheduler_Worker-1] [c.e.b.d.c.a.CollectedSystemApiServiceImpl.findAllByDataCollectorName(227)] - Error finding all by data collector name: data-collector@gcntnb05
java.net.ConnectException: Failed to connect to localhost/127.0.0.1:18455
    at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:297)
    at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:207)
    at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
    at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
    at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
    at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)

Command used to inspect the collector records in the database:

psql postgresql://reporting:Password123\!@127.0.0.1:9003/collected_business_data -c "select * from public.collected_system"

Case‑sensitive mismatch of data‑collector name

The issue occurs because the data_collector_name stored in the reporting node database is case‑sensitive. After redeploying the reporting node, its hostname is in upper case, while the original hostname recorded during ServerDR was in lower case. This discrepancy prevents the data collector service from locating the correct entry, causing data synchronization failures.

• The database entry for data_collector_name is stored in lower case (e.g., data-collector@report ).
• The current hostname of the reporting node is upper case, but the previous ServerDR hostname was lower case (e.g., REPORT ).
• Because the name comparison is case‑sensitive, the service cannot match the stored name with the current hostname.

Resulting connection error

2026-02-10T06:45:00.113Z ERROR [] [DataCollectionQuartzScheduler_Worker-1] [c.e.b.d.c.a.CollectedSystemApiServiceImpl.findAllByDataCollectorName(227)] - Error finding all by data collector name: data-collector@REPORT
java.net.ConnectException: Failed to connect to localhost/127.0.0.1:18455
    at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:297)
    at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:207)
    at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
    at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
    at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
    at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)

Recover Reporting Node Data After ServerDR.

Option 1 – Redeploy Reporting Node with Correct Hostname.

Use this method when you prefer a clean redeployment.

• Ensure that the new reporting node hostname matches the original hostname **exactly**, including case (e.g., REPORT vs report ).
• Redeploy the reporting node using the correct hostname.
• Perform ServerDR (Server Disaster Recovery) on the reporting node again.

Option 2 – Update Data Collector Name Directly in the Database

Use this method to avoid a full redeployment.

1. Log in to the reporting node with appropriate privileges.
2. Verify the current data‑collector entries:

   psql postgresql://reporting:[PASSWORD]@127.0.0.1:9003/collected_business_data -c "SELECT * FROM public.collected_system;"        

3. Identify the row that contains the old hostname and note its address value (e.g., 192.168.1.15 ).
4. to match the current hostname case:

   postgresql://reporting:[PASSWORD]@127.0.0.1:9003/collected_business_data -c "UPDATE public.collected_system SET data_collector_name='data-collector@[HOSTNAME]' WHERE address='[IP_ADDRESS]';"       

   Replace [HOSTNAME] with the exact hostname of the reporting node (case‑sensitive) and [IP_ADDRESS] with the address identified in step 2.
5. Restart the data‑collector service to apply the change:

   systemctl restart data-collector.service        

Verification

• Check the data‑collector log for successful queries:

  cat /var/log/reporting/logs/data-collector/data-collector.log | grep -i "Start to perform data collection"       

  No ConnectException errors should appear.
• Wait for around one hour, then open the Report Browser and verify that newly collected data appears alongside the historic data.