How I'd love if I could just launch dovecot (with symbols) in a debugger, set a breakpoint in the right function call, and login from Rainloop. Then I could run the process one step at a time and inspect everything...
Yassine.
On 3/14/19 3:59 PM, Eric Grammatico via dovecot wrote:
The error is generated when a user get connect from a client (RainLoop, a web UI). I don't know if the client request the quota or if it's automagically pushed from the imap process. I'd say the client requests. My problem is the process imap generating the error is launched just before and stopped right after the error is raised and thus quite difficult to trace the process.
- Eric Grammatico _/)
14 mars 2019 15:46 "Yassine Chaouche via dovecot" dovecot@dovecot.org a écrit:
On 3/14/19 3:40 PM, Eric Grammatico via dovecot wrote:
Hi there,
Well.. I didn't find a way to strace imap. If I well understood, the faulty IMAP is launched by dovecot from or after a succesfull imap-login process. I have executed manually '/usr/libexec/dovecot/imap -u eric' and typed getquotaroot "INBOX" which didn't reproduce the error seen in the dovecot logs and reported the correct quota.
Any idea how to find the imap command generating the error
imap(eric)<3085></M5VXfCBwJejrKVa>: Error: Failed to get quota resource STORAGE: quota-fs: quotactl(Q_GETQUOTA, /dev/vda1) failed: No such file or directory
Thanks and regards,
Eric Grammatico _/) How did you get that error in the first place ? :p
Yassine.