Re: [CentOS] Syncronize systemctl status with reality?

On 29 August 2017 at 21:52, Leroy Tennison <le...@datavoiceint.com> wrote: > - Original Message - > From: "James Hogarth" <james.hoga...@gmail.com> > To: "centos" <centos@centos.org> > Sent: Tuesday, August 29, 2017 2:03:44 PM &

Re: [CentOS] Syncronize systemctl status with reality?

Hmmm, that's an interesting option, I'll have to look into it. - Original Message - From: "Alexander Dalloz" <ad+li...@uni-x.org> To: "centos" <centos@centos.org> Sent: Tuesday, August 29, 2017 4:17:37 PM Subject: Re: [CentOS] Syncronize systemctl status wi

Re: [CentOS] Syncronize systemctl status with reality?

Am 29.08.2017 um 22:52 schrieb Leroy Tennison: The AppPreloader is doing things (and probably confusing systemd in the process) but I didn't start that, it was a part of the reboot. I looked at /etc/init.d/puppetmaster to see if something strange was being done and it was one of the simpler

Re: [CentOS] Syncronize systemctl status with reality?

- Original Message - From: "James Hogarth" <james.hoga...@gmail.com> To: "centos" <centos@centos.org> Sent: Tuesday, August 29, 2017 2:03:44 PM Subject: Re: [CentOS] Syncronize systemctl status with reality? On 29 Aug 2017 17:58, "Leroy Ten

Re: [CentOS] Syncronize systemctl status with reality?

On 29 Aug 2017 17:58, "Leroy Tennison" wrote: The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember

[CentOS] Syncronize systemctl status with reality?

The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ● puppetmaster.service -