I think the key here is that the status of the application for designate-mdns is indicating that 'Services not running that should be: designate-mdns'. Unit designate/2 is still reporting (at the time of collection) that designtate-mdns is still not running.
When checking the psaux.txt listings for each of the unit, we can see that designate/0 and designate/1 are indeed running designate-mdns but unit designate/2 is not.
I think the key here is that the status of the application for designate-mdns is indicating that 'Services not running that should be: designate-mdns'. Unit designate/2 is still reporting (at the time of collection) that designtate-mdns is still not running.
When checking the psaux.txt listings for each of the unit, we can see that designate/0 and designate/1 are indeed running designate-mdns but unit designate/2 is not.
$ grep designate-mdns designate_ ?/psaux. txt 0/psaux. txt:designa+ 83726 0.1 0.0 191408 80920 ? Ss 13:57 0:12 /usr/bin/python3.6 /usr/bin/ designate- mdns --config- file=/etc/ designate/ designate. conf --log-file= /var/log/ designate/ designate- mdns.log 1/psaux. txt:designa+ 79274 0.1 0.0 191408 80992 ? Ss 13:56 0:12 /usr/bin/python3.6 /usr/bin/ designate- mdns --config- file=/etc/ designate/ designate. conf --log-file= /var/log/ designate/ designate- mdns.log
designate_
designate_