Release LoadGen Insight Agent: 1.0.0.13236

Release LoadGen Insight Agent: 1.0.0.13236

Linux and macOS agents only: every change in this release applies to the Linux and macOS agents. Windows agents are unchanged.

Linux hosts installed from 1.0.0.12962: the packages of that build report the version 5.281.1, so the package manager treats this version as a downgrade. On Debian and Ubuntu install it with apt install --allow-downgrades (or dpkg -i); on other distributions use the package manager's option to allow a downgrade. The service fixes below reach a host through a package installation: a self-update replaces only the agent programs.

New Features

  • Unattended Enrolment on Linux - Place /etc/loadgen/bootstrap.env with LOADGEN_PLATFORM_URL, LOADGEN_API_KEY and, optionally, LOADGEN_MACHINE_GROUP_ID on the host before you install the deb, rpm or apk package, and the installation enrols the agent and starts its services, without the API key on the command line. After a successful enrolment the file is removed. If the enrolment fails, the file stays, the reason is printed and the installation still completes. To enrol from such a file by hand, run sudo loadgen-control --setup-platform --from-file <path>.

Enhancements

  • Failed Self-Updates Retried With a Back-Off - A Linux or macOS agent whose self-update fails no longer tries again at every check-in. It logs the failure once, with the step that failed and the time of the next attempt, and waits 10 minutes after the first failure, doubling the wait after each further failure up to 6 hours, as the Windows agent does. A different version, file or download link is tried at once, and the agent remembers the failure across a restart.
  • Gradual Rollouts Respected - When a machine group rolls out an agent version in the Gradual mode, Linux and macOS agents now wait for their own batch, as Windows agents do, instead of updating at the first check-in.
  • Clearer Configuration Errors - When the control service cannot read its configuration, the message now tells a missing file apart from an unreadable one. For a permission problem it names the folder that blocks access, its owner and mode, the account the service runs as, and the command that fixes it.

Bug Fixes

  • Fixed the Control Service Not Starting After Enrolment - On Linux, after sudo loadgen-control --setup-platform the control service did not start and logged load platform config: open /etc/loadgen/control/platform.json: permission denied (run --setup-platform first) every few seconds, until the configuration folder was handed to the service account by hand. Setup now gives the configuration to the service account itself, and its confirmation line shows the owner. No manual chown is needed.
  • Fixed Metrics Not Reaching the Platform on Linux - The check-in worked, but the collector could not connect to the control service (dial unix /run/loadgen/insight.sock: connect: permission denied), so no metric left the host and the Data Health page showed "Never" for every feature of the machine. The collector now connects and metrics are sent.
  • Fixed the Control Service Failing After a Reboot - On Linux with systemd, the control service could fail with 226/NAMESPACE after the first reboot following the installation. Its runtime folder is now created at every start.
  • Fixed Services Restarting Endlessly Without a Usable Configuration - On Linux with systemd, a service started before enrolment, or with a configuration it could not use, restarted every few seconds and filled the journal. A host that is installed but not yet enrolled, such as a golden image, now skips the start of both services cleanly. A configuration that exists but cannot be used stops the control service with one error and status=78/CONFIG; fix the cause and start the service again.
  • Fixed the Wrong Agent Version on Linux and macOS - The Linux and macOS programs and packages of build 1.0.0.12962 reported the version 5.281.1 instead of 1.0.0.12962. Every Linux and macOS agent now reports its real build version, so the Platform can tell whether it is up to date.
Was this article helpful?
0 out of 0 found this helpful