On Mon, Jun 26, 2017 at 12:08:29PM -0500, Benjamin Kaduk wrote: > > 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.
It seems that any ReBozo action (re-exec bosserver) will cause systemd to think that bosserver has successfully exited, since the re-exec will call daemon() again, and the parent process will then exit(0). systemd (as configured by openafs-fileserver.service) does not follow the fork, and does not know to track the new child. It thus thinks that the service has stopped cleanly. openafs-fileserver.service has an ExecStop that runs bos shutdown, so systemd *does* run that, which terminates cleanly the new child bosserver (and the managed services). It seems likely that the cleanest solution will be to convert the unit file to use the -nofork argument to bosserver. -Ben
