You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey back the team, second issue of the evening.
It looks like we cannot make the task scheduler use Redis over an UNIX socket, as for the cache storage or the session provider.
[x]
):Description
Hey back the team, second issue of the evening.
It looks like we cannot make the
task
scheduler use Redis over an UNIX socket, as for thecache
storage or thesession
provider.The service hard-fails at startup with :
routers/init.go:107:GlobalInit() [F] Failed to initialize task scheduler: dial tcp [::1]:6379: connect: connection refused
So this issue got multiple purposes :
addr
becomesaddrs
,
and some other timesnetwork
,pool_size
oridle_timeout
are de facto not interpreted (still according to the parser sources of thetask
scheduler)cache
,session
,task
and issueindexer
connection strings should be configured the same way.Bye again 👋
The text was updated successfully, but these errors were encountered: