On Mon, Jun 26, 2017 at 09:26:01AM +0200, Arne Nordmark wrote: > Package: openafs-fileserver > Version: 1.6.20-2 > Severity: normal > > Dear Maintainer, > > This Sunday morning, the bosserver process on all stretch machines was found > to have stopped. > [snip] > > The reason why a restarttime entry is present is lost in the mists of time, > but might well have been a default setting once.
It was the default for a long time, yes. > Using the bos command to restart bosserver manually gives the same result: > > # bos restart -server localhost -bosserver -localauth > > causes bosserver to shut down, again with the same log entry. > > This is definitely a regression compared to jessie. > As I interpret the log entry, a signal 15 is sent from the outside. > The most obvious difference (compared to jessie) is the presence of a systemd > unit file in the stretch version. > Is systemd process control clashing with how bos tries to restart itself? This does seem likely to be an issue with the systemd integration, yes. (Not using the weekly restarts, I didn't observe it in testing.) Thanks for the report; I'll take a look. -Ben
