craigzour
craigzour
ZZITADEL
Created by craigzour on 5/20/2025 in #questions-help-bugs
Notifier errors since upgraded to 3.0.4
Here is our current config file in case it helps debugging (we reverted that maxconnlifetime change since we still had the issue)
# Default config is merged with the overrides in this file.
# https://zitadel.com/docs/self-hosting/manage/configure#runtime-configuration-file

Log:
Level: "info"

Metrics:
Type: none
Tracing:
Type: none
Profiler:
Type: none
Telemetry:
Enabled: false

Port: 8080
ExternalPort: 443
ExternalSecure: false
TLS:
Enabled: false

Database:
postgres:
Port: 5432
User:
SSL:
Mode: "require"
Admin:
SSL:
Mode: "require"
MaxOpenConns: 20
MaxIdleConns: 10
MaxConnLifetime: "30m"
MaxConnIdleTime: "5m"

DefaultInstance:
LoginPolicy:
AllowRegister: false
ForceMFA: true
HidePasswordReset: true
OIDCSettings:
AccessTokenLifetime: "0.5h"
IdTokenLifetime: "0.5h"
RefreshTokenIdleExpiration: "720h"
RefreshTokenExpiration: "2160h"

OIDC:
DefaultAccessTokenLifetime: "0.5h"
DefaultIdTokenLifetime: "0.5h"
DefaultRefreshTokenIdleExpiration: "720h"
DefaultRefreshTokenExpiration: "2160h"

Notifications:
# Notifications can be processed by either a sequential mode (legacy) or a new parallel mode.
# The parallel mode is currently only recommended for Postgres databases.
# If legacy mode is enabled, the worker config below is ignored.
LegacyEnabled: false
# The amount of workers processing the notification request events.
# If set to 0, no notification request events will be handled. This can be useful when running in
# multi binary / pod setup and allowing only certain executables to process the events.
Workers: 1
# The maximum duration a job can do it's work before it is considered as failed.
TransactionDuration: 10s
# Automatically cancel the notification after the amount of failed attempts
MaxAttempts: 3
# Automatically cancel the notification if it cannot be handled within a specific time
MaxTtl: 5m
# Default config is merged with the overrides in this file.
# https://zitadel.com/docs/self-hosting/manage/configure#runtime-configuration-file

Log:
Level: "info"

Metrics:
Type: none
Tracing:
Type: none
Profiler:
Type: none
Telemetry:
Enabled: false

Port: 8080
ExternalPort: 443
ExternalSecure: false
TLS:
Enabled: false

Database:
postgres:
Port: 5432
User:
SSL:
Mode: "require"
Admin:
SSL:
Mode: "require"
MaxOpenConns: 20
MaxIdleConns: 10
MaxConnLifetime: "30m"
MaxConnIdleTime: "5m"

DefaultInstance:
LoginPolicy:
AllowRegister: false
ForceMFA: true
HidePasswordReset: true
OIDCSettings:
AccessTokenLifetime: "0.5h"
IdTokenLifetime: "0.5h"
RefreshTokenIdleExpiration: "720h"
RefreshTokenExpiration: "2160h"

OIDC:
DefaultAccessTokenLifetime: "0.5h"
DefaultIdTokenLifetime: "0.5h"
DefaultRefreshTokenIdleExpiration: "720h"
DefaultRefreshTokenExpiration: "2160h"

Notifications:
# Notifications can be processed by either a sequential mode (legacy) or a new parallel mode.
# The parallel mode is currently only recommended for Postgres databases.
# If legacy mode is enabled, the worker config below is ignored.
LegacyEnabled: false
# The amount of workers processing the notification request events.
# If set to 0, no notification request events will be handled. This can be useful when running in
# multi binary / pod setup and allowing only certain executables to process the events.
Workers: 1
# The maximum duration a job can do it's work before it is considered as failed.
TransactionDuration: 10s
# Automatically cancel the notification after the amount of failed attempts
MaxAttempts: 3
# Automatically cancel the notification if it cannot be handled within a specific time
MaxTtl: 5m
12 replies
ZZITADEL
Created by craigzour on 5/20/2025 in #questions-help-bugs
Notifier errors since upgraded to 3.0.4
Hello! This is correct. Even though we changed MaxConnLifetime: "30m" to MaxConnLifetime: "1h" the Notifier errors cadence stayed the same (every 30 mins or so)
12 replies
ZZITADEL
Created by craigzour on 5/20/2025 in #questions-help-bugs
Notifier errors since upgraded to 3.0.4
Also just to make sure we are on the same page, we have not touched anything else outside of that Zitadel upgrade.
12 replies
ZZITADEL
Created by craigzour on 5/20/2025 in #questions-help-bugs
Notifier errors since upgraded to 3.0.4
Hello @Rajat . Thank you for spending some time looking into this. I tried to make some small Zitadel configuration adjustments such as: - Tweaking the database connection options (MaxOpenConns and MaxConnLifetime) - Settings up the Notifications options with either LegacyEnabled set to true or false (because I thought it was related to the Notifier word included in the error message)
12 replies
ZZITADEL
Created by craigzour on 5/20/2025 in #questions-help-bugs
Notifier errors since upgraded to 3.0.4
(Bump)
12 replies