Private Synthetic Showing an Shutting Down Message

[amorye]

Hello Team,

I have been working on a Client project and saw the message for configured private synthetic active gate i.e. "Synthetic Engine status​ Shutting down" message. Below are the details of the active gate.

Active Gate Version - 1.303

Chromium Version - 129

Also, in the logs I am seeing below error message.

2025-10-13T08:59:35,258Z INFO [SimpleMessageBus-1] VucMain: Engine shutdown requested: ShutdownRequest{creator='ModuleDiagnosticsService', reason=Monitoring modules failed to be operational in configured time limit}
2025-10-13T08:59:35,259Z INFO [SimpleMessageBus-1] TerminatingServiceImpl: Calling system exit with code 23
2025-10-13T08:59:35,262Z INFO [monitoring-modules-1] BrowserMonitoringModule: Pausing browser monitoring module issued.
2025-10-13T08:59:35,262Z INFO [monitoring-modules-1] VucHibernator: Pause command issued
2025-10-13T08:59:35,263Z INFO [monitoring-modules-1] PeriodicVisitFetcher: FetchExecutor has been paused.
2025-10-13T08:59:35,263Z INFO [monitoring-modules-1] BrowserGuiceModule: Pause requested, removing diagnostic test from the queue..
2025-10-13T08:59:35,266Z INFO [monitoring-modules-1] VucHibernator: Paused module browser - all conditions were met in 00:00:00.002
2025-10-13T08:59:35,266Z INFO [monitoring-modules-1] BrowserMonitoringModule: Pausing browser monitoring module finished.
2025-10-13T08:59:35,275Z INFO [monitoring-modules-1] BrowserMonitoringModule: Shutting down browser monitoring module issued.
2025-10-13T08:59:40,253Z INFO [monitoring-modules-1] AwsS3CloudFileManager: Shutting down
2025-10-13T08:59:40,253Z INFO [monitoring-modules-1] AwsS3CloudFileManager: Shutting down finished

Can you please help me on this.

Regards,

Abhijit Morye

[HannahM · Accepted solution]

Can you check the troubleshooting steps in Why is my Synthetic ActiveGate shutting down?

[t_pawlak · Accepted solution]

Hi
Ensure Synthetic module = 1.303 as well (must match the ActiveGate major).

Which module fails?

On the AG, open vuc-status.log
I don't remember exacly but try find something like this → which of BROWSER/HTTP/HTTP_SCRIPT/MULTIPROTOCOL has isOperational=false. Then check the matching log (vuc-browser*.log or vuc-http*.log) for ERROR/WARN.

Chromium startup issues (common on Linux)

In vuc-browser.debug.log, look for:

 * missing libs (error while loading shared libraries) → install the mentioned RPM/DEB (e.g. dnf install libdrm mpg123-libs mesa* on RHEL 9).

 * TEMP path on Ubuntu/snap → set TEMP=/var/tmp/....

Security software

 * Exclude AG/Synthetic/Chromium paths from AV/EDR. Chromium 129 is stricter—exclude the exact Chrome binary used by Synthetic.

Restart services after fixes

systemctl restart vuc.service