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
When running with "checkpoint=1", and "secs=n", I'm seeing this panic (output below) consistently for any value of n: it will run happily for n seconds, then panic.
I'm using nightlies of both dovecot core and imaptest:
dovecot-20190509 (this looks like it's still the most recent?)
imaptest-20190504 (a little old now, but commit history doesn't suggest anything relevant has changed since)
Is this expected? I would expect it to shutdown cleanly after n seconds (just as if the operator had pressed ^C, which works fine).
Note that it panics after n seconds of runtime (verified by running time imaptest ..., but not shown here), so I guess it's trying to shut itself down cleanly, but is tripping over something? (i.e. it does not seem to be panicking during the run, but rather during the shutdown)
If I run without "checkpoint=1" then it does shut itself down cleanly after n seconds.
(This is with Cyrus IMAPd as the IMAP server being tested, but I should not expect that to make any difference.)
Happy to provide further diagnostics/debug output/etc if you tell me what you need!
As a workaround, I've stopped calling imaptest with the "secs=n" parameter and instead have arranged for the parent process to send the imaptest pid a SIGINT after the desired duration (i.e. trying to mimick the behaviour of pressing ^C in the controlling terminal, which consistently shuts down cleanly). But, to my surprise, it consistently panics like this, too.
I think, maybe, that this might indicate the presence/absence of a controlling terminal as being an important factor here?
Hi,
When running with "checkpoint=1", and "secs=n", I'm seeing this panic (output below) consistently for any value of
n
: it will run happily for n seconds, then panic.I'm using nightlies of both dovecot core and imaptest:
Is this expected? I would expect it to shutdown cleanly after n seconds (just as if the operator had pressed ^C, which works fine).
Note that it panics after n seconds of runtime (verified by running
time imaptest ...
, but not shown here), so I guess it's trying to shut itself down cleanly, but is tripping over something? (i.e. it does not seem to be panicking during the run, but rather during the shutdown)If I run without "checkpoint=1" then it does shut itself down cleanly after n seconds.
(This is with Cyrus IMAPd as the IMAP server being tested, but I should not expect that to make any difference.)
Happy to provide further diagnostics/debug output/etc if you tell me what you need!
Cheers,
ellie
The text was updated successfully, but these errors were encountered: