similar to: auth_passdb_request_finished request fires twice on IMAP login

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup against Redis is only performed once.

Hello, I'm trying to get some IMAP auth stats on a Dovecot 2.3.6 instance, but whatever I declare in metric, it always show 0. What I want basically is how many IMAP auth attempts there was on the server, and optional a way to filter on the auth attempt status (successful or failed). My server uses a simple auth (with LDAP backend) and supports only "auth_mechanisms = plain login"

> I'm trying to get some IMAP auth stats on a Dovecot 2.3.6 instance, but whatever I declare in metric, it always show 0. None of these auth_* requests exist in 2.3.6. > I tried using the following metrics: > > > -------------------------------- > metric auth_request_finished { > event_name = auth_request_finished > } > > metric

Is there any additional documentation/information around the new stats module. Have added some metrics just to see what they produce ## ## Metrics ### metric imap { ??? event_name = imap_command_finished ??? #source_location = example.c:123 ??? #categories = ??? fields = name args running_usecs bytes_in bytes_out ??? #filter { ??? #??? field_key = wildcard ??? #} } metric sql { ???

Hi, I have a daemon process which is changings things in the system only the superuser should be allowed to change. Lets call it "riskyd". Users use a frontend on the same machine (lets call it "risky"). risky is a SUID program which talks to riskyd by binding to a privileged port, then connecting to riskyd on localhost. riskyd cheks that the connection is coming from

Hi, I am trying to implement a dict lookup for disabled accounts, where both the passdb lookup and the disabled lookup is done in the same passdb. I was hoping that this configuration would work: passdb { name = redis driver = dict args = /etc/dovecot/dovecot-redis.conf.ext } --- uri = redis:host=127.0.0.1 key disabled { key = users/%u/disabled/%s format = value

Are there any examples of the utility of doveadm stats? in the man page: > dump accepts following types: command, session, user, domain, ip and > global. > > Filter can be > > user=<wildcard> > Match given user. I've tried the following commands after looking at the (sparse and example-less) man page. # doveadm stats dump

Hi Jeff, Thanks for your reply! Regarding grouping by remote address, I understand and for now I'll keep a close eye. Maybe it's an option to group by /24 for ipv4 and /64 for IPv6? We currently do that based on the logs but the OpenMetrics endpoint seem a lot easier. A slight hijack of the original question: but I tried to log only IP addresses (+ result) of failed login attempts but

On Tue, Aug 25, 2020 at 01:08:06 +0000, Daan van Gorkum wrote: > Hi Jeff, > > Thanks for your reply! > > Regarding grouping by remote address, I understand and for now I'll keep a > close eye. Maybe it's an option to group by /24 for ipv4 and /64 for IPv6? Hrm, interesting idea. But the answer is: no, there isn't a way. The simplest way to implement something

Some of the behaviours you observe may be due to the same bug I encountered: https://dovecot.org/pipermail/dovecot/2019-July/116475.html Especially, regarding the ?successful' field for auth, which does not exists and is really named ?success', and which is never set anyway. > Le 15 ao?t 2019 ? 23:57, Matt Bryant via dovecot <dovecot at dovecot.org> a ?crit : > > Is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Greetings, So the changes to the stats modules between v2.2 and v2.3 have broken some of my monitoring. I am attempting to use the new method of gathering "metrics" from "events" - but the details in the documentation are a bit thin. I started with the examples provided at https://wiki2.dovecot.org/Statistics and tried to

Hi Jeff, Thanks again for your insights. I understand that a lot of features are pending and it's totally fine, we're just very eager to use all these features. Reagarding the logging of failed attempts I did try to configure this in these two metrics: metric auth_client_userdb_lookup_finished { event_name = auth_client_userdb_lookup_finished group_by = service local_ip remote_ip

Hello, I am trying to setup GitLab, Redis and PostgreSQL containers in Kubernetes using Gluster for persistence. GlusterFS nodes are setup on machines (CentOS) external to Kubernetes cluster (running on RancherOS host). Issue is that when GitLab tries starting up, the login page doesn't load. It's a fresh setup and not something that stopped working now. root at

Getting this answer back on the list in case anyone else is trying to share storage. Thanks for the docs pointer, Tanner. -John On Thu, Sep 7, 2017 at 6:50 PM, Tanner Bruce <tanner.bruce at farmersedge.ca> wrote: > You can set a security context on your pod to set the guid as needed: > https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ > > > This

I was wondering if there was any imminent support in 2.3.12+ for using a username to log into Redis, as well as support for using TLS to connect to Redis. And if not, I'd like to put in a feature request for those two things (AUTH with username/password, and TLS connections to Redis). Specifically, I was looking at using a username/password combo to log into Redis for the quota_clone plugin.

Hi, I'm currently fine-tuning OwnCloud on a CentOS 7 server. To configure transactional locking, I need Redis with the corresponding PHP module. Until recently the server has been running PHP 7.1. I simply installed the 'redis' package as well as 'sclo-php71-php-pecl-redis', started and/or restarted a handful of services, and things worked perfectly. Now I'm upgrading my

TL;DR: Is there a sensible way to get rsyslog to talk to redis on CentOS 7. The official way is to use the omhiredis plugin, but that doesn't seem to exist in the CentOS 7 repositories? (It's how I do it on my Fedora box.) The long version: I'm trying to rationalise logging and am using an ELK stack. When I've done this in the past it has suffered badly from congestion at peak

Hi, I would like to use a fqdn instead of an IP address as redis host quota_clone_dict = redis:host=redis.host.name:port=6379 But only ip adresses are supported Error: quota_clone_dict: Failed to initialize 'redis:host=redis.host.name:port=6379': dict redis: Invalid IP: redis.host.name Why is name resolution not implemented here ? Is it for performance considerations ? St?phane

I''m a recent convert to Rails and I''m working on a new project using Rails 2.3 (I''ll probably upgrade at some point when Rails 3 is in production and had a chance to bake the .0 bugs out). I''m going to use Redis anyway for caching important data, so I thought I''d use the redis-store: http://github.com/jodosha/redis-store But it appears the flash

Hello, Are you looking for a general caching solution or you specifically need to use Redis? At Thirdlane we use Memcached which works just fine for our purposes. Regards, Volodya Ivanets From: "Dovid Bender" <dovid at telecurve.com> To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com> Sent: Wednesday, July 8,