Hi! On Fri, 2017-01-06 at 13:46:14 +0100, Vincent Lefevre wrote: > On 2017-01-06 13:15:18 +0100, Guillem Jover wrote: > > On Fri, 2017-01-06 at 11:33:08 +0100, Vincent Lefevre wrote: > > > Package: dpkg > > > Version: 1.18.18 > > > Severity: grave > > > Justification: renders package unusable > > > > I don't think this severity is right here, at least for dpkg, but > > let's see. > > Lowering to normal since after several upgrades, I can't reproduce the > problem.
Thanks. > > I'm assuming that cannot easily reproduce the problem? > > I couldn't reproduce it yet. > > > That the system probably has some unnattended async calls to a > > command that locks the dpkg database? > > Such as? In any case, there is nothing in the dpkg/apt logs that > would suggest that. Do you happen to have something installed like unattended-upgrades or apt-dater perhaps? > In the journalctl logs at this time, I only have: > > Jan 06 11:24:38 cventin systemd[1]: Reloading. > Jan 06 11:24:38 cventin systemd[1]: apt-daily.timer: Adding 8h 48min > 32.153121s random time. > Jan 06 11:24:38 cventin systemd[1]: Reloading. > Jan 06 11:24:38 cventin systemd[1]: apt-daily.timer: Adding 11h 35min > 4.281611s random time. > Jan 06 11:24:38 cventin systemd[1]: Stopped Daily apt activities. > Jan 06 11:24:38 cventin systemd[1]: Stopping Daily apt activities. > Jan 06 11:24:38 cventin systemd[1]: apt-daily.timer: Adding 5h 4min > 59.261844s random time. > Jan 06 11:24:38 cventin systemd[1]: Started Daily apt activities. > Jan 06 11:24:38 cventin systemd[1]: Starting Daily apt activities... > Jan 06 11:24:40 cventin systemd[1]: Started Daily apt activities. > Jan 06 11:24:40 cventin systemd[1]: apt-daily.timer: Adding 10h 35min > 58.916108s random time. > Jan 06 11:24:40 cventin systemd[1]: apt-daily.timer: Adding 9h 54min > 24.332138s random time. > > This is due to the apt upgrade, I assume. This looks strange, though: > e.g. Started, then Starting, then Started. If one of those actually run, the timing would seem to indicate it might have tripped over the currently run upgrade. :/ (This race condition is known and we do not have a solution for it yet, but this would probably be a bug in whatever enabled such automatic handling, and/or apt itself as it could avoid this problem for at least any frontend using it with an additional global lock.) Thanks, Guillem
