OK, still crashed overnight while the laptop was closed.

Here's the log. I had shut the laptop a bit before this first entry:

Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds - 
adjusting timeouts.
Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): 
assertion failed: (usecs >= 0)
Mar 03 02:33:57 master: Error: Raw backtrace: 0   libdovecot.0.dylib            
      0x0000000102d8f120 backtrace_append + 72 -> 1   libdovecot.0.dylib        
          0x0000000102d8f264 backtrace_get + 44 -> 2   libdovecot.0.dylib       
           0x0000000102d9dd54 default_fatal_finish + 72 -> 3   
libdovecot.0.dylib                  0x0000000102d9c7c4 default_error_handler + 
0 -> 4   libdovecot.0.dylib                  0x0000000102d9c790 
fatal_handler_real + 0 -> 5   dovecot                             
0x0000000102ab3538 master_fatal_callback + 248 -> 6   libdovecot.0.dylib        
          0x0000000102d9c940 i_fatal + 0 -> 7   libdovecot.0.dylib              
    0x0000000102db6724 ioloop_iolist_add + 0 -> 8   libdovecot.0.dylib          
        0x0000000102db4a3c io_loop_handle_timeouts + 640 -> 9   
libdovecot.0.dylib                  0x0000000102db7438 
io_loop_handler_run_internal + 392 -> 10  libdovecot.0.dylib                  
0x0000000102db5130 io_loop_handler_run + 224 -> 1
 1  libdovecot.0.dylib                  0x0000000102db5000 io_loop_run + 92 -> 
12  libdovecot.0.dylib                  0x0000000102d0e22c master_service_run + 
28 -> 13  dovecot                             0x0000000102ab2e28 main + 2952 -> 
14  dyld                                0x0000000187c9ffd8 start + 2412
Mar 03 02:33:57 log(451): Warning: Killed with signal 15 (by pid=1 uid=0 
code=unknown 0)

.There were a number of "Time moved forward" entries earlier as well. The one 
here was isolated, but often they occur in pairs with nearly identical amounts 
of time, differing only by the fractions of a second between them, I suppose. 
For example (pairs highlighted with the same color):

Mar 04 13:12:38 master: Warning: Time moved forward by 9.347642 seconds - 
adjusting timeouts.
Mar 04 13:14:31 imap(12422): Warning: Time moved forward 83.410157 seconds
Mar 04 13:14:31 imap(12420): Warning: Time moved forward 83.410166 seconds
Mar 04 13:19:44 imap(12422): Warning: Time moved forward 282.970564 seconds
Mar 04 13:19:44 imap(12420): Warning: Time moved forward 282.970608 seconds
Mar 04 13:19:44 master: Warning: Time moved forward by 366.378919 seconds - 
adjusting timeouts.
Mar 04 13:25:27 imap(12422): Warning: Time moved forward 282.941775 seconds
Mar 04 13:25:27 imap(12420): Warning: Time moved forward 282.943614 seconds
Mar 04 13:25:27 master: Warning: Time moved forward by 282.937627 seconds - 
adjusting timeouts.
Mar 04 13:30:20 imap(12422): Warning: Time moved forward 263.355743 seconds
Mar 04 13:30:20 imap(12420): Warning: Time moved forward 263.350968 seconds

Now that I look, I realize that most, but not all, of the imap warnings (vs 
master) come in pairs.

J

> On Mar 2, 2025, at 18:18, J wrote:
> 
> OK, done. Will restart. Here's the new pmset info:
> 
> System-wide power settings:
>  SleepDisabled                0
> Currently in use:
>  standby              1
>  Sleep On Power Button 1
>  hibernatefile        /var/vm/sleepimage
>  powernap             1
>  networkoversleep     0
>  disksleep            10
>  sleep                1 (sleep prevented by useractivityd, powerd, sharingd)
>  hibernatemode        3
>  ttyskeepawake        1
>  displaysleep         20
>  tcpkeepalive         1
>  lowpowermode         0
>  womp                 0
> 
> J
> 
>> On Mar 2, 2025, at 16:44, Aki Tuomi via dovecot <dovecot@dovecot.org> wrote:
>> 
>> Hi!
>> 
>> Can you try disabling "low power mode" and see if that makes any difference? 
>> I don't have a mac, but try to go System Settings > Battery, select the 
>> drop-down menu next to Low Power Mode, and choose Never?
>> 
>> Aki
>> 
>>> On 02/03/2025 17:30 EET J wrote:
>>> 
>>> 
>>> Below are the results of "pmset -g".
>>> 
>>> Keep in mind that this 
>>> 
>>> 
>>> J
>>> 
>>> 
>>>> On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot@dovecot.org> 
>>>> wrote:
>>>> 
>>>> 
>>>> I wonder if this is some power saving feature that pauses dovecot 
>>>> processes? Do
>>>> you have power saving enabled?
>>> 
>>> 
>>> 
>>> System-wide power settings:
>>> SleepDisabled0
>>> Currently in use:
>>> standby 1
>>> Sleep On Power Button 1
>>> hibernatefile /var/vm/sleepimage
>>> powernap 1
>>> networkoversleep 0
>>> disksleep 10
>>> sleep 1 (sleep prevented by powerd)
>>> hibernatemode 3
>>> ttyskeepawake 1
>>> displaysleep 20
>>> tcpkeepalive 1
>>> lowpowermode 1
>>> womp 0
>> 
>> _______________________________________________
>> dovecot mailing list -- dovecot@dovecot.org
>> To unsubscribe send an email to dovecot-le...@dovecot.org
> 

_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Reply via email to