GAS 6.00 upgrade guide

These topics describe product changes you must be aware of when upgrading to version 6.00.

Important:

This incremental upgrade guide covers only topics related to the Genero Application Server (GAS) version specified in the page title. Check prior upgrade guides if you migrate from an earlier version, and complete the migration tasks for all versions between your existing version and the target version, in order. Make sure to also read about the new features for this version.

Corresponding new features page: GAS 6.00 new features.

Previous upgrade guide: GAS 5.01 upgrade guide

New GAS resources to support Prometheus

Prometheus support added to GAS — new resources:

  • res.prometheus.address: Prometheus server URL
  • res.prometheus.enabled: enable/disable metric collection
  • res.prometheus.port: listening port (default 8451)
  • res.prometheus.rq_application_duration.buckets (histogram application bucket)

  • res.prometheus.rq_service_duration.buckets (histogram service bucket)

  • res.prometheus.rq_static_duration.buckets (histogram static file bucket)

These configure the PROMETHEUS element. For details, go to Monitoring the GAS with Prometheus.

Prometheus metrics for GIP (via GAS)

Genero Identity Provider (GIP) services now support Prometheus metrics collection. When GAS is configured to enable metrics, GIP metrics are processed through GAS. These metrics let you monitor GIP usage and reliability — for example, authentication request counts, authentication error counts, and active session counts. For configuration details, go to Monitoring the GAS with Prometheus. For information on the specific metrics collected, go to GIP metrics.

Prometheus metrics for delegation services (via GAS)

GAS now processes Prometheus metrics from the Genero delegation services included with FGLGWS (OpenID Connect, OAuth2, and SAML). When GAS is configured to enable metrics collection, delegation metrics are forwarded and can be monitored using standard Prometheus tools. For configuration details, go to Monitoring the GAS with Prometheus. For information on the specific metrics collected, go to OpenID Connect Service Provider metrics and SAML Service Provider metrics.

Daily log rotation for long-running processes

GAS now fully supports daily log rotation at local midnight: it closes prior-day files and creates a new date-stamped directory with fresh log files so logs are kept per calendar day and active logs appear in today’s folder.

Previously, when a process such as a web service spanned many days, the logs started for that service existed only in the directory of the day the service started. A service started on day 0 continued to write into day 0’s logs for as long as the service ran; for example, on day 7, the logs were still being written into the log files created on day 0. This made some logs for long-running processes hard to find - you had to search for when the service started - and could cause file-not-found or write errors if deleting or compressing a timestamped directory as part of a log backup and rotation strategy. Daily log rotation addresses these concerns by rotating the logs at midnight by creating new logs for all active applications and services in a new current day folder.

For more information about logs, go to Log files.

Retransmission requests now logged in uaproxy

Starting with GAS versions 3.21.04, 4.01.08, 5.01.04, and 6.00.01, retransmission requests are recorded in the uaproxy log. These entries use the WARNING level instead of DEBUG to indicate that a client resent a request because the original response was not received. Retransmission entries can indicate potential network issues between the user agent and GAS.

Example log entry:

18:01:12.937000 "Retransmission" uri=/ua/sua/a2e7f6512783b2f2c440c7fc0a379cca?ConnectorURI=&appId=0&pageId=6

To troubleshoot retransmission requests, go to Retransmission requests in uaproxy logs.

Log category entries added to GAS logs

Starting with GAS versions 3.21.04, 4.01.08, 5.01.04, and 6.00.01, each GAS log file (dispatcher, proxy) begins with an entry showing the current log category. GAS also adds a new entry whenever the log category changes, including when you run gasadmin reset-log. This makes it easy to confirm the active log category (for example, ALL) across all logs. 

#Version: 1.0
#Date: 2025/10/22 17:10:26.099000
#Log category: WARNING ERROR INFO

For more information about logs and filter categories, go to CATEGORIES_FILTER and Log files.

Changes to the Systemd service templates

The systemd service templates for Linux® have updates for the following:
  • The User= and Group= directives are added for dispatcher processes, allowing you to specify the user and group that run the dispatcher process.
  • SELinux-related directives are included in the template as commented-out examples for environments where SELinux is enabled and enforcing.
For more details, go to Systemd service template

Changes in earlier versions

Make sure to check the upgrade notes of earlier versions, to not miss changes introduced in maintenance releases. For more details, see GAS 5.01 upgrade guide.