[15:55:05] <vgutierrez>	 moritzm: trafficserver-tls systemd unit is not happy with Buster
[15:55:22] <vgutierrez>	 Jan 22 15:54:24 traffic-cache-atsupload-buster systemd[32327]: trafficserver-tls.service: Failed to set up mount namespacing: No such file or directory
[15:55:22] <vgutierrez>	 Jan 22 15:54:24 traffic-cache-atsupload-buster systemd[32327]: trafficserver-tls.service: Failed at step NAMESPACE spawning /usr/bin/traffic_manager: No such file or directory
[15:55:22] <vgutierrez>	 Jan 22 15:54:24 traffic-cache-atsupload-buster systemd[1]: trafficserver-tls.service: Main process exited, code=exited, status=226/NAMESPACE
[15:55:31] <vgutierrez>	 have you seen that one before?
[15:56:44] <vgutierrez>	 for context, trafficserver-tls symlinks some ATS binaries on /srv/trafficserver/tls/bin/
[15:59:14] <moritzm>	 which host is that?
[16:00:17] <vgutierrez>	 hmm I think I've solved it
[16:00:39] <vgutierrez>	 we've seen this one in the past
[16:00:55] <vgutierrez>	 it's basically cause the systemd unit is listing on ReadWritePaths a directory that doesn't exist
[16:01:13] <vgutierrez>	 but the error message is shitty as fuck :)
[16:05:53] <moritzm>	 well, to be fair:"No such file or directory" isn't the most misleading error ever :-)
[16:09:05] <vgutierrez>	 reading "/usr/bin/traffic_manager: No such file or directory" I assume that /usr/bin/traffic_manager doesn't exist
[16:09:18] <vgutierrez>	 but that's obviously a L8 issue
[16:09:49] <cdanis>	 the 'most misleading error' award goes to the "The name org.freedesktop.PolicyKit1 was not provided by any .service files"
[16:09:52] <cdanis>	 ;)
[16:19:57] <moritzm>	 also.
[16:20:19] <moritzm>	 a million times better than "woah, the service is gone and all I have is a stale PID file" :-)
[16:28:01] <vgutierrez>	 lol