Displaying 20 results from an estimated 100 matches similar to: "Getting login stats"
2019 Jul 11
0
Getting login stats
> 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
2019 Aug 15
2
2.3.7 + stats
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 {
???
2020 Sep 19
1
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.
2020 Aug 22
2
Metric label values truncated when using OpenMetrics endpoint
Hi,
Recently we upgraded to Dovecot 2.3.11.3 and configured an example metric like this:
metric imap_command {
event_name = imap_command_finished
group_by = cmd_name tagged_reply_state user remote_ip
}
And enabled the OpenMetrics listener like this:
service stats {
inet_listener http {
port = 5000
}
}
While the result is great, I noticed that some metrics are being truncated
2020 Aug 25
2
Metric label values truncated when using OpenMetrics endpoint
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
2019 Jun 02
4
Stats/Metrics in 2.3
-----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
2023 Mar 15
1
Bug with lmtp_save_to_detail_mailbox
> On 15/03/2023 13:12 EET Dejan <me at dejanstrbac.com> wrote:
>
>
> > lmtp_save_to_detail_mailbox = yes
>
> Plus-delivery conflicts with existing, reserved files such as
> "subscriptions":
>
> Message for kim+subscriptions@ results in:
>
> lmtp(kim@***.com)<14493><SK7sEvaHEWSdOAAAvAYmHA>: Error:
>
2019 Jul 12
2
[bug] success field never emited in auth_request_finished event
Hi,
I'm playing with the new events, and encounter some issues:
First the 'auth_request_finished' event is documented as having a 'successful' field, but in the code, the field is defined as 'success' (e->add_str("success", "yes")).
But more important, in the function "auth_request_success_continue()" (auth/auth-request.c:288),
2020 Sep 19
0
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.
2019 Jul 12
1
[bug] success field never emited in auth_request_finished event
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Would you like to try with 2.3.7? It was released today.
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote type="cite">
<div>
On 12/07/2019 17:05 Jean-Daniel Dupas via dovecot
2020 Aug 26
0
Metric label values truncated when using OpenMetrics endpoint
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
2018 May 30
2
Fatal: nfs flush requires mail_fsync=always
Hello, any news about the attached error?
I'm preparing the 2.2 to 2.3 upgrade and having the same error.
We have the mail stores in an NFS filer.
Regards
> On 19.01.2018 11:55, S?ren Skou wrote:
>> Hiya all,
>>
>> I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on
>> my testbed. The issue is that from what I can see, mail_fsync
2020 Aug 27
1
Metric label values truncated when using OpenMetrics endpoint
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
2018 Jan 19
1
Fatal: nfs flush requires mail_fsync=always
Hiya all,
I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on
my testbed. The issue is that from what I can see, mail_fsync is set
to always :
# doveconf -n | grep mail_fs
mail_fsync = always
The result is that the client does not connect at all, which is not
really what I wanted to happen :)
Any idea what is going wrong here?
Best regards
S?ren P. Skou
2006 Aug 07
2
Dynamically created queries
Hello,
I am having difficulty dynamically building a query. I want to ensure
that I''m using Active Record protection against SQL injection attacks.
In PHP land, I would have built up the query in my logic & attempted to
clean every variable - a bit tedious really.
I want to be able to achieve something like:
events = Event.find(:all,
:conditions => [**DynamicallyBuiltQuery**
2013 Jan 07
3
renumber a list of numbers
Greetings R users,
I am trying to renumber my groups within the file shown below. The groups
are currently set as 8,9,10,etc. I would like to renumber this as
1,2,3,etc. I have searched the help files and only come across using the
rownames to renumber the values but I need to match values. Any assistance
is always appreciated,
Regards,
Charles
structure(list(Group = structure(c(1L, 1L, 1L,
2019 Jul 12
0
[bug] success field never emited in auth_request_finished event
An other issue is that when 'request->passdb_success' is FALSE, the request fails but the error field is not set (as it is only set when request->failure is TRUE), which make it hard to create metrics for failed login attempts.
We have (assuming success were working as expected):
- success = yes -> means auth OK
- error is present -> means request failed for some reasons
-
2019 Oct 30
2
Dovecot and MySQL aborted connections.
We also spotted these sql connections getting aborted, upon upgrading
MySQL from 5.6 to 5.7. (Going back to 5.6 we don't see them!)
Turning on mysql general query logging we can see it is Dovecot's mysql
connections that inquire about or update quota usage in particular:
*** /logs//mysql.log ***
2019-10-30T10:52:22.624690-07:00 2 Connect dovecot at localhost on
npomail using
2017 Dec 30
3
Updated Dovecot 2.3.0 now getting 2 strange log errors
I did some more digging around and found this is reproducible on
multiple hosts running the same version of Dovecot/Pigeonhole/Postfix.
The problem resurfaces on any host to an account with enabled
Vacation/OOO response. The Vacation/OOO reply filter was created in
Roundcubemail, but has been fine for years. One thing to note is in
Dovecot 2.3.0 I did enable UTF8, but even if I disable UTF8
2019 Aug 16
0
2.3.7 + stats
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