Check Compact SP Deployment Proxy Setting in case Content Extraction fails

Mar 2023

Introduction

This is pertaining to an SP release in LB 5.0.9 (but not necessarily limited to this release) where there seems to be a bug with running Compact Mode and Content Extraction.
For some reason there is a process called ericsson-stream-processing-content-extraction that is being setup internally with a 'proxy'. The proxy is for comms between the service and whatever calls it in a containerised system, not in a RPM system. The proxy has to be removed, which thankfully is very simple.
To work out the status of the proxy setting we need to check the status of a service, however to get the latest status of the service we need to restart it, this can be done using the following:

systemctl restart ericsson-stream-processing-content-extraction

There is no feedback from this command line.
To check the status of the service use the following:

systemctl status ericsson-stream-processing-content-extraction

This will give an output similar to the following:

● ericsson-stream-processing-content-extraction.service - ericsson-stream-processing-content-extraction
Loaded: loaded (/etc/systemd/system/ericsson-stream-processing-content-extraction.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2023-03-10 12:32:56 UTC; 56s ago
Main PID: 25250 (bash)
CGroup: /system.slice/ericsson-stream-processing-content-extraction.service
├─25250 /bin/bash -c cd /opt/ericsson/stream-processing-content-extraction/lib; dotnet ContentExtraction.dll --urls 'http://+:8082'
└─25251 dotnet ContentExtraction.dll --urls http://+:8082
Mar 10 12:32:56 env-4e-966427 systemd[1]: Started ericsson-stream-processing-content-extraction.
Mar 10 12:32:57 env-4e-966427 bash[25250]: {"time":"2023-03-10T12:32:57.4401338Z","host":"env-4e-966427","appname":"Content Extraction","pri":"INFO","subsys":"ContentExtraction.Startup","msg":"Proxy mode enabled."}
Mar 10 12:32:57 env-4e-966427 bash[25250]: {"time":"2023-03-10T12:32:57.4607425Z","host":"env-4e-966427","appname":"Content Extraction","pri":"INFO","subsys":"ContentExtraction.Startup","msg":"Creating interface discovery client for http://localhost:8200/api/discoveries"}
Mar 10 12:32:57 env-4e-966427 bash[25250]: {"time":"2023-03-10T12:32:57.4681028Z","host":"env-4e-966427","appname":"Content Extraction","pri":"INFO","subsys":"ContentExtraction.Startup","msg":"Enabling housekeeping. Idle time set to 00:02:00 [Checked every 00:01:00]"}
Mar 10 12:32:57 env-4e-966427 bash[25250]: {"time":"2023-03-10T12:32:57.4905264Z","host":"env-4e-966427","appname":"Content Extraction","pri":"INFO","subsys":"Microsoft.Hosting.Lifetime","msg":"Now listening on: http://[::]:8082"}
Mar 10 12:32:57 env-4e-966427 bash[25250]: {"time":"2023-03-10T12:32:57.4906887Z","host":"env-4e-966427","appname":"Content Extraction","pri":"INFO","subsys":"Microsoft.Hosting.Lifetime","msg":"Application started. Press Ctrl+C to shut down."}
Mar 10 12:32:57 env-4e-966427 bash[25250]: {"time":"2023-03-10T12:32:57.4907296Z","host":"env-4e-966427","appname":"Content Extraction","pri":"INFO","subsys":"Microsoft.Hosting.Lifetime","msg":"Hosting environment: Production"}
Mar 10 12:32:57 env-4e-966427 bash[25250]: {"time":"2023-03-10T12:32:57.4907808Z","host":"env-4e-966427","appname":"Content Extraction","pri":"INFO","subsys":"Microsoft.Hosting.Lifetime","msg":"Content root path: /opt/ericsson/stream-processing-content-extraction/lib"}

The important line here is about halfway down and ends with:

"ContentExtraction.Startup","msg":"Proxy mode enabled."}

If we see the text Proxy mode enabled then Content Extraction will fail.
To rectify this we need to edit just one file, the file is located in the following location:

cd /opt/ericsson/stream-processing-content-extraction/lib

In this location find the file appsettings.json and open it in your favourite text editor (or vi).
Around 5 lines from the bottom of the file we will see the entry “enabled”: “true”,

"houseKeepingFrequency": "00:01:00",
"allowedIdleTime": "00:02:00",
"proxy": {
"enabled": "true",
"interfaceDiscoveryAPI": "http://localhost:8200/api/discoveries",
"serverOfLastResort": ""
}
}

We need to set this to “enabled”: “false”,