What is the time unit maildirlock will accept?
I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in: Fatal: Invalid timeout value: 20s
And if you don't specify time unit you just get: Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
This is on 2.3.3. 2.2 worked fine without needing time unit specified.
Why is there even a lock on 'maildir' at all...
unless this is not specific to maildir as specd in mail_location, I might be missing something though, 'm only just now having my first coffee of the day
(we haven't migrated to 2.3 yet, since 2.2 is very stable)
On 15/10/2018 23:46, Kris von Mach wrote:
What is the time unit maildirlock will accept?
I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in: Fatal: Invalid timeout value: 20s
And if you don't specify time unit you just get: Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
This is on 2.3.3. 2.2 worked fine without needing time unit specified.
-- Kind Regards,
Noel Butler
This Email, including any attachments, may contain legally privilegedinformation, therefore remains confidential and subject to copyright protected under international law. You may not disseminate, discuss, or reveal, any part, to anyone, without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments, immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message. Only PDF [1] and ODF [2] documents accepted, please do not send proprietary formatted documents
Links:
[1] http://www.adobe.com/ [2] http://en.wikipedia.org/wiki/OpenDocument
On 15.10.2018 16.46, Kris von Mach wrote:
What is the time unit maildirlock will accept?
I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in: Fatal: Invalid timeout value: 20s
And if you don't specify time unit you just get: Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
This is on 2.3.3. 2.2 worked fine without needing time unit specified.
Which setting is this?
Aki
This appears to be a bug.
On 10/15/2018 9:46 PM, Kris von Mach wrote:
What is the time unit maildirlock will accept?
I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in: Fatal: Invalid timeout value: 20s
And if you don't specify time unit you just get: Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
This is on 2.3.3. 2.2 worked fine without needing time unit specified.
Don't think maildirlock uses dovecot config, but sure. maildirlock is a utility that comes with dovecot...
# /usr/local/libexec/dovecot/maildirlock -h Usage: maildirlock <path> <timeout> - SIGTERM will release the lock.
# /usr/local/libexec/dovecot/maildirlock /home2/vpopmail/domains/swishmail.com/mach/Maildir 20s Fatal: Invalid timeout value: 20s
# /usr/local/libexec/dovecot/maildirlock /home2/vpopmail/domains/swishmail.com/mach/Maildir 20 Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
# /usr/local/libexec/dovecot/maildirlock /home2/vpopmail/domains/swishmail.com/mach/Maildir 20S Fatal: Invalid timeout value: 20S
# /usr/local/libexec/dovecot/maildirlock /home2/vpopmail/domains/swishmail.com/mach/Maildir 20 seconds Usage: maildirlock <path> <timeout> - SIGTERM will release the lock.
# /usr/local/libexec/dovecot/maildirlock /home2/vpopmail/domains/swishmail.com/mach/Maildir '20 seconds' Fatal: Invalid timeout value: 20 seconds
I also tried sec, secs, both upper and lower.
# 2.3.3 (dcead646b): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.2-STABLE amd64 # Hostname: auth_cache_size = 20 M auth_mechanisms = plain login digest-md5 cram-md5 apop auth_worker_max_count = 120 default_process_limit = 2048 disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 last_valid_gid = 89 last_valid_uid = 89 login_greeting = Dovecot ready. mail_location = maildir:~/Maildir:INDEX=/index/%d/%n mail_max_userip_connections = 512 mail_plugins = quota zlib fts fts_solr mail_privileged_group = mail maildir_broken_filename_sizes = yes namespace inbox { inbox = yes location = mailbox "Deleted Items" { auto = no autoexpunge = 30 days special_use = \Trash } mailbox Drafts { auto = create special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = create autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = create autoexpunge = 30 days special_use = \Trash } prefix = } passdb { args = webmail=127.0.0.1 driver = vpopmail } plugin { fts = solr fts_autoindex = yes fts_solr = break-imap-search url=http://localhost:8983/solr/dovecot/ quota = maildir zlib_save = gz zlib_save_level = 9 } protocols = imap pop3 service anvil { client_limit = 12291 } service auth { client_limit = 12288 } service imap-login { process_min_avail = 32 service_count = 0 vsz_limit = 4 G } service imap { process_limit = 5120 vsz_limit = 4 G } service pop3-login { process_min_avail = 32 service_count = 0 vsz_limit = 4 G } service pop3 { process_limit = 5120 vsz_limit = 4 G } shutdown_clients = no ssl_cert =
On 10/28/2018 2:41 AM, Aki Tuomi wrote:
On 27 October 2018 at 21:32 Kris von Mach < mach@swishmail.com mailto:mach@swishmail.com> wrote:
This appears to be a bug.
On 10/15/2018 9:46 PM, Kris von Mach wrote:
What is the time unit maildirlock will accept? I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in: Fatal: Invalid timeout value: 20s And if you don't specify time unit you just get: Panic: BUG: No IOs or timeouts set. Not waiting for infinity. This is on 2.3.3. 2.2 worked fine without needing time unit specified.
Can you provide doveconf -n please?
Aki Tuomi
participants (3)
-
Aki Tuomi
-
Kris von Mach
-
Noel Butler