sean797
commented
7 years ago @Klaas- there's a lot of info here, can you provide simple steps to reproduce this?
E.g
systemctl start foo
yum install bar
tracer -eaClosed Klaas- closed 6 years ago
sean797
commented
7 years ago @Klaas- there's a lot of info here, can you provide simple steps to reproduce this?
E.g
systemctl start foo
yum install bar
tracer -ea
Areyus
commented
6 years ago Hi,
since Klaas is not working with us anymore, I'm currently taking a look into this issue. I am currently not able to reproduce this consistently. It looks like tracer is sometimes not able to recognize the reboot after kickstart post section, but I can not tell for sure. I will take a closer look as soon possible.
sean797
commented
6 years ago @Areyus running tracer in kickstart post section sounds a little odd to me, I mean you're going to reboot the box anyway so I don't see any benefit running tracer?
Klaas-
commented
6 years ago @sean797 tracer is run after the reboot. Kickstart (+post scripts) install a lot of packages yum.log --> until [Puppet is the last package installed within kickstart post] then system is rebooted and on first puppet run after reboot it installs a lot of other packages from puppet and starts some services. Including the one I referenced (package open-vm-tools service vmtoolsd) as an example.
After all this is done tracer shows services need restarting but that is impossible because it only installs new packages that have not existed in system prior and therefore can't run in an old version.
But I'll let @Areyus get into the details more, I can't provide any additional info because I changed jobs and do not have access to those systems anymore.
Greetings Klaas
sean797
commented
6 years ago @Klaas- As I understand your comment, you're saying installing open-vm-tools results in tracer reporting something needs restarting. I'm unable to reproduce that.
After all this is done tracer shows services need restarting but that is impossible because it only installs new packages that have not existed in system prior and therefore can't run in an old version.
Not necessarily, when you install a package it could (but shouldn't) overwrite an existing file which would cause tracer to report it needs restarting.
Klaas-
commented
6 years ago @sean797 are there docs that explain how the service restart detection works? It could be that puppet is touching configuration files or something along those lines Or can I enable debug to see why tracer is reporting the services that need restarting?
sean797
commented
6 years ago @Klaas- There is http://docs.tracer-package.com/en/latest/
If a process has loaded in memory an file which is provided by any package and changed since the process has start, we consider that process as outdated.I think we can close this for now, I can't reproduce this anymore
Thanks for the help @sean797
Hey, I have a problem with tracer false positives after I have installed new packages via puppet. If you see the yum.log it only installs new packages after reboot and doesn't update any so I think everything tracer notices are false positive messages.
the most obvious example to me is vmtoolsd, this is from package open-vm-tools the package was installed at 14:11:06 service was started at 14:11:12 before that the service was not installed so it can't need a restart because its already running from the installed package
current epel tracer:
epel-testing tracer:
systemctl status for those services:
yum.log of that server (I've inserted a few comments on where the installs happen):