-------------------- Start of forwarded message -------------------- Subject: [rt.debian.org #9931] /var/run/reboot-lock ineffective on tag2upload-builder-01 From: "Adam D. Barratt via RT" <[email protected]> Message-ID: <rt-4.4.6+dfsg-1.1+deb12u3-1215400-1768662790-1602.9931-...@debian.org> To: [email protected] Date: Sat, 17 Jan 2026 15:13:10 +0000
On Sat Jan 17 14:46:04 2026, adsb wrote: > On Sat Jan 17 14:02:53 2026, [email protected] wrote: > > Hello, > > > > Aurelien Jarno [17/Jan 12:36pm GMT] wrote: > > > I haven't looked at all the details, but here are a few things from > > > the logs. > > > The reboot of tag2upload-builder-01 was scheduled at 14:12:29. It > > > indeed caused a podman container to be stopped: > [...] > > > Could you please confirm from your logs that the reboot lock was > > > indeed taken by your tag2upload job? > > > > It doesn't print anything if it successfully takes the lock, but it > > prints something and exits if it fails to take the lock (verified by > > our test suite), and the logs indicate it did not exit. So, yes, I > > can > > confirm that the job did indeed take the lock. > > Looking through the log of #1125239, I think some of the timings have > been confused, so it would be worth checking the process flow. In fact, I was confused. > | Jan 10 13:53:44 tag2upload-oracle-01 tag2upload-oracled[2556368]: > [t2u-oracled tag2upload-builder-01.debian.org,2556368][2026-01- > 10T13:53:44] group_leader: received SIGTERM; shutting down workers > | Jan 10 13:53:44 tag2upload-oracle-01 systemd[2556306]: Stopping > tag2upload-oracled.service - tag2upload Oracle daemon... > | Jan 10 13:53:44 tag2upload-oracle-01 systemd[2556306]: Stopped > tag2upload-oracled.service - tag2upload Oracle daemon. > | -- Boot cbbd32cac2974b5e901921187e477fa7 -- > | > | This is the host rebooting. > > In fact, it's not - as Aurelien noted, the reboot was at 14:12. [...] Ian was correct. The above is tag2upload-_oracle_-01 rebooting. > | Jan 10 14:12:29 tag2upload-oracle-01 tag2upload-oracled[1788]: > Connection to tag2upload-builder-01.debian.org closed by remote host. > | Jan 10 16:36:21 tag2upload-oracle-01 tag2upload-oracled[892]: [t2u- > oracled tag2upload-builder-01.debian.org,892][2026-01-10T16:36:21] > group_leader worker=1787: died due to fatal signal PIPE > | > | IHNI what these are. They are probably related. Any ideas? > > No idea on the second, but the first is the tag2upload-builder-01 > reboot. This is still correct. The oracle rebooted at 13:54, the builder at 14:12. If it helps, the manager reboot was at 13:58. Sorry for the confusion. Adam -------------------- End of forwarded message --------------------
