I've rebooted at least 3 times since I did the update and it's still the same, but I tried those commands and got this:
[root@MAGGIE ~]# systemctl restart pmlogger
Job for pmlogger.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status pmlogger.service" and "journalctl -xe" for details.
The details are:
May 04 13:14:26 MAGGIE.mydomain.com systemd[1]: Failed to start Performance Metrics Archive Logger.
-- Subject: A start job for unit pmlogger.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit pmlogger.service has finished with a failure.
--
-- The job identifier is 13372 and the job result is failed.
May 04 13:14:26 MAGGIE.mydomain.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:>
May 04 13:14:26 MAGGIE.mydomain.com systemd[1]: Starting Check pmlogger instances are running...
-- Subject: A start job for unit pmlogger_check.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit pmlogger_check.service has begun execution.
--
-- The job identifier is 13479.
May 04 13:14:27 MAGGIE.mydomain.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:>
May 04 13:14:27 MAGGIE.mydomain.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s>
May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 4.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Automatic restarting of the unit pmlogger.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: Stopped Performance Metrics Archive Logger.
-- Subject: A stop job for unit pmlogger.service has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A stop job for unit pmlogger.service has finished.
--
-- The job identifier is 13582 and the job result is done.
May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: Starting Performance Metrics Archive Logger...
-- Subject: A start job for unit pmlogger.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit pmlogger.service has begun execution.
--
-- The job identifier is 13582.
I have gathered all the files into archive and will email you them separately - hope that's ok.
Hi Mark,
I've rebooted at least 3 times since I did the update and it's still the same, but I tried those commands and got this:
[root@MAGGIE ~]# systemctl restart pmlogger
Job for pmlogger.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status pmlogger.service" and "journalctl -xe" for details.
The details are:
May 04 13:14:26 MAGGIE.mydomain.com systemd[1]: Failed to start Performance Metrics Archive Logger. /lists. freedesktop. org/mailman/ listinfo/ systemd- devel u:system_ r:init_ t:> check.service has begun execution /lists. freedesktop. org/mailman/ listinfo/ systemd- devel check.service has begun execution. u:system_ r:init_ t:> u:system_ r:init_ t:s> /lists. freedesktop. org/mailman/ listinfo/ systemd- devel /lists. freedesktop. org/mailman/ listinfo/ systemd- devel /lists. freedesktop. org/mailman/ listinfo/ systemd- devel
-- Subject: A start job for unit pmlogger.service has failed
-- Defined-By: systemd
-- Support: https:/
--
-- A start job for unit pmlogger.service has finished with a failure.
--
-- The job identifier is 13372 and the job result is failed.
May 04 13:14:26 MAGGIE.mydomain.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_
May 04 13:14:26 MAGGIE.mydomain.com systemd[1]: Starting Check pmlogger instances are running...
-- Subject: A start job for unit pmlogger_
-- Defined-By: systemd
-- Support: https:/
--
-- A start job for unit pmlogger_
--
-- The job identifier is 13479.
May 04 13:14:27 MAGGIE.mydomain.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_
May 04 13:14:27 MAGGIE.mydomain.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_
May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 4.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https:/
--
-- Automatic restarting of the unit pmlogger.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: Stopped Performance Metrics Archive Logger.
-- Subject: A stop job for unit pmlogger.service has finished
-- Defined-By: systemd
-- Support: https:/
--
-- A stop job for unit pmlogger.service has finished.
--
-- The job identifier is 13582 and the job result is done.
May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: Starting Performance Metrics Archive Logger...
-- Subject: A start job for unit pmlogger.service has begun execution
-- Defined-By: systemd
-- Support: https:/
--
-- A start job for unit pmlogger.service has begun execution.
--
-- The job identifier is 13582.
I have gathered all the files into archive and will email you them separately - hope that's ok.
Cheers,
Fernando