> > Therefor we are curious whether a bird3 package update will > > interrupt packet forwarding on a BIRD3 BGP router? > > > > The package update does not restart BIRD by itself. One must do it > > manually or scripted themselves. > > We updated bird3 now and bird got restarted automatically in this process > (which is the usual behavior for debian package updates unrelated to bird).
In my case it stayed untouched. I'm running Debian 13 Trixie, was updating from 3.1.4 to 3.2.0, and the bird version shown by the CLI was still 3.1.4 until I restarted it manually 5 minutes later. > At the same time in the log shows the restart without manually triggering > it: > > Jan 05 11:51:47 Stopping bird.service - BIRD Internet Routing Daemon... > Jan 05 11:51:52 bird.service: Deactivated successfully. > Jan 05 11:51:52 Stopped bird.service - BIRD Internet Routing Daemon. > Jan 05 11:51:52 bird.service: Consumed 49min 40.707s CPU time, 1.3G memory > peak. > Jan 05 11:51:52 Starting bird.service - BIRD Internet Routing Daemon... > Jan 05 11:51:52 Started bird.service - BIRD Internet Routing Daemon. That's weird. I have no idea how this happened to you. We don't request for the restart anywhere. Will run tests and check whether we can replicate this behavior on our side. > > I have no idea whether systemd could execute different variants of > > restart and shutdown, but if it is possible to do so, we might extend > > our service file in order to execute the restart/shutdown gracefully, > > regularly or by killing the daemon. > > > > Or set the behavior by an env var? What do you think? > > Since the package update automatically restarts the bird systemd service I > guess this is what people are used to already so it might be hard to change > that? Autorestart is wrong by itself imho. If nothing else, APT should at least _ask_, not restart on update. One could get disconnected by autorestarting BIRD. Maria -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
